Repository navigation
Improve review-anvil finding explanations and impact judgment - #13
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.
Summary
Implements the two content improvements, not a Codex-specific launcher change:
Align normal reviewer context/task, engine scope selection, reproduction and the existing scope auditor: PR/diff reviews require applicable attribution; whole-file/path reviews can report proven existing defects within their declared scope. Newly exposed unchanged helpers remain in scope.
No launcher/backend changes, schema additions, new production audit waves, weakened semantic locks or approval-threshold changes. Updates README, retains sanitized evaluation evidence, and removes the source-text/wording assertion suite while retaining behavioral suites.
Verification
Limits and observed failures
timeout exit: got '3', want '124'. Retained captures show capability checking exited 143 with empty capability output, returningcapability-rejectedbefore the expected run-phase timeout; source/proof unchanged and runtime removed. Runner and suite code are unchanged; no unrelated runtime fix or retry was attempted.Evidence:
evaluations/review-anvil-finding-content.json. Private code, feedback quotations and author identities are excluded.