Repository navigation
feat(calibrate): --stamp marks variants as written against the shipped wording (0.2.14) - #136
Merged
Merged
Conversation
…d wording (0.2.14) `bouncer calibrate --stamp <question[,question]|all>` writes the question's fingerprint into its lines in fixtures/variants, which is what lets --gate ask them. A line already current is left byte for byte; a line stamped against another wording is stale, is left alone and fails the command until its question is named with --restamp. The eight draft lines for egress and outside_repo are rewritten for the wording 0.2.11 shipped. Nothing is stamped: all 28 are still the owner's to review. Refs #127 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Two things that unblock the polarity and rephrase parts of
calibrate --gate(#127): the stale variant drafts are rewritten, and there is a command to stamp a variant once it has been reviewed.calibrate --stamp--gateasks a reversed form or a rewording only when its line carriesbase, the fingerprint of the question it was written against. Abaseis a claim that someone checked the line still means what it should, so stamping is asked for by question name and does the least it can:base→ gets one;basealready current → the line is left byte for byte;basenames another wording → stale, left alone, and the command exits 1. Naming the question with--restampreplaces it.--restamprefusesall.Comments and every untouched line keep their bytes. The file is replaced atomically or not at all. The command prints the policy file it read before anything else, because with no
--policya personal~/.bouncer/bouncer.yamlwins, and stamping a repository's variants against one's own copy of the questions is the mistake to make visible.The redraft
The reversed form and three rewordings of
egressand ofoutside_repowere written against wording that 0.2.11 replaced (#129). All eight are rewritten for what ships. The file headers now point at--stampinstead of saying a loader will land.Nothing is stamped in this PR. All 28 lines are still unreviewed, so
--gateon the shipped files still reports polarity and rephrase as not evaluated.Checks
--gateon it: partial stamping measures only the stamped questions,allmeasures every row, a stale line survives until--restamp.bench --againstthe base bundle, six paired runs: medians −0.3 to +0.3 ms. Bundle 516.5 → 521.3 KB.No new attack surface. The command rewrites two files in a directory the user names.
Refs #127
🤖 Generated with Claude Code