queue: Q41 erratum verified (0.229590, fifths rule printed, anchors reconcile at 116); D1 confirmed at ff32a44; disk 7.0 GB and not this lane's doing

WORK-QUEUE.md

@@ -5970,3 +5970,31 @@ finishing SHA is Merlin's `ff32a44` (erratum) + `fbb2562` (landing evidence), on
 - **Q7, measured:** Q42 open and offered to zephyrus; Q37 is the pipe's; Q9 (checksum handover), Q13 (the wording
   fixes), Q19 (wizard onboarding) and the Helm §4 adoption `cp` (collector `4e45021d…` + gate `9b09f328…`) stay gated
   on Alexander. The unclaimed executable set is not empty; **no new item opened this tick.**
+
+**Q41 erratum verified by independent recompute; D1 confirmed at the right ref; the disk is at 7.0 GB and nobody here did it. 2026-10-12 16:19Z (control plane).**
+
+- **The erratum's numbers hold under my own parse, not just the author's.** Deliverable `recoveries/excerpt-placement-nonmagazine.md`
+  = **38,817 B / sha256 `815222254935…`**, check-in **65,336 B / `52a8b89d139d…`**, queue **664,584 B / `293545d0c032…`**
+  — all three matching the landing evidence. Recomputed from the patched rows: **42 measured rows, mean 0.229590 →
+  0.2296**, min 0.0000, max 0.8048, fifths by the now-printed rule `min(int(f*5),4)` = **21/10/9/1/1**, rows with more
+  than one occurrence = **9** (the 8→9 correction), classes 30/5/7/4/4 over 50 rows. The fifths bucketing rule is now
+  printed in the deliverable, which closes the precision item this lane raised two ticks ago.
+- **The anchor census now reconciles, so my earlier flag is resolved rather than open.** Q41's 35 = 25 unique + 10
+  shared with the magazine 91, and the union is **116** — which is Q21's own census figure. The "10-anchor gap"
+  I recorded at 14:02Z was the symptom of the unlogged 25→35 revision, and the erratum both fixes the label and logs
+  the revision.
+- **D1 confirmed by my own read, at the correct ref.** `ff32a44:checkins/2026-10-12-merlin.md` = **63,646 B / sha256
+  `51772f9e7c76e474…`** and `fbb2562^` is `ff32a44`, so 63,646 is the pre-append revision the convention calls for.
+  The published Run 8 row instead cites **64,914 B / `f4110ada…`**, and that revision exists only in the author's own
+  scratch — `fix_landing_row.py`, `fix_landing_row2.py`, `fix_landing_row4.py`, `out/rb-checkin2.md`. A transient local
+  revision is therefore published as the committed one, in the row that vouches for the fix. D2 (the commit message
+  enumerates three read-back files where the table shows two) and D3 (the "0 malformed" line cites a class-summary
+  table that prints `malformed: 7`; the transition counts are 0→1 ×15 and 0→3 ×1) are carried as the monitor's
+  findings — I did not reproduce them locally. Q41 stays DONE; nothing is re-opened.
+- **Disk: 7.0 GB free of 154 GB, up from 866 MB at 14:23Z — and this lane did not free it.** The known reclaim classes
+  are unmoved: both pre-update zips still present (2.67G + 3.87G), the model cache still 11G, the music tree still 39G,
+  `/var/lib/docker` still 1.7G. So something outside this lane acted, and the record should say so rather than imply
+  credit. Consequence: the AI Lab cron and the forge's own CI are unblocked. Two writers are growing again —
+  `/root/.hermes/state.db` and a docker container `-json.log`, both past 100 MB inside two hours — and `/var/log` is
+  back to 574 MB with `syslog` at 255 MB. `stackchain-dashboard.service` is at `NRestarts=724,359` and has moved from
+  `activating` to **`failed`**, which is worth confirming rather than assuming benign.