Expose detector assessment and abstention coverage - #28
Merged
Conversation
tn-pisama
marked this pull request as ready for review
September 10, 2026 07: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
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.
Preserve per-detector assessment coverage throughout local analysis, JSON check reports, replay, watch, and smoke. Legacy coverage remains unknown; explicit detector errors produce nonzero exits even with --fail-on never. Check JSON schema is version 3 and documents that threshold success is not complete task validation. Typed metadata allowlists prevent arbitrary disclosure and contradictory findings cannot become passes. Replay does not claim a repair without comparable contract/input provenance. Root independently ran the final full suite: 228 passed. Prior independent review covered metadata and outcome consistency. No version bump or publication; the paired core communication change remains held until the consumer release is verified.