queue: Q49 recorded (name the argv that moved the live pin, or record the negative); 143 errata upgraded to a false provenance claim (grep -c returns 163); the 06:52Z cp recommendation withdrawn pending Q49

WORK-QUEUE.md

@@ -6848,3 +6848,30 @@ digests; the armed/disarmed pair on the discriminator.
 again and this is the one Helm unit that is not human- or counterparty-gated. Unchanged and unclaimed beside
 it: Alexander's `cp` of collector `4e45021d…` + gate **`a590170f…`**, the `manifest_match` pin stale since
 2026-10-08, and the Q13 publication call.
+
+**Q49 recorded; the 143 defect confirmed by a second instrument and upgraded — the record claims the count came from `grep -c`; and §6.2's attribution is contradicted by §7. 2026-10-13 07:11Z (control plane).**
+
+- **The 143 defect now has two independent instruments and is worse than a typo.** The pipe counted 163 on
+  `out/DIFF-vs-q47.txt` (8,300 B / `71c593e2954ecaf3…`) and I counted 163 in my 06:52Z block; the record's own text
+  says the number was "counted by `grep -c`, not asserted: added = `^+` minus `+++` = 143"
+  (`recoveries/helm-runtime-redirect.md:31`, repeated at :29 and :32, and `checkins/2026-10-13-merlin.md:322`). `grep -c`
+  on that artifact returns **163** — I ran it. So the record asserts a method whose output contradicts the number it
+  printed: the erratum is not "a component was mis-copied" but "a provenance sentence is false", which is the graver
+  of the two and the reason it is recorded here rather than folded into the earlier line.
+- **Q49 is open, and it is the right item.** The queue carries it at line 6826 — *The runtime-resolved root's live
+  write path: name it, reproduce it, then close it.* It exists because §6.2's causal claim (the gate's own
+  original-subject legs moved the live pin) is contradicted by §7.3/§7.4 and by the shipped-gate invocation with the
+  live root named: redirect fires, the Q43 check fails, `live_delta` 0, no restore. Until the exact argv is named, the
+  mechanism that moved `stackchain-home.html.sha256` is **Testimony**, not a measurement. §6.1 does name a candidate —
+  `make_fixtures_q48.py`'s `verify_interpreter()`, v1, ~05:5xZ — which is what Q49 should test first.
+- **The `cp` recommendation this lane gave at 06:52Z is withdrawn for now.** The protection itself is measured (armed →
+  the pin lands in the sandbox; disarmed → the guard restores byte-exact; `live_delta` 0 on both objects), but the
+  incident's mechanism is unattributed, so a `cp` today would land Q48 with its own §6.2 sentence unproven. Hold until
+  Q49 names the argv or records the negative measurement. Nothing is lost by waiting: the deployed bin is unchanged —
+  `7ed1bca8…`, `HELM_COLLECTOR` reads **0** — so none of Q31–Q48 is in production either way.
+- **One correction to the brief this lane was handed:** it reports live `main` as "4 commits past" the snapshot's
+  `abe1f0b`. Measured, `abe1f0b..HEAD` is **6** commits — `f1537be` (this lane), then `a0fbe0a`, `af3222d`, `2ff8bf3`,
+  `a59e640`, `5aa32b3` under the `Timmy` identity the pipe pushes with. Its other figure reproduces exactly: the
+  pre-append check-in blob at `20623b6` is 32,103 B / `6c6eeded…`, against 32,901 B / `014d86e3…` at `abe1f0b`.
+- Live pair re-read for this block: snapshot 14,039 B / `aa842b0f…`; held pin 120 B / `5b6d7071…` with `ctime_ns`
+  `1791873567284160583`; disk 46 GB.