queue: Q47 verified (gate 76f2292b 115,182 B / 2,124 lines; diff 130 = 2+4+96+4+24; 21/21 rows delta 0; declared green digests now byte-match the .out files); E6 confirmed at legacy/q39:273 and already logged at 6668; pair 4e45021d + 76f2292b

WORK-QUEUE.md

@@ -6669,3 +6669,34 @@ Verified on a second instrument written from scratch (`/root/crucible/q47/timmy-
 - **E5 residual — the superseded figure is still unannotated in his text.** `checkins/2026-10-13-merlin.md:27` (Run 12's section) reads "2,032 lines / 109,643 B" with no pointer to the correction every other locus now carries. Counted: that file **1 × `110,509` / 1 × `109,643`**; `recoveries/helm-read-path-guard.md` **1 / 0**; this queue **12 / 10**. His file, his call to annotate; logged here so the number does not survive unnoted.
 - **Receipts.** `branch-head` = `head` = `1b3d7a44da46`; the monitor's moved paths 3/3 hash-identical to `git rev-parse HEAD:<path>`. Loopback API: one branch (`main`), **0 open PRs**, `private: false` / `internal: false`. Deployed gate `/root/.helm/bin/helm-selftest.py` `7ed1bca8…` with `grep -c HELM_COLLECTOR` = **0** — Q40 stands, so the §4 `cp` (now collector `4e45021d…` + gate `76f2292b…`) remains the only path into production. Nothing deployed, nothing published, `decisions/` and `inbox/` untouched, no counterparty file edited, no secret.
 - **Q7, measured: no new item opened, and the reason is stated rather than implied.** The Helm lane's executable set is empty again and the one follow-on both records name — resolve every path the subject declares **at runtime**, not only the literals it declares statically (Q44 limit 1, Merlin's Q45 §9) — is held as a **limit**, not a measurement, so opening an item on it would be opening on a hypothesis. Its measurement is also the one this lane will not take unasked: a subject that composes its live destination at runtime is aimed at `/root/.helm/data/snapshot.json` (14,039 B / `aa842b0f…`), and a miss writes the live file, after which a restore would move the `mtime_ns`/`ctime_ns` values three records cite as deltas. **Named, unclaimed, with the missing measurement named.** No lane is dry: Q42 is zephyrus's, Q9/Q13/Q19 are Alexander's, and the `cp` is the same human call.
+
+**Q47 verified independently; E6 confirmed at the cited line and already logged; the adoption pair is now collector `4e45021d…` + gate `76f2292b…` — and the gate has stopped moving. 2026-10-13 04:11Z (control plane).**
+
+- **Q47's figures reproduce on my own reads.** Gate `76f2292b9a6cad08…` = **115,182 B / 2,124 lines** (`len` and `stat`
+  agree); my `diff -u` against Q46 gives **130 = 2 file + 4 hunk + 96 added + 4 removed + 24 context** with
+  **2,032 + 96 − 4 = 2,124 exact**, and **zero** added or removed lines touch `check()` or the 169 count — the diff
+  convention this lane had to correct twice is now applied correctly by the lane that writes the gates. Collector
+  byte-identical `4e45021d…`; landing rows at the revision they cite: `recoveries/helm-read-path-guard.md` 12,821 B /
+  `5bf9ba11…`, `WORK-QUEUE.md` 774,704 B / `30d735ef…`, check-in 20,685 B / `88670dbf…` (and 22,715 B at the fill
+  commit `1b3d7a4`, matching the record's self-hash note).
+- **The acceptance claim holds on my count.** `Q47-NEGATIVES.json` 57,247 B / `f542adbb…` = **21 rows**, `live_delta` =
+  0 and `live_held_delta` = 0 on **21/21**. `Q47-GREEN.json` 2,725 B declares five stdout digests — `21920260…` /
+  `58002175…` / `49025d65…` / `c8155f07…` / `1d2c7d69…` — and those are **byte-exactly the five `.out` files on disk**,
+  13,312 B each, "helm-selftest: 169 passed, 0 failed". That is the Q46 defect, not repeated.
+- **E6 confirmed at the line it names, and already logged.** `legacy/q39/helm-selftest.py` (77,704 B / `9b09f328…`)
+  reads at :273 `_q39_tree = _q39_ast.parse(_q39_src_text)`, catches `SyntaxError as _e` at :274, sets `_q39_tree =
+  None` and appends `("parse", "-", "the subject does not parse: …")` at :275–276, then continues. So Q39 **does**
+  compile the subject's text and the "never compiles" sentence is false in all three loci. The class is what a gate
+  does *with* a failed parse — record-and-continue, dereference, or re-import the decoded text — which is the
+  distinction Q47's fix turns on. No acceptance claim moves. The queue already carries this as E6 (three mentions; the
+  note is at line 6668 and names the same three loci), so **nothing is appended here and no duplicate is written**.
+- **The gate has stopped moving, which is what makes the ask actionable now.** The §4 pair is collector `4e45021d…` +
+  gate **`76f2292b…`**, the first name today that is not already superseded: `18580c10…` → `2bbca218…` → `ae69d5dd…` →
+  `76f2292b…`, four in roughly twenty-six hours, because each new item rebuilt the gate. Q46 and Q47 are now both
+  closed and the lane's executable set is empty, so a copy lands the settled head rather than mid-flight work; the
+  collector has been stable across Q33–Q47. The two smaller standing calls — the `manifest_match` pin, stale since
+  2026-10-08, and the Q13 publication call — are what else keeps the lane parked.
+- Deployed bin unchanged: `helm-selftest.py` 33,647 B, `HELM_COLLECTOR` reads **0**, so none of Q31–Q47 is in
+  production. Live snapshot `aa842b0f…` / 14,039 B unchanged; held pin `5b6d7071…` / 120 B unchanged; disk 46 GB. The
+  check-in's Run 12 section still prints 109,643 B for the Q46 gate (line 27) — that file is Merlin's, and annotating
+  it is his call, so this lane does not touch it.