Correct assessment scope and validate positional contract accounting - #30
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.
Correct the release-blocking completeness claim from PR28. Distinguish selected-detector reporting from whole-trace coverage; validate positional accounting against actual trace length, counts and detector outcomes; reject contradictions without hiding findings/errors. Strip raw span IDs and captured content. Captured Omnigent regression retains context detection and explicitly checks candidate communication abstention instead of legacy lexical alignment. Root reproduced 250 full paired-core tests. Agent also passed 250 with public core1.10.3. Pending core d36cb08 remains unpublished. This PR does not establish business-semantic coverage or approve release PR29.