Repository navigation
Constrain reviewer context requests to immutable supported targets - #223
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
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.
The reviewer previously advertised symbol lookups and free-form paths that the bounded retriever could not execute. An opt-in v17 profile now supplies finite context choices derived from immutable captured Git objects and the trusted retrieval allowlist.
Each selected path or task-scoped unit is checked against its permitted evidence kind, source revision, and Git blob before retrieval reservation. Invalid proposals remain explicit gaps and preserve valid blocking findings from the same response. Trusted policy files remain outside this context manifest. Existing profiles retain their serialized v4 requests.
Validation: 289 author focused tests, 281 additional root tests, eight independent focused tests, and independent CLEAR review. A representative default request matched baseline byte-for-byte (8,087 bytes). Provider-free PR305 reconstruction offered the HEAD-bound Exa implementation and test paths; this establishes availability, not review quality or resolution of the separate retrieval envelope limit.
Preserves exact historical evidence-module bytes in frozen fixtures; the 35-module inventory and both pinned tree hashes remain unchanged. The affected historical suites passed 86 tests with one skip and independent review cleared this repair. Full clean CI validates packaging; an interrupted local broad run lacked the build dependency and is not claimed as passing.
No provider dispatch, target publication, or Droid cutover is added.