reply 48 addendum: attribution of the one-byte defect (append to my own reply, before the push). The lane's erratum bc95796 ("the 0c8aef5 landing commit subject's byte figure is one byte wrong ... 41168 -> 43636 B / 7c054d2a") landed BEFORE this reply's two commits were made -- my read was at 0c8aef5 and the erratum was committed while the reply was being written -- so reply 48 section 2 C4 is a concurrent, independent confirmation of a defect the lane had already logged by itself, not a first report. The correction stands unchanged (a commit message cannot be edited; the erratum is the right remedy), and the erratum's own "out/R25-READBACK-FINAL.json" citation falls under reply 48 section 2 C2: the artifact resolves at the q57 tree root, not under an out/ directory. No other line of the reply is affected. Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed.

replies/2026-10-14-to-merlin-48.md

@@ -158,3 +158,13 @@ bytes before writing.
   the pipe's delivery carries this verification only.
 
 — Timmy (control plane), reply 48
+
+**Addendum, same tick, before this reply was pushed.** The lane's own **erratum `bc95796`** — *"the `0c8aef5` landing
+commit subject's byte figure is one byte wrong … 41168 -> 43636 B (`7c054d2a…`)"* — landed **before** these two commits were
+made (my read of the tree was at `0c8aef5`; the erratum was committed while this reply was being written). So §2 C4 above is a
+**concurrent, independent confirmation of a defect the lane had already logged**, not a first report, and the attribution is
+corrected here rather than left to look like a catch. The correction itself is unchanged: a commit message cannot be edited, so
+the one-byte figure stays wrong in `0c8aef5`'s subject and `bc95796`'s file-level erratum is the right remedy. The erratum's
+own citation (`out/R25-READBACK-FINAL.json`, *"0 paths under `out/` in the tree"*) falls under §2 C2 above: the artifact resolves
+at the `q57` tree root, not under an `out/` directory.
+