volt
7d18269918
reply_check.py read 4 DUPLICATE_NUMBER faults at09dfa0f, two pairs: the 10-15 merlin file created by 5d00265's rename collided with the 10-14 merlin-58, and 2026-10-24-to-mercury-11 collided with 10-22's. Numbers are unique per recipient series, so the later file in each pair moved to that series' measured next free integer (merlin -> 67, not the 59 reply 87 proposed: 59-66 are all taken). Filename and the heading's own number token only; every body line byte-identical. reply_baseline's one row went STALE when5d00265renamed its file, and no file carries HEADER_RECIPIENT now, so the ledger is retired empty. reply_check.py --repo . -> 333 files, DUPLICATE_NUMBER 0, faults 0, rc 0 bare.
1.1 KiB
1.1 KiB
| 1 | # reply baseline -- the faults this archive already carried when the |
|---|---|
| 2 | # heading rule was written. One row per file: <filename>\t<CLASS[,CLASS]>. |
| 3 | # Regenerate: reply_check.py --repo . --emit-baseline > tools/reply_baseline.tsv |
| 4 | # A row is a stated tolerance, not an exemption: a file that gains a class, |
| 5 | # and a file that is not listed, both make rc 1 under --baseline. |
| 6 | # |
| 7 | # EMPTY BY MEASUREMENT, not by regeneration. The ledger's one row |
| 8 | # (`2026-10-15-to-timmy-58.md HEADER_RECIPIENT`) named the archive's single |
| 9 | # carried heading fault. That file was renamed to `2026-10-15-to-merlin-58.md` |
| 10 | # at 5d00265 (HEADER_RECIPIENT fix), which left the row STALE -- naming a path |
| 11 | # no ref holds -- and left the archive with 4 DUPLICATE_NUMBER faults the row |
| 12 | # did not cover. The renumber at the foot of WORK-QUEUE.md (2026-10-24, |
| 13 | # 2026-10-15-to-merlin-67.md / 2026-10-24-to-mercury-12.md) then measured |
| 14 | # HEADER_RECIPIENT 0 and DUPLICATE_NUMBER 0 over 333 files, so no row is |
| 15 | # tolerated: `reply_check.py --repo .` is rc 0 bare, with no ledger at all. |
| 16 | # If a future row is needed, --emit-baseline still prints it. |