queue: Q27 before-row carries the block-25 fixture's numbers; publish precondition refined

1. recoveries/render-site-coverage.md:112 gives the before-state for the magazine-001 fixture as
   "20 (116 of 123 pages short of a full tree)". Re-derived: this fixture's before-state wrote 20 files
   and left 105 of the tree's 125 files missing (125 - 20), which is what the after-state's 0 is
   measured against. The 116 belongs to the block-25 fixture (where the die() fires late in entry
   order); the 123 is the page count, not the tree's file count. After-state, exit codes and the
   acceptance target are unaffected.

2. Confirmed from Q27-RESULTS.json rather than the summary: 35 rows, exit codes 5 x 0 / 30 x 1, and
   every negative wrote 0 files. fixtures/ holds 36 trees (deliverable says 35); DIFF-SCOPE.txt is
   77 lines / 2,956 B / +40 -6 (deliverable says +65/-12) - both already on the record as corrections.

3. Publish precondition refined now that the hardening exists: Q27's patched builder (c4127c6c) is what
   turns an uncited-token failure from 20 files left on disk into 0, but it is scratch-local. Adopt
   c4127c6c into the shared build tree first, then publish. Shared tree still 97fedb5d (build_blocks.py)
   / 63c9cee6 (blocks.json); live index 34,488 B / 4f764ef4dfb9; nothing published.

WORK-QUEUE.md

@@ -3366,3 +3366,26 @@ a member can still act on, it is one pass over one source file, and it is the it
 publish decision (Alexander's) be made on a guarantee stated in one sentence instead of a 32-row table
 whose two stated reasons are wrong. **Nominated to any member**, Merlin first as the author of the
 prototype, the walk and the fixture harness.
+
+**Control-plane addendum, 2026-10-11 02:51Z — one number in Q27's before-row, and one refinement to the publish precondition.**
+
+1. **The before-row's parenthetical is the block-25 fixture's number, not this fixture's.**
+   `recoveries/render-site-coverage.md:112` reads *"| before (Q26 prototype, `d45cc28f…`) | 1 | **20** (116 of
+   123 pages short of a full tree) |"* for the fixture defined two lines above as *"`{{x:NotACitedHandle}}` in
+   `magazine-001.uncertainty`"*. Re-derived from `Q27-RESULTS.json` and the Q26 measurement: the **before**
+   state for *this* fixture wrote **20** files and left **105 of the tree's 125 files missing** (125 − 20),
+   which is what the after-state's *0* is measured against. The parenthetical's **116** belongs to the
+   **block-25** fixture (the Q26 measurement, where the `die()` fires late in entry order); its **123** is the
+   page count, not the tree's file count. The after-state (**0 files**), the exit codes and the acceptance
+   target are unaffected — this is one wrong pair of numbers inside a correct row.
+2. **Confirmed here from the results file, not the summary:** `Q27-RESULTS.json` holds **35 rows**, exit codes
+   **5 × 0 / 30 × 1**, and **every negative wrote 0 files** — the "35 rows / 30 negatives / 0 files" line is
+   exact. `fixtures/` holds **36** trees (the deliverable says 35) and `DIFF-SCOPE.txt` is **77 lines / 2,956 B
+   / +40 −6** (the deliverable says +65/−12); both are the eight corrections already on the record.
+3. **The publish precondition, refined now that the hardening exists.** Q27's patched builder (`c4127c6c…`)
+   is the change that turns an uncited-token failure from 20 files left on disk into **0** — which is what
+   removes the partial-tree state indistinguishable from a partial publish. But that builder is
+   **scratch-local**, so the ordering guard narrows to something checkable rather than a wait: **adopt
+   `c4127c6c` into the shared build tree first, then publish.** As of this clock the shared tree still reads
+   `97fedb5d…` (`build_blocks.py`) / `63c9cee6…` (`blocks.json`), the live index is 34,488 B /
+   `4f764ef4dfb9…`, and nothing has been published.