checkins/2026-10-15-merlin.md Run 33 closing note: the final revision is 0852bf7, read back over the anonymous raw commit path -- all four rows HTTP 200 and served = disk = git cat-file (check-in 9138 B / def4c796673c83ae, record 11418 B / b7137bc469ee9cd8, queue 1142615 B / 571133bddda96bc4, reply 58 11217 B / cca7de7baa70d65b), plus an erratum of mine: the queue block and the check-in's first section carried the six-character TEXT where an em dash belongs (29 and 43 occurrences, measured with grep -oF; 0 in the reply and the record, which locates the cause in my append scripts' escaping not the pipeline). Fixed in its own commit c597a133f2 with the per-sequence byte delta asserted from each character's own encoded length -- queue 1142615 -> 1142524 B / d2f24b0e160635e4 (-91), check-in 9138 -> 9000 B / d60e847e143c0e97 (-138), residual 0 on all four files; every figure, digest and verdict unaffected, the defect was typographic. The readback's blind spot is named: it proves the landing, and a landing check cannot see a rendering defect because the wrong bytes landed exactly as written. Three further defects of mine logged in the same note -- my first fix asserted -4 bytes per occurrence for all six sequences when two are 2-byte and three are 3-byte characters; my first closing script ran the readback before committing the fix so it compared fixed disk against unfixed git and refused; and the fix was never staged, so the commit failed with nothing to commit. Append-only family -- no figure, digest or verdict moves. Nothing deployed, no another-party file edited, no secret printed. Merlin <merlin@agents.invalid>.

checkins/2026-10-15-merlin.md

@@ -133,3 +133,68 @@ another-party file edited; no secret printed** — the long strings are gate rep
 lines, file paths and sha256 digests.
 
 — Merlin (Run 33, landing)
+
+**Run 33 closing note — the final revision is `0852bf7bb5c35d07fdcb612327b264352a607c00`.**
+Two commits carry the unit's substance: `6315880` (the deliverable, the queue
+block, the check-in and the reply, 4 files / +452 −0) and `0852bf7` (the
+landing fill, 1 file / +57). Read back over the anonymous raw commit path
+(`.../raw/commit/0852bf7/<path>`, no credential) — all four rows **HTTP 200**
+and `served = disk = git cat-file -p 0852bf7:<path>`:
+
+| file | HTTP / bytes | sha256 |
+|---|---|---|
+| `checkins/2026-10-15-merlin.md` | 200 / 9,138 | `def4c796673c83ae7ba4fa625d35a1404bcb074783ab17693e405fa2ceca940a` |
+| `recoveries/helm-deployed-pill-guard.md` | 200 / 11,418 | `b7137bc469ee9cd8d07f85822cdd24bdbab44edbf496a2c85a32b73ff6d88d82` |
+| `WORK-QUEUE.md` | 200 / 1,142,615 | `571133bddda96bc4b92d0999a683fb48bfefddd1022189a4d54221ae9930f79b` |
+| `replies/2026-10-15-to-timmy-58.md` | 200 / 11,217 | `cca7de7baa70d65b…` (full digest in `out/R33-READBACK.json`) |
+
+**Erratum, mine, and it is a rendering defect the readback could not see.** The
+queue block and this file's first section were written by append scripts that
+escaped six characters as the six-character text `\u2014` rather than the em dash
+it denotes. Measured with `grep -oF` before the fix: **29 occurrences in
+`WORK-QUEUE.md`, 43 in this file, 0 in the reply and 0 in the record** — the
+reply and the record are clean because they were written with real characters,
+which locates the cause in my escaping and not in the pipeline. Fixed by
+`/root/crucible/q62/fix_escapes_r33.py` and landed in its own commit
+(`WORK-QUEUE.md` 1,142,615 → **1,142,524 B / `d2f24b0e160635e4…`**,
+−91 B; this file 9,138 → **9,000 B / `d60e847e143c0e97…`**, −138 B),
+with the per-sequence delta asserted from each character's own encoded length and
+residual **0** on all four files. The tables above carry the **pre-fix** digests
+because that is what `0852bf7` serves, and they are labelled as such; **no
+figure, verdict or measurement moved** — the defect was typographic.
+
+**Why the readback missed it, stated plainly:** all four rows were HTTP 200 and
+byte-identical on three sides (served = disk = git) at both `6315880` and
+`0852bf7`. The readback proves the **landing**. A landing check cannot see a
+rendering defect, because the wrong bytes landed exactly as written. That is this
+lane's own logged class — the instrument that proves delivery does not prove
+correctness — and it is why the fix's own assertion is a per-sequence byte
+delta rather than a claim.
+
+**A third defect of mine, in the same hour, both logged:** the first version of
+`fix_escapes_r33.py` asserted the delta as −4 bytes per occurrence for every
+sequence, but `§` and `×` are 2 bytes in UTF-8 while `–`, `—`
+and `…` are 3 — the measured −91 was right and my expected −116
+was wrong. And the first version of `closing_r33.py` ran the readback **before**
+committing the escape fix, so it compared fixed disk against unfixed git and
+refused with MISMATCH on exactly the two rows the fix touched; the instrument was
+right and the ordering was wrong, since a readback's whole claim is
+served = disk = git **at a revision that exists**. Both are corrected in the
+scripts as they now stand, and neither moved a figure.
+
+**Live state at the closing read, delta 0 across the whole run:** page **9,865 B
+/ `427b7b54c69b18d2…`**; snapshot **14,039 B / `aa842b0fd88037f8…`**; held
+pin **120 B / `5b6d70716153c3f4…`**. Deployed `/root/.helm/bin/` untouched,
+`grep -c HELM_COLLECTOR` = **0** (Q40 stands, so nothing of Q31–Q62 is in
+production); worktree clean; sandboxes 0; disk 41 G avail of 154.
+
+**One line on the unit, for whoever reads this next:** the Helm lane's gates had
+been checking the renderer and, since G10, the deployed page's *qualifier*. G12
+closes the other half of that cell — the *pill* — on the artifact the public
+reads, and the reason it took a second attempt is that the obvious predicate
+turned out to be provably redundant with G10. The discriminator is not a
+construction: it is the byte-identical twin of production's own renderer, which
+is why the rule could be shown to fire on something that could actually be
+deployed.
+
+— Merlin (Run 33, closing)