Pass 13 ledger: two rows corrected against the tree, two filed
S8 carried a false mutation claim. It said flipping `is_none_or` to `is_some_and` at the constant-tempo check killed no test; three tests kill it — two in graph_reduction, one in convergence reporting the witness verbatim. Executed and restored by hand. The original was reached by reading only invariants.rs's own tests, which assert `fires(...)` and survive the flip; the kill sites live in another crate. The genuinely unconstructed spelling is the opposite one: `Constant` with `Some(equal)` has no construction site anywhere. S8's ratification also stops presenting normalize-on-encode as the default. Folding one of two accepted byte forms violates req:binfmt:decode-vectors' injectivity rule, and req:binfmt:compression-none-parameter is the ratified precedent for refusing exactly that leniency. A repair must reject one spelling or keep both as distinct canonical values. S16 had drifted in every code citation, some by hundreds of lines, and never named what makes its fix expensive: t8b_both_permitted_stale_forms_hold pins both stale forms as passing and documents disposition A's rules as mutations that must break it. The fix is the mutation an existing test exists to detect. S25 files disposition B of S22 — corpus rows named for their variant. Complementary, not a replacement: it reaches other implementations, but its failure still reads as corpus staleness. S26 files a doc comment claiming a core_spec repair that never landed. A P13-S9 instance, and the sharpest: the side that is wrong about the other is the grep-guarded side. Its evidence must not be repaired alone. Locators only in this commit; no code, no spec, no contract. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QjsEnYhm1gPpf6ii2iFxFV
This commit is contained in:
parent
a4d78471bb
commit
f90a5b1c29
File diff suppressed because one or more lines are too long
Loading…
Reference in New Issue