queue: Q22 verification tick (control plane) - Q22 DONE at 5c7a75f (Merlin) verified from this host 15:57-16:02Z, landing f0d684e; index 200/34,488 B/sha 4f764ef4dfb9, 121/121 entry pages 200 first attempt, deliverable 16,731 B/sha f12b8a42 and queue byte-identical over the anonymous raw path; four corrections appended rather than edited into Merlin's text - the distinct-source split is 21/1/2/3 = 27 not 20/1/2/3 = 26, StackchainQuant is named unanchored on three event entries (08-18 x2, 08-28, 10-05 x2) so the fix set is eight not six, the @handle subtotal is 38 not 37, and the depth line cites Q8 which closed at 1cb13e7 on 2026-10-07; drift recorded for 40,838/40,839, 159,958/159,957, 64,516/64,518 and the check-in's pre-append self-hash; one unclaimed executable item left (Q20) so Q23 opens in the next commit; decisions/2026-09-26.md still eb34b4b4d7, nothing executed

WORK-QUEUE.md

@@ -2349,3 +2349,45 @@ Six entries named whose source does not resolve: `magazine-020`, `magazine-051`,
   deletion are indistinguishable from here. This tests liveness only, not whether the named source
   supports the claim beside it (Q8/Q10/Q20) or whether the *anchored* sources resolve (Q3/Q21).
 - **Q22 closes owing nothing from Merlin. Q20 remains the top unclaimed item.**
+
+**Addendum, 2026-10-10 (control plane) — Q22 verified from this host, four corrections appended, Q23 opened.
+Reply `replies/2026-10-10-to-merlin-04.md` filed as `9875529` before this record, so the ordering rule holds.**
+
+- **`5c7a75f` (Merlin, 2026-10-10T15:46:04Z, +373/−20, three files) — Q22, named-source liveness.** Verified from
+  this host, 2026-10-10 15:57–16:02Z: index `https://alexanderwhitestone.com/stackchain/blocks/`
+  **200 / 34,488 B / sha256 `4f764ef4dfb9…`** to the nibble; **121/121 entry pages 200** on the first attempt
+  (**91 `magazine-*` + 22 `event-*` + 8 `block-*`**); deliverable `recoveries/named-source-liveness.md`
+  **16,731 B / sha256 `f12b8a42…`** and `WORK-QUEUE.md` **313,733 B / `652de13b…`**, both **byte-identical** over
+  the anonymous `forge…/raw/branch/main/` path; landing note `f0d684e` (check-in raw 200 / 34,108 B
+  byte-identical). **All six non-resolving rows reproduce to the status, title and body** — `@_overflow__`
+  404/37,678, `@humblebitcoiner` 404/37,702 and `StackchainQuant` 404/37,702 (`User Profile Not Found - X | 404
+  Error`), `@BTC_Freeborn` 200/40,800 and `@RedTailHawk1923` 200/40,838 (`Profile / X` + `Account suspended`),
+  `@captainsiddh` 200/68,579 with *"Now at @captainsidd"* and `x.com/captainsidd` resolving *Evan (Captain Sidd)
+  (@CaptainSidd)*. All **20 resolving `@handle`s** re-fetched 200; the **25 unanchored distinct handles** and every
+  census entry-association reproduce row for row; the **`@staceski` suffix-match defect is confirmed** (no
+  `x.com/staceski` anchor, only the `stackchainmagazine.net/…staceski/` permalink). **Grade: Documented** for
+  every figure; his process claims stay **Testimony only**. No another-party file edited; nothing executed.
+- **Four corrections returned, none of them touching his text.** (1) **The verdict split does not sum:** his
+  *"27 distinct sources: 20 `resolve` (19 X accounts + the 1 archive URL), 1 `resolve-moved`, 2 `suspended`,
+  3 `404`"* is **26**; the correct split is **21 `resolve` (20 X accounts + the 1 archive URL)** / 1 / 2 / 3 =
+  **27** — 22 fetch-rows − 1 (`@happyclowntime` duplicate fetch) = 21 resolving sources. (2) **`StackchainQuant`
+  is named unanchored on three entries, not one:** `event-2022-08-18` (`What happened` ×2) **plus
+  `event-2022-08-28`** (*"The October 2022 StackchainQuant article independently confirms 1492…"*) **and
+  `event-2022-10-05`** (*"StackchainQuant's Bitcoin Magazine guest post reports…"*), neither page carrying any
+  `x.com` anchor — so the fix set is **eight entries**, not six, and the worst-case 404 carries claims on three
+  pages. (3) **The `@handle` subtotal is 38, not 37** — by my independent `(entry, section, handle)` count and by
+  summing his own census column (single-counting the one account printed under two spellings). (4) **The depth
+  line leans on a closed item:** his *Next* cites *"Q8's sweep stands at 73/91 with batch `072–080` next"*, but Q8
+  closed at `1cb13e7` on 2026-10-07 at 91/91.
+- **Drift, not error, recorded so the figures are not read as disagreement:** `@RedTailHawk1923` **40,838** vs his
+  40,839; `x.com/captainsidd` **159,958** vs 159,957; `block-5`'s bare Wayback capture (`-L`, 0 redirects)
+  **64,516** vs 64,518 — the csp-nonce/dynamic-page class he already names. The check-in's landing block reports
+  its own pre-append size **32,647 B / `27537f59`** (`5c7a75f`); after `f0d684e` the file is **34,108 B /
+  `90f02058`**. Both asks — the eight-entry anchor-or-strike set and the `@captainsiddh` → `@captainsidd` wording
+  — are live-page edits and remain **Alexander's through Q13**; `decisions/2026-09-26.md` is still `eb34b4b4d781`
+  and `inbox/seed-2026-09-26.json` still `c05e6a0666d8`.
+- **Queue state, measured:** `Q22` **DONE** this tick; `Q20` open and unclaimed (the single unclaimed executable
+  item); `Q9` blocked on the audio handover; `Q13` and `Q19` gated on Alexander. One unclaimed executable item is
+  thin by the pipe's own precedent (the set falling to one is what opened Q21 and then Q22), and §2.4 removes the
+  closed item that was padding the count — so **Q23 is opened** in the next commit. **Q20 remains the top
+  unclaimed item.**