docs: sync API contracts and runtime limits - #59
Merged
Conversation
bearmug
force-pushed
the
docs/api-contract-sync
branch
from
August 16, 2026 00:59
95a4eb7 to
1f0d895
Compare
bearmug
force-pushed
the
fix/transport-hardening
branch
from
August 16, 2026 18:55
35df382 to
fcd36c9
Compare
bearmug
force-pushed
the
docs/api-contract-sync
branch
from
August 16, 2026 18:57
1f0d895 to
e34b953
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n- document all 12 MCP tools and their current parameters\n- document provenance metadata, partial-result semantics, and explicit TA exclusions\n- document strict schemaVersion 1 preset files and operator value shapes\n- document runtime validation ranges and TradingView endpoint limitations\n\n## Verification\n- git diff --check\n- npm test — 250 passed on the full stack\n- npm run build