queue: Q44 closed and verified (gate 94,819 B not 94,716; live_delta and live_held_delta 0 on all 17 rows); three non-material errata; adoption pair = 4e45021d + 18580c10

WORK-QUEUE.md

@@ -6295,3 +6295,33 @@ Deliverable `recoveries/helm-root-redirect.md` (12,811 B / sha256
   audio handover, Q13/Q19 gated on Alexander, Q42 open and zephyrus's). No new item opened. The §4
   adoption is now a three-file ask: collector `4e45021d…` + gate `18580c1…`, with Q40's finding
   unchanged — the deployed gate `7ed1bca8…` has no subject-selection path at all.
+
+**Q44 closed; the discriminator holds; three non-material errata and one wording inversion recorded. 2026-10-12 21:08Z (control plane).**
+
+- **Q44's hard target is met and the lane has nothing executable left.** Gate `18580c10…` measures **94,819 B / 1,731
+  lines** (my `stat` and `wc -c` agree; the record's "94,716 B / 1,731 lines" pairs the **pre-`patch_gate2`** size with
+  a post-fix line count — the fix adds exactly +103 B / +2 lines). Collector still `4e45021d…`; deliverable
+  `recoveries/helm-root-redirect.md` 12,811 B / `e68be4cd…`; harness `out/Q44-NEGATIVES.json` 66,881 B with 17 rows.
+  My own receipt on the acceptance claim: **`live_delta` = {0} and `live_held_delta` = {0} across all 17 rows**, and
+  the five green runs are 12,966 B each with "169 passed, 0 failed" and `VERDICT: ALL GATES PASS`. Both live objects
+  re-measured now — snapshot 14,039 B / `aa842b0f…` / mtime_ns `1791479579475780303` / ctime_ns `1791789490146606356`
+  (that ctime is the trace of this lane's 07:18Z restore, recorded as such), held pin 120 B / `5b6d7071…` — and the
+  deployed `/root/.helm/bin/` is unmoved.
+- **Prevention is separated from detection by measurement, as the monitor re-derived it:** with the redirect armed,
+  `pinleg` exits 0 with 169 passed and its held file lands in the row's own sandbox; with it disarmed,
+  `pinleg-noredirect` exits 1 with 166 passed / 3 failed and the same shape lands in the protected root with a nonzero
+  ctime. I did not re-run those variants (the harness writes the JSONs the record rests on); the numbers are carried as
+  the monitor's, and my independent contribution is the zero-delta acceptance receipt above.
+- **Errata, none of which moves a measured number carrying the closure — Q44 stays closed, nothing is reopened.**
+  (1) the stale gate size above; (2) the diff decomposition "3 header + 133 added + 14 removed + 45 context" — my own
+  `diff -u` between the Q43 and Q44 gates counts **2 file headers + 6 hunks (8 header), 124 added, 14 removed, 40
+  context**; that pair is not the `patch_gate2` pair the record describes, so my added/removed figures are a different
+  object and stay labelled as mine, but "3 header" is wrong for any unified diff and the class of error is the same one
+  this lane corrected in its own C2 erratum; (3) the summary timing range "12.00–12.14 s" against the JSON's **11.95**
+  low. Plus one wording inversion: the check-in says `pinleg-noredirect`'s "live root stood in for the scratch root",
+  while the environment has the **scratch protected root standing in for the live root** in both variants.
+- **The only open lever remains Alexander's `cp`, and the pair is now collector `4e45021d…` + gate `18580c10…`.** The
+  monitor's phrase "three-file Helm pair" names two files; the bin also holds `helm-render.py`, `helm-validate.py` and
+  `summarize.py` unchanged, so the adoption I have verified is the two-file swap. If a third file is intended, the
+  order should say which. The deployed gate `7ed1bca8…` still has no subject-selection path, so none of Q31–Q44 is in
+  production until this lands.