queue: Run 36 (G14) re-derived here, with a process defect of my own caught before it published -- my first draft was anchored on my OWN previous block instead of the ledger's true last line, so it landed immediately before Merlin's G14 block at :9449 rather than at the tail; the insertion was uncommitted, so it was discarded with 'git checkout -- WORK-QUEUE.md' and re-applied against a tail read taken immediately before the anchor, nothing committed was edited or deleted, and the working tree at that moment hashed to c0264da97bd49360 -- byte-identical to the queue blob be55b95 cites in its own readback row, an independent corroboration of that row. Run 36's record holds to the byte: numstat 74/0 + 107/0 + 237/0 = 418/0; d503214 64/0 check-in only; append-only verified structurally (queue child starts with the parent's exact bytes, 1161042 -> 1166035 = +4993 B; check-in 32862 -> 39888 = +7026 B), so no line citation shifted; all three readback rows re-fetched anonymously at be55b95 (200 / 13678 / d92f5b7c, 200 / 39888 / b52a1558, 200 / 1166035 / c0264da9) served = git; provenance 111 merlin at be55b95 and 112 at HEAD. What moves for the decision is the payload: renderer a70998c8 = q65/helm-render-g14.py 22930 B / 514 lines supersedes 306d4bee (22731 B), gate 833d0827 = q65/helm-selftest-q65.py 190330 B / 3619 lines / 145 regs supersedes 6a887f42 (182752 / 3464 / 142) = +7578 B / +155 lines / +3 regs, collector 4e45021d unchanged, acceptance target now rc 0 / 195 / 0 with as-deployed rc 1 / 192 / 3 -- so the section 4 ask is a FOUR-file cp in one order and the file list must be re-read at adoption time. The /tmp/q31-g8-deploy-* leak measured here: 475 dirs, 12 MB total, newest 08:53:29Z holding one mode-600 snapshot.json (22892 B) -- a litter defect, not disk pressure (/tmp bytes are dominated by snap-private-tmp 4.8 G, q24verify 931 M, trailer_frames 429 M); disk 41 G free of 154 (74 pct), above the line where this profile's crons die; NOT cleaned because those trees are not this lane's and reclaiming them is section-4-class. Production re-measured: page = served = 9865 / 427b7b54 with mtime frozen 2026-10-11T08:57:14Z, snapshot 14039 / aa842b0f, pin 120 / 5b6d7071, live body 200 / 217163 / c34ae2c2 against pin f27326e8 so the published match is false today (G14 row 1), five deployed-bin digests unchanged, HELM_COLLECTOR 0 -> nothing of Q31-G14 in production. Vincent route still dead, PR #77 residual still verified-but-unowned, no fallback opened without a decision.

WORK-QUEUE.md

@@ -9519,3 +9519,14 @@ another-party file edited, no secret printed.
   `grep -n 'def pin_stackchain' /root/crucible/q48/helm-collect.py` →
   `664:def pin_stackchain():`; Run 35's record cited the older `647–662`
   span.
+
+---
+
+**Run 36 (G14) re-derived here: the record holds to the byte, the adoption payload has moved again, and the `/tmp` leak it discloses is measured — small, and not a disk risk. 2026-10-15 09:01Z (control plane; clock read immediately before this edit, and the tail read immediately before the anchor).**
+
+- **First, a process defect of my own, caught before it published and fixed rather than logged:** my first draft of this block was applied with the anchor taken from my *own* previous block instead of from the ledger's true last line, so it landed **immediately before Merlin's G14 block at `:9449`** rather than at the tail — the exact rule this lane keeps restating, broken by me five minutes after writing it. The insertion was **uncommitted**, so it was discarded with `git checkout -- WORK-QUEUE.md` and re-applied here against the tail read above; nothing committed was edited or deleted, and the working tree at that moment hashed to `c0264da97bd49360…` — byte-identical to the queue blob `be55b95` cites in its own readback row, which is an independent corroboration of that row.
+- **Every checkable sentence of Run 36 reproduces.** `be55b95` numstat = 74/0 + 107/0 + 237/0 = **418/0** ✓; `d503214` = 64/0 on the check-in alone ✓. Append-only verified *structurally*, not by claim: the child blob of `WORK-QUEUE.md` starts with the parent's exact bytes (1,161,042 → 1,166,035, **+4,993 B**) and so does the check-in (32,862 → 39,888, **+7,026 B**), so no line citation shifted. All three readback rows re-fetched **anonymously** at `be55b95`: 200 / 13,678 B / `d92f5b7c…`, 200 / 39,888 B / `b52a1558…`, 200 / 1,166,035 B / `c0264da9…` — served = git ✓. Provenance **111** merlin-authored commits at `be55b95`, **112** at HEAD ✓ (the record's count is the cited revision's).
+- **What moves for the decision is the payload, not the finding.** The candidate renderer is now **`a70998c8…` = `/root/crucible/q65/helm-render-g14.py`, 22,930 B / 514 lines**, superseding `306d4bee…` (22,731 B) which earlier blocks and briefs named; the candidate gate is **`833d0827…` = `q65/helm-selftest-q65.py`, 190,330 B / 3,619 lines / 145 registrations**, superseding `6a887f42…` (182,752 / 3,464 / 142) = **+7,578 B / +155 lines / +3 registrations** ✓. Collector `4e45021d…` (29,954 B / 720) is unchanged. **Acceptance target is now rc 0 / 195 checks / 0 failures**, with the as-deployed state at rc 1 / 192 passed / 3 failed (G10 deployed page, G13 row 2, G14 row 1). So the §4 ask is a **four-file** `cp` in one order — renderer `a70998c8` → collector `4e45021d` + gate `833d0827` → re-collect → re-render → deploy — and the file list must be re-read at adoption time, never copied from an earlier block.
+- **The `/tmp/q31-g8-deploy-*` leak, measured on this host rather than relayed:** **475 directories, 12 MB total**, newest `/tmp/q31-g8-deploy-cfkvskma` (mtime 08:53:29Z) holding exactly one mode-600 `snapshot.json` (22,892 B). It is a **litter defect, not disk pressure** — `/tmp`'s bytes are dominated by other things entirely (`snap-private-tmp` 4.8 G, `q24verify` 931 M, `trailer_frames` 429 M, `skills-eval` 388 M). Disk **41 G free of 154 G (74 % used)**, comfortably above the line where this profile's crons die. **Not cleaned:** those trees are not this lane's and reclaiming them is a §4-class action needing authorization, so the leak stays disclosed with its true size beside it.
+- **Production re-measured first-hand, unchanged and still showing the defect:** deployed page = what the public is served (`https://alexanderwhitestone.com/helm/` returns 200 / **9,865 B / `427b7b54…`**, byte-identical to the file), mtime frozen at **2026-10-11T08:57:14.017837233Z**; snapshot 14,039 B / `aa842b0f…`; pin 120 B / `5b6d7071…`; live body **200 / 217,163 B / `c34ae2c2…`** against the pin `f27326e8…` → **the published `match` is false today**, which is exactly what G14 row 1 goes red on; five deployed-bin digests unchanged; `HELM_COLLECTOR` **0** in all five, so nothing of Q31–G14 is in production.
+- **Nothing executed, and the outbound route is still dead:** the Vincent contract from 08:37 remains **undelivered** (provider HTTP 401; re-auth is Alexander's call), so PR #77's import-path residual stays verified-but-unowned, and no fallback route was opened without a decision. No item closed, none opened; no another-party file edited; no secret printed.