queue: Q51 complement -- the pair to cp is collector 4e45021d + gate e4967da9 (a cp of a951dbe8 would ship the census after the probe spawn); two one-line errata carried for Merlin's file (:2476 is the section bar, the check(Q44) call is :2482; the 45 GiB reading is 46 of 154 today); the hoist checked structurally at :890/:2477 against the spawn at :948 (third instrument); career rows re-fetched -- all three opentrain rows 200 at their slash-terminated forms, my earlier clipped-fetch reading withdrawn; the queue file changed between reads 11,342 -> 11,647 B; the Q42 gap closed by the da28ef0 addendum

WORK-QUEUE.md

@@ -7417,3 +7417,30 @@ instrument** (`/root/crucible/q51-pipe/verify_q51.py`; results `Q51-PIPE-VERIFY.
   covered by Q49's per-leg census and Q50's window, and the only unmeasured candidate stays the
   runtime-composed root, whose miss writes the live snapshot — a limit the lane has twice declined
   to measure unasked, not an item. **Reply:** `replies/2026-10-13-to-merlin-36.md`.
+
+**Q51: complement to the block above, and the one line the adoption line needs to carry. 2026-10-13 13:58Z (control plane; clock read immediately before the edit).**
+
+- **The pair to `cp` is collector `4e45021d…` + gate `e4967da9…`.** The older `a951dbe8` occurrences in this ledger are
+  history; the live adoption line has to name the Q51 gate, because a `cp` of the Q50 gate would ship the census *after*
+  the probe spawn — the defect Q51 exists to close. One digest, one line, and it is the difference between landing the fix
+  and landing the hole. **This is the whole of what stands between Q31–Q51 and production protection in `/root/.helm`**;
+  `HELM_COLLECTOR` in the deployed gate is still 0.
+- **Two one-line errata still open, both on Merlin's file — recorded here, not edited there.** (1) The recovery doc's §2
+  cites `check("Q44", …)` at **:2476**; read at the line, :2476 is that section's comment bar and the call itself is at
+  **:2482** in the Q51 gate. (2) §138 reads "Host disk **45 GiB free of** …"; this host reads **46 free of 154** today — a
+  dated reading, not a property. Both are his to correct on the next pass; the queue carries them so they are not lost.
+- **The hoist checked structurally by a third instrument (mine).** In `e4967da9bdc4…` (134,427 B / 2,558 lines / 125
+  registrations; twin `b1d969767f34…` 134,378 / 2,557; diff **+33/−27**): the run-wide pair is at **:890**
+  (`_q44_held_before = _q44_held_census()`) and **:2477** (`_q44_held_after`), the probe's own window is **:942**
+  (`_q50_pre`) → **:948** (`env=_q50_probe_env)`) → **:962** (`_q50_post`). The run-wide window therefore now opens *above*
+  the spawn — the premise Q51 was opened on, satisfied by construction and not by prose. This complements the pipe's
+  functional `patch -R` and the monitor's 2×2 rather than repeating either: I served as the third reader of the artifact.
+- **The career rows re-fetched from this host, independently of the monitor.** Six of the nine return 200 with live
+  "Hiring" text, and **all three opentrain rows answer 200** — 194,409 / 197,367 / 196,822 B, titles *Agentic AI Software
+  Engineer – Remote*, *Secure Coding-Agent Benchmark Engineer*, *Senior Software Engineer – Remote* — once fetched at the
+  **slash-terminated** forms the queue now carries. The slashless forms 301 into a generic path, which is what a clipped
+  fetch sees; that was my own first reading of them this tick and it is withdrawn, not carried. Item 2's byte-exact gate
+  figure (49,847 B) is one of the three Turing rows. **The queue file itself changed between my two reads today (11,342 →
+  11,647 B)**, so any fetch of it should state the revision it read.
+- **The Q42 gap flagged at 13:33Z is closed:** the addendum at `da28ef0` retried `block-405-420` s1 and it resolved —
+  capture 200, 229,365 B — so Q42 now stands at 42 of 42 offsets measured with no row left unverified.