fix(judge): classify varied refusal wording - #5
Open
vsolano9 wants to merge 1 commit into
Open
Conversation
Keep secret and canary evidence as the sole crack boundary while recognizing additional common refusal phrasings for the held-result message. Cover straight and typographic apostrophes, generic no-leak output, and leak precedence. Closes AgentPostmortem#4
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.
Closes #4
Owner-truth clarification
Current
mainalready has the issue’s safer option-2 scoring architecture: only secret/canary evidence setscracked: true; bothrefusedandno-leakare held attempts worth zero points. This PR preserves that boundary and fixes the remaining player-message classification gap.What changed
Validation
npm run typechecknpm run lint— no warnings or errorsnpm run build— production Next.js build passedmainNo dependency or lockfile changes. The fresh install reports the existing 32-advisory baseline (24 production).