queue: Q52 complement -- the Q52-READBACK.json holds revision 6954cc6 (its check-in row 67,347/912985e3) while the table cites c559d33's 65,145/d89b2189, both true, so read the artifact's revision before comparing; live delta 0 is a net end-state with two disclosed transient pin movements (Q45's class); the twin is 25 B larger because :854 turns an assignment into a comment, inverting the Q50/Q51 pattern; verified 126 registrations, diff -3/+122, 2558+119=2677, DIFF artifact 8299 B/169 lines; adoption line already reads 78b290ec at :7651/:7700

WORK-QUEUE.md

@@ -7700,3 +7700,33 @@ unchanged and its note does not conflict with its `proposed_action`.
 not a task: the §4 adoption `cp` (collector `4e45021d…` + gate `78b290ec…`), the stale `manifest_match` pin,
 Q13, Q9, Q19, Q42 — all Alexander's or a counterparty's. Open set otherwise unchanged: Q52 (Mercury's),
 Q53 (career lane, held for Alexander).
+
+**Q52/Run 18: three things the verification block above leaves open, and one standing ask that now has a new digest. 2026-10-13 16:27Z (control plane; clock read immediately before the edit).**
+
+- **The readback artifact is a *different revision* than the table it is cited for.** `out/Q52-READBACK.json`
+  (`b0f745879671…`) carries `read_at 2026-10-13T16:09:11Z` and **`"revision": "6954cc6"`** — so its third row is
+  **67,347 B / `912985e3…`**, while the guard doc's table cites **65,145 B / `d89b2189…`**. Both are true: the check-in is
+  65,145/`d89b2189…` at `c559d33` and 67,347/`912985e3…` at `6954cc6`, and I read the guard three ways at all three
+  revisions — worktree, `git cat-file` at both commits, and the anonymous raw path all agree on 13,173 B / `3f813ca2…`.
+  Nothing is wrong; what is missing is the pairing. **An auditor comparing the table against that artifact will see a
+  2,202-byte "mismatch" that is only a revision difference** — so read the artifact's `revision` field before comparing,
+  which is the mutable-metadata rule applied to a readback file.
+- **"Live delta 0 across the whole run" is a net end-state, not an absence of movement.** Two of the 21 invocations
+  deliberately moved the live pin mid-run before the guard restored it byte-exact. The honest phrasing — and the one that
+  keeps Q45's integrity event from looking like an accident that can't recur — is **net zero with two disclosed transient
+  movements**. Both live objects now read ctime_ns `1791907371554631194`; bytes, sha256 and mtime are unchanged
+  (snapshot 14,039 B / `aa842b0f…` / mtime_ns `1791479579475780303`; pin 120 B / `5b6d7071…` / `1791478687099553071`).
+- **This twin is *larger* than the gate it disarms, which inverts the Q50/Q51 pattern.** `be7b306a…` is 140,390 B against
+  the gate's 140,365 B, and the reason is the single differing line, :854: `_env[_v] = _home` becomes
+  `pass  # Q52 disarmed: the redirect is cut` — a comment where an assignment was, so the disarmed cell costs bytes. In
+  Q50 and Q51 the twin was smaller. One line differs, exactly, and it is the line that carries the fix. What I measured
+  myself: **126** registrations (Q51's 125 + one), diff **−3/+122**, `2,558 + 119 = 2,677` exact, `out/DIFF-vs-q51.txt`
+  8,299 B / 169 lines.
+- **Already carried by the pipe, so not repeated here:** the adoption line reads collector `4e45021d…` + gate
+  **`78b290ec…`** at :7651 and :7700; the two text defects (`caff1f50…` cited as evidence in three places though no
+  artifact records it, and the one-character subject cite) are logged in reply 37 and at :7683; the Q52 double-naming is
+  surfaced; and the check-in's 67,347 row is recorded.
+- **Standing, then, and unchanged in substance: the §4 adoption `cp` of collector `4e45021d…` + gate `78b290ec…` into
+  `/root/.helm/bin/`** — `grep -c HELM_COLLECTOR` is still **0** in all five deployed files, so none of Q31–Q52 is in
+  production — the **stale `manifest_match` pin**, and **Q53, the career lane, held for Alexander**. No sandboxes left;
+  disk 46 GiB free of 154.