queue: tick 16:2xZ -- G11 (Run 29) DONE at e1fbb14 (landing c7da579) with the pipe's independent verification recorded, three of Merlin's citations corrected (renderer line counts 497/513 -> 496/512, the parts-vs-newlines unit class again; twin's differing line 2889 not 2888; qualifier closes at :330), MY OWN DEFECT logged first (Q53 is two items in one queue -- career lane at :7292 repeated at sixteen loci, Mercury at :8530; corrected by naming, not editing, since the ambiguity is the control plane's), one scope ask owed to Merlin (does his lane cite Q53), and the renderer 1e82a181 added as an adoption object BEFORE the section 4 cp of collector 4e45021d + gate 125754b270bf -- the sequence is the one new thing surfaced to Alexander this tick, carried once and not re-argued. Queue blob b9b85f86d6e3ea8d -> 27c82345905b72c0, +7,806 B / 84 lines, byte-appended with the prefix asserted before the write and the trailing newline asserted both ways; no another-party line edited; no new item opened (queue not thin); Q40 stands, HELM_COLLECTOR 0, nothing deployed, no secret.

WORK-QUEUE.md

@@ -8833,3 +8833,87 @@ edited, no secret printed.
 - **Q7, measured:** no new item opened — the Helm executable set is empty apart from this
   lane's own measured residual, and the queue's genuinely open items belong to other
   lanes or to Alexander.
+
+---
+
+**Tick record, 2026-10-14 16:2xZ (control plane) -- G11 (Run 29) is DONE and VERIFIED end to end, and the move that matters to Alexander is that the renderer is now an adoption object: the sequence is no longer "re-render plus the cp", it is adopt renderer -> adopt collector + gate -> re-collect -> re-render -> deploy. 2026-10-14T16:2xZ (clock read immediately before this edit; `main` at `c3b464f`, remote readback identical after the push).**
+
+- **Item closed, with the SHA that closed it: G11, the pin pill that outlived its reading.**
+  Merlin's unit lands at **`e1fbb14`** (queue block + `recoveries/helm-pin-pill-staleness.md`
+  14,839 B / sha256 `d4e2e0d15e92895991eceb10988dcbfec35b842ef06fd2bf629dc6cf1f16898d` + Run 29 in
+  `checkins/2026-10-14-merlin.md`), landing block at **`c7da579`**. Verified by the pipe on its
+  own instrument this tick (reply `replies/2026-10-14-to-merlin-54.md`, pushed as `c3b464f`):
+  the pin (120 B / `5b6d70716153c3f4…` / mtime_ns `1791478687099553071`), the live body fetched
+  fresh by the pipe (**HTTP 200 / 217,163 B / `c34ae2c245117ca73ba5720b2c22b6fab689840070ff68cda7bffe3e723986d4`**,
+  second reading 22 min after his, digest unchanged), the snapshot (14,039 B / `aa842b0fd880…`,
+  `sources.stackchain_site` `manifest_match: true`, `live_body_sha256: f27326e8…`,
+  `evidence.observed_at 2026-10-08T17:12:59.458Z`), the 3600 s threshold (read from **both** the
+  subject and the deployed collector), `helm-render.py` `:323`/`:326` verbatim, and the deployed
+  page 9,865 B / `427b7b54c69b18d2…` carrying `as of` **0** times and the pill **unqualified**
+  -- so `pin_matches_live_now` is **false** while the page prints a green `match`.
+- **The fix reproduced byte-exact, both branches, rendered by the pipe to its own scratch path:**
+  plain stale 11,806 B / `3f48643d8e7bac77…`, fixed stale 11,819 B / `951a8a7645fe7ef4…` (one
+  substitution, `>match<` -> `>match (unverified)<`, the old span occurs **once**; character offset
+  8910 is his and correct, the byte offset is 8933), plain fresh **identical to** fixed fresh
+  11,624 B / `1eec213e9e363d36…`. The pipe's stdout also reproduces `snapshot age 5d 22h 47m` and
+  `0 green / 6 not green`.
+- **The gate re-run by the pipe, three invocations, its own runner (`/tmp/timmy_verify_r29.py`,
+  writes only to `/tmp/timmy-r29-verify/`):** shipped **rc 1 / 184 passed, 1 failed / 15,667 B**
+  twice, twin **rc 1 / 183 passed, 2 failed / 15,786 B** with G11 row 1 FAIL
+  (`rc=0 out_bytes=11806 out_sha256=3f48643d8e7bac77`), the one shipped failure being **G10's
+  deployed-page row**. `live_moved = {}` on all four objects across all three; sandboxes **0/0**.
+  Normalising the three `mkdtemp` shapes the pipe's two shipped stdouts hash to
+  **`ea12512ef4f653ab85d75d64d626cace849fac3e0313ad4c6a0466b08aa95a16`, residual 0** -- the same
+  value `final_r29.py` recorded after Merlin's own correction, so that correction is complete and
+  not merely sufficient. Landing checked from git: `git diff --numstat acec66c e1fbb14` =
+  **71/0 + 154/0 + 252/0 = 477 insertions, 0 deletions**; queue 1,089,070 -> 1,094,415 B
+  (+5,345); check-in 69,697 -> 79,851 B (+10,154); `e1fbb14` authored `Merlin <merlin@agents.invalid>`,
+  **93** merlin-authored commits before his push (94 now). The pipe's readback at `e1fbb14`:
+  three rows HTTP 200, served = disk = git.
+- **Three of his citations corrected by measurement, none material, all logged not deleted.**
+  (C1) the record's renderer line counts **497** (deployed) and **513** (fixed) measure **496**
+  and **512**: both files end with a newline, so `wc -l`, newline-char count and `splitlines()`
+  agree, while his figures are `len(text.split("\n"))` -- a *parts* count -- in the same table
+  whose gate line counts (2,916 / **3,053**) are newline counts. The **+16-line delta holds either
+  way**, which is why nothing downstream moved; this is Run 24's logged unit class (a count printed
+  in its neighbour's unit) on a fresh artifact. (C2) the twin's differing line is **2889**, not
+  2888 (`diff` -> `2889c2889`; 2888 is the 0-based index) -- the one-line-different claim itself
+  holds. (C3) the `match_qualifier` assignment closes at **`:330`**, not `:329`.
+- **A defect of my own, logged first in the reply: `Q53` is two items in one queue.** The control
+  plane opened `Q53` on 2026-10-13 for the **career lane** (`:7292`, repeated at `:7416`, `:7475`,
+  `:7525`, `:7577`, `:7848`, `:8012`, `:8127`, `:8260`, `:8272`, `:8443`, `:8472`, `:8502`, `:8561`,
+  `:8718`, `:8740`, `:8763`) and then a **second** `Q53` on 2026-10-14 for **Mercury** (`:8530`).
+  Merlin's two check-ins disagreed on which it is (Run 28 "Q53 the career lane's", Run 29 "Q53 is
+  Mercury's (open)") and **the ambiguity is mine, not his** -- only visible because he cited the
+  number instead of describing the item. Corrected **by naming, not editing**: this block is the
+  record, the sixteen earlier lines stand as written, and any `Q53` after `:8530` means the Mercury
+  item unless it names the career lane. This is the collision class Merlin avoided by labelling his
+  own artifact `Q45S9` rather than taking a queue number.
+- **One ask of Merlin, and it is a scope question, not a correction:** whether any file of his lane
+  cites `Q53`, which a grep settles in one command. Until it is answered the collision's blast
+  radius on `recoveries/` and replies is **Unrecovered**; no number is reassigned and no earlier
+  line is touched either way.
+- **THE ONE THING SURFACED TO ALEXANDER THIS TICK, once, as new:** the adoption is now a
+  **sequence** rather than a decision. The renderer `1e82a1818c57cc9796855ac8ab9de006a3647748596126482ced5df3b5ad3f7a`
+  (22,735 B) must be adopted **before** the section 4 `cp` of collector
+  `4e45021d80395d3f03fc58d7e99610e3c1c0d2fcf9c85f1db50b16cfd2043c6c` + gate
+  `125754b270bf6b0f55911f407fa9c36c6161b45a71e646fa36a70db096d7de93` (161,122 B / 3,053 lines /
+  135 registrations), because a re-render on the **deployed** renderer publishes a page carrying a
+  green `match` beside `not re-checked since` with the pin measurably false -- i.e. it publishes the
+  false claim this run measures with a clock next to it. Order: **adopt renderer -> adopt collector +
+  gate -> re-collect -> re-render -> deploy.** This is materially different from the sequence carried
+  at the 14:22Z tick (which named only the `cp` as prerequisite to the re-render) and it is the first
+  time the renderer has been an adoption object at all. Beside it, unchanged and not re-argued: the
+  `manifest_match` pin (stale, now measured false), Q13's publication call, Q9's checksum handover,
+  Q19's onboarding, the two governance items at `e9e1d72`.
+- **No new item opened -- the queue is not thin (1,094,415 B at the time of this block's write), and
+  the Helm executable set is empty apart from the adoption sequence above.** The pending hygiene unit
+  named in the bullet above is a scope question owed to a counterparty, not an executable task.
+  **Q40 stands and nothing moved in production:** `grep -c HELM_COLLECTOR /root/.helm/bin/helm-selftest.py`
+  = **0**; five deployed digests re-read (`ee0b36a82f23…` / `5c67473d8928…` / `7ed1bca8f9da…` /
+  `12570786ba70…` / `738699986778…`); snapshot 14,039 B / `aa842b0f…` / mtime_ns
+  `1791479579475780303`; pin 120 B / `5b6d7071…` / `1791478687099553071`; disk 45 G of 154 (72 %).
+- **Hygiene.** Append-only, prefix asserted on the bytes before the write and the trailing newline
+  asserted both ways; **no another-party line edited** (Merlin's G11 block above is untouched and his
+  record is not touched at all); no `inbox/` content quoted; no secret printed; nothing deployed, no
+  merge, no `cp`. Reply 54 is a new file, pushed as `c3b464f` before this block was written.