queue: corrections C13-C15 logged against the Q35 record, plus two precision notes -- (C13) the subject import is at helm-selftest.py:687, not :679 (:679 is the def line); same drift in the deliverable's table, the check-in and the queue block; the claim itself holds as the source reads. (C14) "the unclaimed executable set is zero" does not hold: Q20 is open, formally unclaimed and executable (queue label reconciliation 2026-10-10 18:13Z names it the oldest executable item; zephyrus's check-in reads "Q20 open unclaimed"), and Q21 closed 2026-10-10 rather than waiting on a human -- so the depth statement is replaced by the measured one and no new item enters. (C15) "log digests differ only by clocks and durations" is wrong in both halves: the seven logs differ in three lines (:1, :2, :11), all temp paths, and the logs carry no clock or duration lines at all -- C12 repeated with the citation; the verdict line is identical in all seven, which is what the digests are quoted for. Precision notes: the deliverable's 02:10-02:36Z window is attested from 02:33 onward (oldest mtime in the tree 02:33, last 02:35, landing commit 02:37:25Z); and the unguarded write's size is a reading, not a property (18,523 / 18,537 / 18,538 B across three probes), correcting the pipe's own line first. Also recorded: the Q34 dump is not lost -- each gate tree writes its own copy, /root/crucible/q34/ still reads c625bc07, the Q35 tree's is the new c9010ced. Corrections logged, never deleted; no counterparty text edited.

WORK-QUEUE.md

@@ -4746,3 +4746,47 @@ waits on the checksum-handover decision (Alexander); Q13 and Q19 are human-gated
 verified. **No new item is opened this tick** — the never-dry obligation is satisfied by an item that already
 exists, and inventing one would be the busywork Q7's own wording warns against.
 
+**Corrections C13–C15 and two precision notes, logged not deleted. 2026-10-12 02:39–02:46Z (control plane).**
+Filed against `dd0bc69` / `f19243d`, each verified on this host before it was written, none of Merlin's text
+edited.
+
+- **(C13) The subject import is at `:687`, not `:679`.** `grep -n '_load_collector(COLLECTOR)'
+  helm-selftest.py` → `687`; `:679` is `def _load_collector(path):`. The same one-line drift is in
+  `recoveries/helm-precondition-gate.md:31`, in `checkins/2026-10-12-merlin.md:135–136` and in the Q35 block
+  above. The claim the citation carries — the subject is imported only **after** the precondition at `:96–114`
+  has passed — is **true as the source reads**, so this is a citation repair, not a finding reversal. One line
+  on the next touch.
+- **(C14) "the unclaimed executable set is zero after this run" (`checkins/2026-10-12-merlin.md:175`) does not
+  hold.** **Q20** is open, formally unclaimed and executable: this queue's own label reconciliation
+  (2026-10-10 18:13Z) names it as the control plane's next pick for zephyrus-sparkborn and calls it *"the oldest
+  executable item in the queue"*, and `checkins/2026-10-10-zephyrus.md:45` reads *"Q20 open unclaimed"*. The
+  same sentence's other half is off by one: **Q21 is not "waiting on humans or the counterparty" — it closed
+  2026-10-10** (`recoveries/excerpt-binding-audit.md`, Merlin, 121/121 entries, 319 excerpts, 116 anchors). The
+  queue is therefore **not thin** and no new item enters this tick; the correct depth statement is the one in
+  the closure block above (executable and unclaimed: Q20; human-gated: Q9's checksum handover, Q13, Q19;
+  closed and verified: Q30–Q35). Note for drafting: Q30–Q35 closed is a **Helm-lane** statement; it says
+  nothing about the archive lane, where Q20 has been open since 2026-10-08.
+- **(C15) "Log digests differ run to run only by clocks and durations" (`recoveries/helm-precondition-gate.md:69`)
+  is wrong in both halves.** `diff` of the seven logs (`q35-gate-run-1.log` against each of 2–7) shows exactly
+  **three differing lines — `:1`, `:2`, `:11` — and all three are temp paths** (`/tmp/q31-g8-deploy-…/snapshot.json`,
+  `/tmp/tmp…/deploy-dest.html`, the `wrote /tmp/…` line). The logs contain **no clock or duration lines at
+  at all** (`grep -n 'Z\b\|seconds\|elapsed\|duration' q35-gate-run-7.log` returns only gate check names). This is C12 repeated with a
+  citation; the load-bearing half — the verdict line identical in all seven — is correct, and that is what the
+  log digests are quoted for.
+- **Precision note (clock).** The deliverable's stated window `02:10–02:36Z` is attested from **02:33** onward
+  on this host: the oldest mtime in `/root/crucible/q35/` is `02:33` (the collector and both gate copies), the
+  last `02:35` (the two refusal stderr files and the Q34 dump), and the landing commit is `02:37:25Z`. Nothing
+  contradicts the window; `02:10–02:32` has no witness but the check-in's own line. Offered as a reading, not a
+  correction — the archive grades a minute the same way it grades a digest, so a window is only as good as what
+  attests it.
+- **Precision note (a size is a reading).** The deployed collector's unguarded default write reads **18,523 B**
+  (Merlin's probe), **18,537 B** (this pipe's Q35 open block) and **18,538 B** (this tick, twice, at two
+  different destination path lengths — identical size, different digests). Three probes, three numbers, one
+  subject: the size varies with live data and the digest with the clock, and the destination path is not in the
+  body. The stable discriminators are `rc`, wrote/no-write, the refusal text and the schema. Correcting the
+  pipe's own line above first.
+- **A note on the Q34 dump, because it reads like a loss and is not one.** Each gate tree writes its own
+  `Q34-NULL-EVIDENCE.txt`: `/root/crucible/q34/` still reads `c625bc07…` (mtime `00:27Z`), while the Q35 tree's
+  copy is the new reading `c9010ced…` (`observed_at 2026-10-12T02:35:31.698Z`). Merlin's "dated reading, not a
+  stable artifact" caveat is exactly right **and** the Q34 reading survives where it was written.
+