Repository navigation
Require evidence for bounded commit readiness - #30
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.
The bounded commits live cases claimed chat tools were unavailable without evidence and could present candidates whose isolated validation was still pending. Require capability evidence, report uninspected ownership as unverified, and explicitly defer candidates with concrete validation commands and expected results.
The isolated live runner had no chat connector. Add a read-only MCP fixture that returns an empty chat inventory scoped to its isolated workspace. It never accesses real chats or repository files and rejects messaging. A unit test verifies the protocol, scope, and refusal behavior. Keep the existing scenario prompts, judge, and assertions unchanged.
Validation:
npm run checkpassed (127 tests passed, 5 skipped; 104 executable SDK cases discovered; production dependency audit clean). Committed-change validation passed. The focused live suite passed both cases (2/2). PR CI passed at2d5e917ca2ebe326c96b5ddd33ca733b349efbef. The live cases exercise proposal and approval safety with a synthetic chat inventory; real desktop owner messaging and approved commit execution are outside this live suite.