queue: open Q24 (the Q13 fix pack) - Q23 closed at 8b56abe and the unclaimed executable set fell to one (Q20), Q7's never-dry trigger; the finding half of Q12/Q21/Q22/Q23 is verified and closed and only the staging half is left, which is where Q13's record shows it stops (1 of 8 staged since 2026-09-26); scope: reduce every verified live-page clause to an exact old->new delta against /root/stackchain-legends-build/blocks.json with the settling artifact and clock, stage it the 091 way (EDITS/ record + unrun apply script + revert command + emitted-file blast radius), reconcile each against decisions/ so a decided note controls over proposed_action and any conflict is surfaced rather than executed, and mark each decided or undecided; finish line docs/q13-fix-pack.md in the fixed column order; scope boundary stated so it cannot drift into applying, rebuilding, publishing or contacting a third party, or into re-auditing what Q12/Q21/Q22/Q23 already settled; nominated to Merlin but open to any member, and declining with a reason remains legitimate

WORK-QUEUE.md

@@ -2511,3 +2511,59 @@ Reply `replies/2026-10-10-to-merlin-05.md` filed as `7d0e60c` before this record
   successor here is **not** a re-run — Q22+Q23 together close the named-source liveness question for both the
   unlinked and the anchored classes, so the accumulating backlog is the fix set itself: **Q24 is opened** in the
   next commit as the **Q13 fix pack**. **Q20 remains the top unclaimed item.**
+
+---
+
+## 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
+finding half of every one of them is now verified and closed. What is left is the **staging** half, and Q13's own
+record shows that half is where it stops: *"1 of 8 has a decision and staged correction (`magazine-091`) … The other
+7 are undecided."* The worked example is cheap and mechanical — `EDITS/2026-09-26-magazine-091-correction.md` plus
+`EDITS/apply_editorial_fix_091.py`, a `blocks.json` delta, an appended `uncertainty` note, a rebuild with
+`build_blocks.py`, and a blast radius of exactly one emitted file. Nothing has been staged since.
+
+The archive's build source is on this host at `/root/stackchain-legends-build/`
+(`blocks.json` **278,459 B**, `build_blocks.py`, `EDITS/`), so every clause can be reduced to an exact delta
+*without touching a live page* — which is the whole point: Alexander's decision should be one pack, not four
+audits' worth of prose.
+
+**Do this, per clause** (Q12 findings 1–2; Q21 finding 1 and the `github.com/plebiolira/…` → `github.com/flav1000/…`
+ownership note; Q22's anchor-or-strike set; Q23's fix set):
+
+1. **Locate the string** in `blocks.json` — entry id and field — and quote the **current** value exactly, plus the
+   live page and panel where it is emitted today.
+2. **Write the proposed value as an explicit `old → new` delta**, one clause per row, with the artifact that
+   verified the finding and its clock (`recoveries/evidence-tier-audit.md`, `excerpt-binding-audit.md`,
+   `named-source-liveness.md`, `named-source-liveness-unlinked.md`) — the finding is not re-tested here; the row
+   cites what settled it.
+3. **Stage it the Q13 way:** an `EDITS/` record naming the files, the before hash and the revert command, plus an
+   apply script **committed unrun**. Nothing in this item writes to the live tree, rebuilds, publishes, or contacts
+   a third party.
+4. **Reconcile against `decisions/`:** where a decided note conflicts with a `proposed_action`, the **decided note
+   controls** and the conflict is surfaced as a blocker rather than executed — Q13's `magazine-091` note already
+   carries one authority/escalation caveat, and this is the item where any others become visible.
+5. **Mark each clause `decided` or `undecided-for-Alexander`**, and name the clauses that Q23's §2.1 correction
+   would add if the *"named as a source of record"* filter is **not** written into that header (`magazine-002`,
+   `magazine-005` join the anchor set; `magazine-036/038/053/068` only on the loose reading).
+6. **Measure the blast radius in emitted files before staging**, as Q13 did for `091`, and record it per row.
+
+**Done means:** `docs/q13-fix-pack.md` — one row per clause in the fixed column order `entry | live page | panel |
+current string | proposed string | authority (artifact + clock) | decided / undecided | staged file`, with the count
+of decided and undecided clauses and every conflict with a decided note named. **Evidence:** the `blocks.json`
+field path and exact current string read from the file with its clock; the emitted live page and its sha256; the
+verifying artifact per row; the revert command per staged clause.
+
+**Scope boundary, stated so it cannot drift:** this is the staging half of Q13 — **not** applying a fix, **not** a
+rebuild or publish, **not** a third-party contact, all of which stay gated on Alexander exactly as Q13 states. It is
+also not a re-audit: no row re-tests a claim already settled by Q12/Q21/Q22/Q23, and no clause may be staged in a
+form that could be applied without his approval.
+
+**Why it earns a slot:** Q23 closed at `8b56abe` and the unclaimed executable set fell to **one** (`Q20`), which is
+Q7's trigger. The fixes are now the largest body of **verified, un-staged** work in this repo — four audits' worth
+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.
+
+**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).