Ship repository setup doctor and bounded benchmark corpus (0.3.1) - #15
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.
Adds
encrypted-context doctor <repository-root> --term <known-identifier>so developers can check an installed repository MCP server before connecting Claude or Codex. The read-only probe verifies the exact Git worktree, all four tools, freshness and matching source provenance; it explicitly leaves actual client acceptance untested.The raw-evidence benchmark exceeded its single 128-record fixture. Version 2 retains the full corpus across bounded synthetic collections and counts every response. Per-call limits and gate thresholds stay unchanged; the documented total response budget scales with collection count. This is payload measurement, not evidence of task or subscription savings.
Both packages are versioned 0.3.1 with matching dependency/notices and updated installation guidance. npm publication remains blocked by HTTP 401; matching GitHub release tarballs are the delivery route.
Validation: full workspace checks (386 tests and independent installed-package consumers), both benchmark gates, navigation stdio smoke, 22 scale tests and the 10k postings probe. Private experiment files are excluded.