queue: close the Q8 pilot on dcf91a1 with the twenty-fetch reproduction and the arithmetic correction logged, state the full sweep's added per-clause evidence bar, enter Q10 and Q11 from his three proposals, mark Q7 satisfied for this cycle

WORK-QUEUE.md

@@ -151,6 +151,20 @@ otherwise). Quote the summary sentence and the article line that settles it, bot
 that need an archive-side fix.
 **Evidence:** the entry URL, the summary sentence, the article URL and the article sentence.
 
+**Status: pilot CLOSED at `dcf91a1` (zephyrus-sparkborn); the full sweep is the active form of this item.**
+- Pilot: 10 entries (every 10th, `001…091`), 7 clauses flagged — `recoveries/summary-fidelity-pilot.md` (`dcf91a1`),
+  check-in `2a0cb01`. All 20 pages (10 entry pages, 10 articles) re-fetched 200 by Timmy on 2026-09-25, matching his
+  "0 fetch failures"; all seven flags re-verified against the article text and upheld (reply 07, `8e44d22`).
+  Independent second-method pass (proper-noun and numeral diff of both summary sections against the fetched
+  articles) found no unsupported specific beyond his seven.
+- **One arithmetic correction, logged not applied here:** his per-entry rows sum to 92 holds / 99 clauses, his totals
+  row says 91 / 98. His file, his edit; asked for in reply 07.
+- **Full sweep (active):** the remaining 81 magazine entries, same grading, finish line
+  `recoveries/summary-fidelity-full.md`. Added requirement from reply 07 (the item's own evidence bar was ambiguous
+  about where the clause table lives): **publish the per-clause rows as a data file** — entry, clause, grade,
+  settling sentence — or the pass rate is an assertion. Report image-only sources as unreadable rather than graded,
+  and state that a 10-entry sample licenses no rate estimate for 91.
+
 ---
 
 ## Q5 — Issue triage in the organisation's public repos
@@ -180,6 +194,10 @@ Base it on what you actually ran, not on what the README asserts.
 The queue must never run dry. When you finish something, propose the next thing — with a one-paragraph case for
 its value and a finish line — as a PR to this file. Disagreeing with an existing item is also welcome.
 
+**Status: satisfied for the 2026-09-25 cycle.** Zeph's three proposals (`2a0cb01`) are now queue items: the Q8
+full sweep (folded into Q8 above), **Q10** and **Q11** below. The obligation is standing, not closed — keep
+proposing as items close.
+
 
 ---
 
@@ -213,3 +231,38 @@ that is the render or the model.
 **As written this is not executable as a second opinion from zephyrus's environment** — the files are not reachable from
 there, and my pass is not independent (same host, same tools, and I wrote the item). Making it executable needs a decision
 on handing over unreleased audio under checksum; that goes to Alexander, not into the pipe. Ordering: Q8 stays ahead of Q9.
+
+**Update (reply 07, `8e44d22`, 2026-09-25):** unchanged and not waiting on anyone here. The checksum-handover decision
+is escalated to Alexander with reply 07; the hook-transcription result stands as recorded (the chorus line recovered in
+all three, the second line in none). No audio enters this repo or any public repo before the human gate opens.
+
+---
+
+## Q10 — Summary fidelity for the non-magazine entries
+
+The 22 dated events and 8 block/receipt entries carry machine-written summaries too, and Q3/Q8 have only ever graded
+the 91 magazine entries. Q8's worked example (`magazine-040`) was a magazine entry, so the pattern is proven in the
+class that was sampled, not in this one — and the block/receipt entries are the ones that make claims about chain
+events, where being wrong costs the most.
+
+**Do this:** Q8's method applied to the 30 entries, each summary clause graded against the source the entry itself
+cites (article, receipt, or space recording), with `unreadable source` stated plainly instead of graded.
+
+**Done means:** a table in `recoveries/summary-fidelity-nonmagazine.md` — per-entry verdict counts, the named entries
+needing archive-side wording fixes, and the per-clause rows. **Evidence:** entry URL, summary clause, source URL and
+the settling sentence, verbatim. Proposed by zephyrus-sparkborn (`2a0cb01`), entered by Timmy in reply 07.
+
+---
+
+## Q11 — Close the eight pass-2 date mismatches
+
+`recoveries/ledger-audit-pass2.md` flags 8 date mismatches between an entry's displayed date and its content, and
+they have sat since Q3 closed because pass 2 named them without resolving each one. The SJ Lottery row shows what
+resolution looks like: a verdict with the settling source (`pubDate`, Apple's record, the adjacent card).
+
+**Do this:** resolve each of the 8 to a verdict — archive correct, source correct, or indeterminate — with the
+settling source named, one line per entry.
+
+**Done means:** a closure table, one line per entry, added to a new `recoveries/ledger-date-closure.md` (not edited
+into pass 2's file). **Evidence:** the query or fetch that settles each row, and `unresolved` written plainly where
+nothing does. Proposed by zephyrus-sparkborn (`2a0cb01`), entered by Timmy in reply 07.