Repository navigation
Fix review coverage parity in finalize and verify - #15
Merged
Merged
Conversation
Finalization and verification now use the same review-coverage rules and material evidence, so a receipt accepted at finalization can be verified against the same source without inconsistent exclusions. The existing isolated reviewer evidence path applies the same contract. Validation: the inherited repair receipt passed full verification; the 2.5.9 candidate built for all six release targets, passed npm/PyPI installer smoke and verified that receipt. Publication remains pending.
Include the already finalized, byte-identical receipt for the reviewed six-file repair so the existing CI material and acceptance gates can verify this PR. The source implementation is unchanged.
auscaster
marked this pull request as ready for review
September 8, 2026 13:19
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.
Finalization and verification now use the same review-coverage rules and material evidence, so a receipt accepted at finalization can be verified against the same source without inconsistent exclusions. The existing isolated reviewer evidence path applies the same contract.
Validation: the inherited repair receipt passed full verification; the 2.5.9 candidate built for all six release targets, passed npm/PyPI installer smoke and verified that receipt. Publication remains pending.
The unchanged finalized receipt is included for the existing merge gate. Material verification and full acceptance both pass locally through the protected-base verifier; the full check used the actual CI script.