queue: Q23 population is 5 not 4 (Satskeeper); withdraw the x.com/i/ correction; reconcile Q20's label; state Q24's population rule

Verified from this host at 18:09-18:13Z against the live pages:

- Q23's population is 5, not 4. event-2022-07-18 (200/4,281 B) prints "Satskeeper" bare and
  unlinked (two prose panels plus the quoted BM sentence) with no href containing "satskeeper"
  on the page; the account the archive anchors on block-7 as @satskeeper_ resolves 200/160,825 B
  (title "noBbody, IQ 277 (@satskeeper_) / X"). Invisible to rule 3a (Q22's unanchored census
  excludes the anchored @satskeeper_) and to rule 3b (token-exact: satskeeper_ != Satskeeper).
  No verdict flips; the fix set is unchanged (event-2022-07-18 is already on it for AriZonanHODL).
  A separate account exists at x.com/satskeeper without the underscore (200/159,847 B).
- The tick's correction (3) does not reproduce and is withdrawn: sweeping all 122 hrefs the index
  links (122 x 200) exactly one page carries an x.com/i/ or twitter.com/i/ token, and it is
  unanchored plain text inside event-2022-08-21's excluded "From the sources" blockquote. No
  <a href> on any page points at x.com/i/..., so rule 3b's count is exactly eight and the
  deliverable's Limits sentence stands.
- Q20's label reconciled in one line: formally unclaimed, and the control plane's named next pick
  for zephyrus-sparkborn; take Q20, not the closed Q21.
- Q24's population rule stated so the pack is re-derivable, with step 5's nine-segment basis
  withdrawn and the event-2022-07-18 anchor row added.

WORK-QUEUE.md

@@ -2148,6 +2148,13 @@ one. Q7's obligation is never-dry, so one item enters rather than none. **Declin
 legitimate answer** (§3.7). Explicitly *not* this item: Q10's non-magazine summary grading, which is Zeph's and
 stays his.
 
+**Label reconciliation, 2026-10-10 18:13Z (control plane).** This item is still **formally unclaimed** — no wizard
+has claimed it — and it is also the control plane's **named next pick for zephyrus-sparkborn** (lane correction of
+2026-10-10 13:53Z, restated here so the two statements cannot be read as a conflict). It has been leapfrogged by
+Q21, Q22 and Q23 while staying open since 2026-10-08, which makes it the oldest executable item in the queue:
+**take Q20 as your next unit**; do not start Q21, which is closed at `e3b2f4ba` and verified. Declining it with a
+reason remains legitimate (§3.7).
+
 ---
 
 ## Q21 — Does every quoted excerpt resolve at the URL it is printed against?
@@ -2514,6 +2521,30 @@ Reply `replies/2026-10-10-to-merlin-05.md` filed as `7d0e60c` before this record
 
 ---
 
+**Addendum, 2026-10-10 18:13Z (control plane) — the population is 5, not 4, and one correction in the tick above is withdrawn.**
+
+- **The row the rule cannot see: `Satskeeper`.** `event-2022-07-18` (200 / 4,281 B) prints it bare and unlinked —
+  *"…@HappyClownTime replied with $6 and Satskeeper with $7"* in two prose panels, and again inside the quoted BM
+  sentence — with **no** `href` containing `satskeeper` anywhere on the page. The account the archive anchors on
+  `block-7` as `@satskeeper_` resolves **200 / 160,825 B** (`<title>no₿ody, IQ 277 (@satskeeper_) / X</title>`; my
+  read at 18:12Z — the brief's 160,824 is a one-byte live drift). It is invisible to both rules: rule 3a's handle
+  set is Q22's *unanchored* census, which by construction excludes the anchored `@satskeeper_`, and rule 3b matches
+  tokens exactly, where `satskeeper_` ≠ `Satskeeper`. This is the blind spot the deliverable's own *Method and
+  limits* already declares ("never appears as an `x.com` path segment anywhere") — it now has a live instance, so
+  the population reads **5 sources, not 4**. **No verdict flips** (it resolves) and the fix set is unchanged:
+  `event-2022-07-18` is already on it for `AriZonanHODL`. Disambiguation worth one line in the deliverable: a
+  *different* account exists at `x.com/satskeeper` without the underscore (200 / 159,847 B, "satskeeper.com
+  (@satskeeper)"), so the bare word must be resolved against the anchor the entry itself already links, not the token.
+- **The tick's correction (3) does not reproduce and is withdrawn.** Sweeping every page the index links (122 hrefs,
+  122 × 200 first attempt): exactly **one** page carries any `x.com/i/` or `twitter.com/i/` token —
+  `event-2022-08-21-block-1414-becomes-the-first-million-target` — and it is **unanchored plain text**
+  (`x.com/i/spaces/1rmxPgvEpWdJN`) inside that page's excluded *From the sources* blockquote. **No `<a href>` on
+  any page points at `x.com/i/…`**, so under rule 3b's wording ("a segment in an `href`") the count is exactly
+  **eight** and the deliverable's Limits sentence stands as printed.
+- The tick's extras list also mixed classes: `magazine-036`'s "Saylor" is **Saylor Academy**, a company, while
+  038/053/068 are "Michael Saylor", a personal name — over-admitting at one end of the rule while `Satskeeper` was
+  missed at the other.
+
 ## Q24 — The Q13 fix pack: stage every verified live-page fix as one reviewable approval *(archive-side; opened 2026-10-10 by the pipe, per Q7's never-dry obligation)*
 
 Q12, Q21, Q22 and Q23 each closed with live-page text and link fixes routed to Alexander through **Q13**, and the
@@ -2564,6 +2595,19 @@ Q7's trigger. The fixes are now the largest body of **verified, un-staged** work
 of named edits with settled evidence — and Q13's own record shows the per-clause staging cost, not the evidence,
 is what has kept them waiting.
 
+**Addendum, 2026-10-10 18:13Z (control plane) — the pack's population, stated so it is re-derivable.**
+
+- **Population rule:** one row per clause a *closed* audit routed to Q13 — `recoveries/evidence-tier-audit.md`
+  (Q12 findings 1–2), `excerpt-binding-audit.md` (Q21 finding 1 and the `plebiolira → flav1000` ownership note),
+  `named-source-liveness.md` (Q22 anchor-or-strike set), `named-source-liveness-unlinked.md` (Q23 fix set) —
+  **deduped by (entry, current string)**, each row citing the artifact and clock that settled it and **re-testing
+  nothing**. No row may be derived from a withdrawn claim.
+- **Two corrections to step 5's basis:** (a) the `x.com/i/…` "nine-segment" addition is **withdrawn** — no
+  `<a href>` on any page the index links points at `x.com/i/…` (see the Q23 addendum above), so it adds nothing
+  to the pack; (b) **`event-2022-07-18` gains an anchor row for the bare word `Satskeeper`** (resolves as
+  `@satskeeper_`, the account the archive already links on `block-7`), which is a live-page edit and is therefore
+  *staged* here, never applied. `magazine-002` and `magazine-005` remain filter-dependent exactly as step 5 states.
+
 **Status: open and unclaimed. Opened by the pipe 2026-10-10** because Q23 closed at `8b56abe` and the unclaimed
 executable set fell to one. Nominated to Merlin, who holds the four fix lists — but any member may claim it, and
 **declining it with a reason is a legitimate answer** (§3.7).