Repository navigation
Retro: judge-local stale refusal, grep note, restate-text.py - #353
Merged
Merged
Conversation
problem-text.sh and db-sql.sh refuse a database missing the checkout's migrations; judge-local.sh only warned on stderr and judged the cases as they were, so a piped tail hid the warning and an old case was reported ACCEPTED. It now shares require_current_db: exit 2, or judge anyway with CODEBITE_ALLOW_STALE=1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
In this environment grep is a shell function running the claude binary as ugrep. On the 8 GB machine it was killed (exit 137) about ten times in one session, and a dev-branch-servers.sh migrate piped into it died too, leaving V582 unapplied. /usr/bin/grep and output written to a file worked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Step 2 asked every Example's Output to be the sample's expected output, but a Driver that prints a check (VALID, or k then the values) is exempt through DRIVER_PRINTS_ANOTHER_FORM; that was only found by reading the test, and #350's ticket proposed the wrong fix for it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A text-only Restatement retyped whole columns (description, constraints, English and Korean) to change a sentence. restate-text.py reads them as they stand and applies exact old-to-new replacements, refusing one not found exactly once or bringing in a $$; #350's seven Restatements were written this way. restate-problem step 3 points at it. 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.
Summary
Four changes to the agent environment from the retro on the statement cold-read and #350:
Evidence
judge-local.shagainst a database at V1 only printed a WARNING and judged the old cases (exit 0). In Statement cold-read 2026-11: fix 8 problems #350 a| tailhid that warning, and a corrected case was reported ACCEPTED against its old input.After: the new
judge-local.test.shcases pass: refused with exit 2, naming both versions andCODEBITE_ALLOW_STALE=1, which still judges.restate-text.test.pyhas 7 cases: both languages, edits in order, the_koname, a miss, a double match,$$, and a non-statement column. Run against the real database, it passes db-sql.sh's stale refusal through.run-script-tests.shandcheck-doc-references.pypass.Merge Danger
Door: two-way
Blast Radius: tooling
judge-local.sh <slug>now exits 2 on a stale database where it used to judge it.--casesmode is unchanged.🤖 Generated with Claude Code