Repository navigation
0.3.16: generate tool guidance from the backend contract - #10
Merged
Merged
Conversation
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.
Generate the tool registry and guidance from a pinned backend-owned contract so MCP, CLI and OpenAPI cannot drift through independent edits. Import/build checks validate the payload, source inventory and compiled exports; publication rejects uncommitted backend provenance. This prepares compatible core 0.3.16.
All 105 tool names, schemas and annotations remain compatible. Descriptions clarify restricted-key 404s, authority, runtime-off cases, spending and follow-on runs. The REST preservation review retains model-alias resolution, classification waits, install answers, publisher limits and kit-edit consequences. Detailed classified receipt interpretation is delivered with applicable results; toolDocumentation retains full offline/REST help. Pre-call warnings remain in descriptions, raw response data is unchanged, and REST-only long polling adds no MCP input.
Local validation: typecheck, 134 tests and five hygiene checks; packed-core integrations passed MCP 167 and CLI 109 + one existing skip with installed-package smoke. Fresh Linux/macOS/Windows × Node 22/24 CI passed all six jobs on the final imported contract. Actual assembled workers metadata falls from 60,857 to 47,557 serialized tokens (21.9%); this is not a billed-context claim. Both CLI model receipt probes retained the tested interpretations with shorter metadata. Size reports are advisory; stale imports and contract mismatches fail.
Draft pending the backend-first release gate. Publish core after its backend contract is released; consumers then pin the published package. Browser-client exposure is unverified and the approximate 50% size goal remains open. No consolidation or UUID-only input migration is included.