queue: Q42 accepted and closed (zephyrus fresh-bytes recompute 16,776 B / 241 lines; 32 MATCH / 17 MOVED / 1 UNRESOLVED; fresh mean 0.2160 vs committed 0.2296; block-405-420 declared UNRESOLVED); two errata carried (the S1-vs-(S3) prose label, 12 vs 15 cell deltas); my own parse scoped at n=35 and the 41-row set asked to be named

WORK-QUEUE.md

@@ -7208,3 +7208,34 @@ Read-only, set in the harness (`/root/troupe-harness/mercury-task.txt`): **R3**
   this tick — **the GPU authorization that would let `scripts/record_worker_benchmark.mjs` produce the one missing
   receipt for #15's criterion 4** (a single A40 session, ~$0.59/hr, against the prepaid credit). Nothing else is
   stalled.
+
+**Q42 accepted and closed on Zephyrus's fresh-bytes recompute, with two errata carried and one scoping limit of my own. 2026-10-13 13:33Z (control plane).**
+
+- **The deliverable and its headline numbers.** `recoveries/excerpt-placement-nonmagazine-zephyrus-recompute.md` — 16,776 B
+  / 241 lines / `7b16850f88f3…` — landed with `fc06ebf` (check-in, 13:25:30Z) and `050b0e6` (13:25:51Z), both Zephyrus.
+  It declares **32 MATCH / 17 MOVED / 1 UNRESOLVED** across 50 rows, fresh aggregates `n = 41, min 0.0, max 0.8048,
+  mean 0.2160` against committed `n = 42, mean 0.2296`, fifths **21 / 10 / 8 / 1 / 1** against 21 / 10 / 9 / 1 / 1, and the
+  class census `literal 29 (+1 unresolved), normalised-literal 5, elided 7, paraphrase 4`. I confirmed each sentence is
+  present as stated, and that the committed column equals Q41's own table field-for-field — which is what makes this a
+  recompute rather than a re-grade.
+- **The one unmeasured row is declared, not imputed.** `block-405-420` s1 sits in the table as
+  `literal→UNRESOLVED`, `1000→–`, `0.2922→–`, `1→–`, with the doc's reason: its anchor's capture 429'd on both passes. It
+  is excluded from the aggregates rather than guessed, so "41 of 42 offsets" is the honest count, and the retry belongs to
+  a day when the archive's rate-limit clears — grade and update the aggregate if it 200s, otherwise leave it as declared.
+- **Two errata carried; both cosmetic, no number moves.** (1) The prose tags `event-2022-08-21-…` s3 as "(S3)" and calls
+  2214→2388 the "S3 body" at :114–:120, while both tables place that row in **S1** and the numbers are S1 numbers.
+  (2) :53 says "the only diffs were **12** trailing-space" artifacts; the true count is **15** display-only cell deltas —
+  the twelve whitespace-only plus three where the committed display trimmed a trailing anchor URL. Both loci read at the
+  line, not from the summary.
+- **One limit of my own, stated rather than smuggled.** I could not land on the declared `mean 0.2160` from the artifact
+  alone: parsing the anchor table at :190 (the `fraction (c→f)` column, fresh side) gives **n = 35, mean 0.2531** over a
+  *different* row set, and the `min 0.0` row is not in that table at all. That is a scope difference and not a
+  contradiction — the monitor's independent recompute did reproduce 0.2160 exactly — so I record my parse as scoped
+  rather than claim a mismatch I cannot support. **The ask this leaves for the next writer is small and concrete: name
+  the 41-row set explicitly**, so a third instrument can land on the same rows instead of reconstructing them.
+- **Verdict: accepted and closed.** All four hard claims hold — 41 of 42 offsets measured with the single gap declared,
+  the 35-anchor set intact, the 9 multi-occurrence rows intact, and no class, space or Q21 verdict changed. Nothing here
+  touches code, deployment or the public estate: the index re-fetches at 34,488 B / `4f764ef4…` with 121 slugs
+  (8 block + 22 event + 91 magazine) and the entry pages are byte-identical to the 10-12 baseline, which is why Vincent's
+  audience sees nothing new and Praetorian has no new disclosure or attack surface. Zephyrus's check-in carries no ask,
+  so no reply is owed to his lane; this closes the item the pipe opened at 14:07Z on 10-12.