queue+table: Zephyrus was egress-blocked, not silent -- my own roster corrected (append-only)

The lane pushed three commits today (9dd6ae1 audit, 1f96c8a/23837a4 check-ins), local-only since
2026-10-11T13:09Z because it was egress-blocked; his own 10-12 note records the rebase onto eec89dc.
My record was false as written: WIZARDS-TABLE.md:15 ("Q20 -- taken, not worked ... no check-in since
2026-10-10") and 6796e31 12:18:35Z ("no check-in for 10-11 or 10-12"). The escalation resting on them
is withdrawn; corrections appended, nothing deleted.

New general limit, distinct from Q36 and Q37: the monitor reads origin only, so unpushed counterparty
work is indistinguishable from silence. No script fixes it; a per-wizard push path is an access
decision.

The audit is real: sample file 13,368 B, 26 excerpts (3+3+3+3+3+3+3+3+2), 26 literal / 0 others; the
rows file (74,561 B, 323 lines) reports 269 rows / 91 entries (87x3+4x2) / offsets 0-20,641 /
fractions 0.0000-0.9472 / mean 0.4735 / fifths 53-65-51-61-39. Q20's population verdict stays
Corroborated; the audit is a third independent pass (Documented).

Defects, with one loose statement in the monitor's own list:
(1) the 10-11 check-in attributes Q21 three times to Cassian while e3b2f4b carries Merlin's own
message text and the queue's 13:53Z correction names Merlin -- figures stand, the name does not;
(2) recoveries/excerpt-placement-audit.md DOES resolve on main (blob 2562ffe608798684..., 14,045 B),
so "resolves to nothing" is loose -- but it is Merlin's deliverable and the 13,368 B attached to that
path is the sample file's size, while its ccc6eb7 does not resolve at all;
(3) the "amended/supersession" claim is not present in the pushed 10-12 file, measured raw;
(4) sample and population numbers live in different detag spaces and are not comparable.

Disk 958 MB free, falling faster than syslog alone explains.

WIZARDS-TABLE.md

@@ -47,3 +47,16 @@ Every wizard owes, daily, under `STANDING-AGREEMENT.md`:
 A lane that stops churning is a lane that needs a decision, not silence. If a wizard
 is blocked, its `Blocked:` line names the exact thing holding it, and Timmy escalates
 only what needs a human.
+
+---
+
+**Correction, appended 2026-10-12 13:24Z (control plane) — the Zephyrus row above is false as written.**
+His lane was **not** silent and Q20 was **not** "taken, not worked". He pushed three commits today — `9dd6ae1` (the
+Q20 sample audit), `1f96c8a` and `23837a4` (his 10-11 and 10-12 check-ins) — which had sat **local-only since
+2026-10-11T13:09Z** because the lane was **egress-blocked**; his own 10-12 note records the rebase onto `eec89dc`
+and the push. The escalate-line in that row ("needs Alexander's one line — re-task the lane or let it lapse") is
+**withdrawn**, as is the queue's `6796e31` reading ("no check-in for 10-11 or 10-12"). What survives, and is new, is
+the general limit: **the monitor reads origin only, so unpushed counterparty work is indistinguishable from
+silence** — distinct from Q36's identity hole and Q37's branch-head line, and not fixable by a script; a per-wizard
+push path is an access decision. Q20's population verdict still stands as Corroborated, with his sample audit as a
+third independent pass.

WORK-QUEUE.md

@@ -5618,3 +5618,37 @@ two corrections logged, one subject-import hazard measured. 2026-10-12 11:5xZ (t
   reconciling against its `proposed_action`; item 13's decided note still controls over its proposed action
   (escalate to author and publisher, do not edit the live page). The public-with-pending-material mismatch stays a
   §4 gate for Alexander. Nothing from `inbox/` is quoted here or in reply 55.
+
+**Q20/Zephyrus: the lane was egress-blocked, not silent — and my own roster was false. 2026-10-12 13:24Z (control plane).**
+
+- **The lane was never silent.** Zephyrus pushed three commits by `zephyrus-sparkborn@noreply.127.0.0.1` — `9dd6ae1`
+  (the Q20 sample audit), `1f96c8a` (10-11 check-in), `23837a4` (10-12 check-in) — rebased onto `eec89dc`. His own
+  10-12 note says it verbatim: *"Yesterday's two commits sat local-only (egress-blocked on the 10-11 tick); today I
+  rebased them onto `eec89dc` and pushed."* **My own record is therefore false as written:** `WIZARDS-TABLE.md:15`
+  reads "**Q20 — taken, not worked** … no check-in since 2026-10-10", and `6796e31` (12:18:35Z, mine) reads "no
+  check-in for 10-11 or 10-12". The escalation built on them — re-task the lane or let it lapse — rested on a false
+  premise and is **withdrawn**. Both are corrected by appended notes; nothing is deleted.
+- **New general limit, distinct from Q36's identity hole and Q37's branch-head line: the monitor reads origin only,
+  so unpushed counterparty work is indistinguishable from silence.** No script fixes it. A per-wizard push path is
+  an access decision, not a tooling change.
+- **The audit is real and the population file's internal consistency holds.** Sample file
+  `recoveries/excerpt-placement-audit-zephyrus-sample.md` = 13,368 B (sha256 of the fetched text `f8cda6cd2c70…`;
+  my slice is the raw fetch, not the blob id), 26 excerpts (3+3+3+3+3+3+3+3+2), **26 literal / 0 others**; his
+  aggregate recompute of `recoveries/excerpt-placement-rows.md` (74,561 B, sha256 `880223f35f9b…`, 323 lines)
+  reports 269 rows, 91 entries (87×3 + 4×2), offsets 0–20,641, fractions 0.0000–0.9472, mean 0.4735, fifths
+  53/65/51/61/39. **Q20's population verdict stays Corroborated**; this audit is a third independent pass
+  (**Documented** — the monitor's 18-page re-fetch, clocked, plus his parser and the monitor's).
+- **Record defects, including one loose statement in the monitor's own list.** (1) The 10-11 check-in attributes Q21
+  three times to **Cassian** (`:4`, `:20` "Cassian executed Q21 overnight", `:29` "Cassian took Q21"), while the
+  commit it cites — `e3b2f4b` — carries Merlin's own message text ("queue: Q21 excerpt-binding census DONE (Merlin)"),
+  and the queue's 13:53Z correction names Merlin. His figures stand; the executor's name does not — returned for an
+  inline supersession note. (2) `recoveries/excerpt-placement-audit.md` **does** resolve on main (blob
+  `2562ffe608798684…`, **14,045 B**), so "resolves to nothing" is loose — but that file is **Merlin's** Q20
+  deliverable, and the 13,368 B the 10-11 check-in attaches to that path is his **sample** file's size: the citation
+  pairs one file's path with another file's size, and its `ccc6eb7` does not resolve at all. (3) The 10-12 claim
+  about an "amended/supersession" note is **not present in the pushed 10-12 file**, measured against the raw text at
+  this tick; as pushed it says only that the lane was restored, replies 52–54 read, the rows recomputed and Q40
+  corroborated. (4) His sample numbers live in a different detag space than the population's, so 0.9381 and 0.9472
+  are not comparable across the two files.
+- **Disk (standing, non-forge): 958 MB free**, down from 1.4 GB earlier in the hour — falling faster than syslog
+  alone explains. The dashboard restart loop and the dead watchdog token remain Alexander's calls.