test: guard fail-closed checker behavior - #3
Merged
AmazingAng merged 1 commit intoAug 7, 2026
Conversation
klmtseng
force-pushed
the
test/guard-fail-closed-checker
branch
from
August 7, 2026 14:09
088b796 to
173f40c
Compare
AmazingAng
added a commit
that referenced
this pull request
Aug 7, 2026
A regression mixing up the two failure branches (pattern present vs scan broke) previously returned the same rc 1 and would have passed the self-test. Proven non-vacuous with a throwaway mutant (return 2 -> 1 made the self-test fail). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
AmazingAng
added a commit
that referenced
this pull request
Aug 7, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
|
lgtm, merged |
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
2 participants
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.
This adds a small regression check for the fail-closed behavior discussed in #1. It verifies that the must-not scan passes only when grep returns "no matches", and still fails when the scan itself breaks. The goal is to make the negative-control behavior durable rather than relying only on the one-off validation recorded in evidence.md. No product-code changes and no new dependencies.