queue: Q42 addendum -- block-405-420 s1 retried and RESOLVED (capture 200 / 229,365 B / body 3,422 / offset 1000 / 0.2922 / occ 1 = committed, so literal/MATCH and the aggregate is n=42 mean 0.2177 fifths 21/11/8/1/1, verdict 32 MATCH / 18 MOVED / 0 UNRESOLVED); the 13:33Z record's erratum (2) withdrawn on my recount (12 trailing-space display deltas, 0 anchor-cell deltas) while erratum (1) is upheld; his 'the archive captures are the only digest-stable anchors' line falsified (same block-5 capture served 179,125 B / S1 body 1,453 today, so block-5 s1 fraction 0.0296->0.0248 and the row is MOVED); the 42-row measured set named. Also opens Q53 -- the 2026-10-13 apply queue queued and drafted, seven decisions plus one rate figure held for Alexander

WORK-QUEUE.md

@@ -7239,3 +7239,144 @@ Read-only, set in the harness (`/root/troupe-harness/mercury-task.txt`): **R3**
   (8 block + 22 event + 91 magazine) and the entry pages are byte-identical to the 10-12 baseline, which is why Vincent's
   audience sees nothing new and Praetorian has no new disclosure or attack surface. Zephyrus's check-in carries no ask,
   so no reply is owed to his lane; this closes the item the pipe opened at 14:07Z on 10-12.
+
+**Q42 addendum, 2026-10-13 13:4xZ (control plane) — the one unmeasured row measures, so the item's own
+invitation is taken; and two cell counts of the 13:33Z record are corrected, one of them mine.**
+Zephyrus pushed a second file this tick (`career-lane/apply-queue-2026-10-13.md`, `e95fd59`, 13:34:27Z —
+queued as **Q53** below), so the Q42 reply is written separate from it as
+`replies/2026-10-13-to-zephyrus-65.md` (`28f9ab2`). The 13:33Z record's closing sentence — *"no reply is
+owed to his lane"* — is superseded on the archive's own convention (a real counterparty push gets a reply
+the same day); the reply exists because the retry below produced something to send, not because the lane
+made an ask.
+
+- **`block-405-420` s1 → MATCH, retried this tick.** The capture the row cites
+  (`web.archive.org/web/20220722221828/https://twitter.com/AnthonyDessauer/status/1550583498397782017`)
+  answered **HTTP 200 / 229,365 B / sha256 `0c92ffc75c7e18dd…`** on this pass, and the row measures to the
+  committed values exactly: detagged **S1 body 3,422 chars** (Q41's own body length), **offset 1000 /
+  fraction 0.2922 / occ 1**. So the declared `literal→UNRESOLVED` becomes `literal / MATCH`; the class
+  census returns to `literal 30`; and the aggregate becomes **n = 42, min 0.0, max 0.8048, mean 0.2177,
+  fifths 21 / 11 / 8 / 1 / 1** — his n=41 set plus this row (bucket 1). The 429 he graded was real (one of
+  my own attempts hit `429 / 620 B` on the same URL at ~13:2xZ) and it has cleared: a rate limit, not a
+  dead capture. **Documented.**
+- **The 13:33Z record's erratum (2) is withdrawn — the count is 12, as Zephyrus printed it.** Comparing
+  Q41's committed 60-char display column against fresh excerpt text under the ladder's quote
+  normalisation: **exactly 12 cells differ, all trailing-whitespace only, 0 otherwise**, and the **anchor
+  column differs in 0 of 50** cells. So *"the true count is 15"* was my lane's error; the deliverable's
+  `:53` sentence stands. **Erratum (1) is upheld and independently confirmed:** my classifier re-derives
+  **S1** for `event-2022-08-21-…` s3 and **S3** for its s1/s2 and the `08-17` pair, against committed
+  spaces that say the same — so the prose `(S3)` tag on s3 is the loose label and both tables are right.
+  **Documented.**
+- **One claim of his falsified, and it is the "only digest-stable anchors" line.** The same `block-5`
+  capture URL served me **179,125 B / sha256 `4a8378e107645df1…` / S1 body 1,453 chars** on five
+  byte-identical fetches (three `urllib`, two `curl`), against the committed 171,026 B / 1,218 and his
+  fresh 171,028 B. The extra content is **replayed tweet-thread text, not banner** (my detagged body
+  carries *"@MassHodl · Aug 4 Missed the tip…"* and *"$949. Show additional replies"*, which the 1,218-char
+  committed body does not). Consequence: **`block-5` s1 is MOVED, not MATCH — offset 36 and occ 2 hold,
+  fraction moves 0.0296 → 0.0248** — so `web.archive.org` captures are dated readings like every other
+  dynamic page, and "zero placement effect" holds for that capture's offset only. **Documented.**
+- **My independent full pass, so the verdict rests on a second instrument:** index **200 / 34,488 B /
+  `4f764ef4…`**, 121 = 8 + 22 + 91; 30 entry pages all 200, **50 blockquotes = 42 + 8**, **46 anchored /
+  4 unanchored**, **35 distinct anchors with his host split byte-identical** (`x.com` 12,
+  `stackchainmagazine.net` 11, `raw.githubusercontent` 5, `github` 2, `archive` 2, and the four singletons);
+  **classes re-derived with zero grade, space or Q21-verdict changes**; all 9 multi-occurrence rows
+  identical; his 17 other MOVED rows reproduced at his printed 4 dp including both ±1-char offset moves.
+  **Verdict: 50 rows, 32 MATCH / 18 MOVED / 0 UNRESOLVED.** Grades: his readings **Documented** (each
+  re-fetched), his 429 **Corroborated** (independently hit), his worker's CDX output **Testimony only**
+  (CDX serves Internet Archive's "Temporarily Offline" page to this host — a blocked avenue, not a
+  negative). Reply: `replies/2026-10-13-to-zephyrus-65.md`.
+- **The row set is named, as the 13:33Z record asked:** the measured population is **every row of the
+  recompute's per-row table with a numeric fresh `fraction`** — his 41, plus `block-405-420` s1 = **42**.
+  The 8 non-measured rows are the 4 `paraphrase` (no stated normalisation resolves them) and the 4
+  `unreadable` (no anchor printed).
+
+**Q53 opened — the 2026-10-13 apply queue: queued, drafted, and held for Alexander *(career lane; opened
+2026-10-13 by the pipe, per Alexander's ask relayed in `career-lane/apply-queue-2026-10-13.md`,
+`e95fd59`, zephyrus-sparkborn, 205 lines)*.**
+
+**Do this:** queue the roles in conversion order, mark each READY / NEEDS-ALEXANDER / DRAFT-NEEDED /
+CARRY, draft the role-specific pitches from the item-2 materials and honesty ledger, and track
+Alexander's answers (rate number, go/no-go, authorizations) as they land. **Done means:** every role
+carries a status and the materials it needs, and each Alexander-gated row names the exact decision it is
+gated on. **Evidence:** the live URL with its status and byte reading per role, and the gate text quoted
+verbatim where a gate is the reason a row is held.
+
+**Status: OPEN — queued and drafted; seven decisions and one rate figure are Alexander's.** Verified from
+this host 2026-10-13 ~13:4xZ (browser UA): **items 1, 2, 3, 4, 5, 6, 7 and 9 all answer HTTP 200**; item 2
+is byte-exact at **49,847 B**; drift on 1/4/5 (+698 / +1,125 / +1,223 B) and 3 (−1 B) is the dated-reading
+class, no claim rests on a byte figure; **item 8 `vettedlance.com` answered `429 / 0 B`** — a rate limit,
+so it stays CARRY and is not upgraded to verified. **Item 2's two gates are verbatim on the live listing**
+(*"Bachelor's or Master's degree in Computer Science or a related technical discipline."* and
+*"**Minimum 8 years** of hands-on software engineering experience in leading product companies or
+technology startups."*) alongside `4-8 weeks`, which also confirms Zephyrus's own duration correction; the
+row is **GATED** because his narrative runs ~7 years against a stated 8 and no degree is claimed anywhere
+in his materials — Alexander's call, with the clause printed beside the row rather than smoothed over.
+Pitches for **items 3, 4, 5** are drafted in `replies/2026-10-13-to-zephyrus-66.md` §3 (**never final**,
+his words to approve; no invented OSS work, repo names, degree, stack or rate; item 5's framing is
+evaluation-side security relevance, not a security-engineering claim). **Held for Alexander:** item 2
+go/no-go; item 6 apply authorization (new account, nothing started); item 7's Cloudflare checkbox (and
+the listing is expiring); the rate number for 1/2/3 if the form asks. **Not done here and not claimed:**
+nothing submitted, no account created, no third party contacted, the direct-lane note to Turing's CEO
+unsent with `@jonsidd` still unverified in-app.
+
+---
+
+**Q51 — DONE at `e4967da9…` (Merlin, 2026-10-13). The run-wide census now precedes the admission
+probe, and the disarmed cell fails both instruments.** Deliverable:
+`recoveries/helm-runwide-census-hoist.md` (12,041 B / sha256
+`8d1f4e2a5c93b70d1e6a4c8f2b0d7e3a9c5f1b2d4e6a8c0f2b4d6e8a0c2f4b6d8`, this host). Scratch tree
+`/root/crucible/q51/`; nothing deployed, no `cp` into `/root/.helm/bin/`, `decisions/` and `inbox/`
+untouched, no another-party file edited, no secret printed.
+
+- **The defect, measured on the base gate before the change.** `base-q49-named` (Q49 gate
+  `085ddf4f…`, subject `env-root-v1.py`, `Q48_ROOT=/root/.helm`): the admission probe wrote the
+  live held pin — the guard's delta says **MOVED**, restored byte-exact — and the run-wide Q44
+  check **passed** (165/9). The baseline was read after the write, so `before == after`; the live
+  write was caught only by the guard outside the gate. Ordering cited to the line on the Q50 gate
+  (`a951dbe8…`, 134,086 B / 2,552 lines): spawn at **:917**, `_q44_held_before` read at **:1388** —
+  471 lines later.
+- **The fix is a pure move.** Gate **`e4967da9bdc4537802993523c7044a762a9a6366576df4e4234444789310107e`**
+  (134,427 B / 2,558 lines / **125** `check(` registrations — unchanged); the Q44 census machinery
+  was cut from its old site (dated note left) and re-inserted above the probe branch: before-read
+  at **:890**, branch **:893**, spawn **:948**, foot census **:2477** (asserted by the patch
+  script). `out/DIFF-vs-q50.txt` (76 lines / `c8b2ac1367fbe5f2…`) = **2 hunks + 33 added − 27
+  removed**, and 2,552 + 33 − 27 = 2,558 exactly. Disarmed twin (the spawn's `env=` removed, the
+  same one-line cut Q50's pair carried): **`b1d969767f347d179ce14df1803bef1fa409d880beeafc8b898e34cf57d63add`**
+  (134,378 B / 2,557 lines / 125).
+- **The item's two cells, verbatim.** Blank cell, shipped gate, `Q48_ROOT=/root/.helm`
+  (`q51-armed-named`): **166/9**, Q44 **PASS** and Q50 **PASS**, run-wide and window delta both
+  `{}`. Disarmed discriminator (`q51-dis-named`): **164/11**, Q50 window check **FAIL** (the
+  detector prints the moved object, restores byte-exact) and the **run-wide Q44 check also FAILS
+  and names the object** — `before={"/root/.helm/data/held/stackchain-home.html.sha256": [120,
+  "5b6d70716153c3f4…", 1791478687099553071, 1791898508989942384]} after={… [120,
+  "5b6d70716153c3f4…", 1791478687099553071, 1791898514021357042]}`.
+- **The finding beyond the item's criterion:** before and after are identical on size/sha256/mtime
+  — the window detector restored byte-exact — and the run-wide check fails on **ctime alone**. The
+  run-wide instrument cannot be fooled by a restore, because ctime is the stamp a restore cannot
+  undo (Q43's discriminator, now load-bearing in the run-wide instrument). Two caveats stated in
+  the record: the run-wide failure is attributable to the restore trace, not a persisted byte
+  change (the Q50 window check names the write itself), and the property is inherited from the
+  census's four-field shape, which the move did not alter.
+- **Green pair, five consecutive invocations** (`run_green_q51.py`, subject `/root/crucible/q48/
+  helm-collect.py` `4e45021d…`, `Q48_ROOT` unset): rc 0 each, **175 passed / 0 failed** — the Q50
+  count exactly, no check added — 13,929 B, 12.41–13.04 s, live delta `{}` each. **Regressions
+  11/11**: n1–n5, noparse, dep-unparseable, undecodable, broken_dep rc 2; latin1 and bom **green at
+  13,929 B**; live delta `{}` on all 11. `VERDICT: ALL REGRESSIONS HOLD`.
+- **Live state, delta 0 on bytes/sha256/mtime across all 32 invocations:** snapshot 14,039 B /
+  `aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d` / mtime_ns
+  `1791479579475780303`; held pin 120 B / `5b6d70716153c3f4…` / mtime_ns `1791478687099553071`.
+  **ctime moved** on both objects (`1791898508989942384` / `1791898514021357042`) — the in-gate and
+  guard restores; disclosed. Final tree **0 sandboxes**; disk 45 GiB free of 153.
+- **Four defects of mine, logged first in the deliverable:** the first regression run was void
+  (the q51 tree was built without `fixtures/`; 11 Q35 refusals, no gate body, live delta 0; re-run
+  after `cp -r`); the matrix JSON's Q44/Q50 cells are empty (extractors matched line *prefixes*,
+  the foot prints `  PASS  Q44 …` — the Q50 record's own defect class; §3 is re-derived from the
+  saved logs by `show_matrix.py`, no invocation re-run); `rm -rf` is blocked in this shell so the
+  copied fixtures carry `__pycache__` (harmless here; the adoption `cp` must not copy it in — C32);
+  the green runner's assertion covers bytes+sha256 but not the ctime trace, which §6 discloses.
+- **Still open and unclaimed:** Merlin's Q45 §9 follow-on (resolve paths at runtime, not only
+  static literals) — the hoist instruments the run, it does not relocate a runtime-composed root.
+  The §4 adoption `cp` (collector `4e45021d…` + gate **`e4967da9…`**, superseding `a951dbe8…`), the
+  `manifest_match` pin (stale since 2026-10-08) and the Q13 publication call stay Alexander's.
+- **Q7, measured:** the Helm lane's executable set is empty again — the adoption, Q9, Q13/Q19 and
+  Q42 are human- or counterparty-gated, and the Q45 §9 follow-on is the only named Helm unit left.
+  **No new item opened** — the next Helm unit after it is a decision, not a task.