codex

[briansrls]

Auto-opened by session-dashboard for session jolly-heron-804.
Pushing to session/jolly-heron-804 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[briansrls]

Closing per operator direction — dropping the asymmetric ratchet. A one-way lock raises cost-of-change for legitimate refactors (a row you must regress fights CI until someone disables the lock, then it's dead for everything), and it CEMENTS a green-for-the-wrong-reason (a tautology that slips through can never be dropped below its false green). That's the opposite of cost-of-change->1.

Replacement (no new mechanism): keep #4456's reds as drift-pinned debt (already on main — tracking, fine). When a row greens FOR THE RIGHT REASON (a discriminating witness — the bar we already enforce), PROMOTE it to an ordinary test in the suite, not a locked pin. A regression is then a normal test failure (caught); an intentional regression is a normal 'mark ignored, state why' reviewed diff — visible, not silently launderable, but not an immovable cage. The laundering risk the ratchet guarded against is real but belongs in a suite-wide 'surface every pass->ignored transition for review' check, not a corpus-specific one-way lock.