queue: both owed one-liners landed at 8950228 (Q10 pilot census 21->22 / 29->30, clause 5 -> holds) and 4fbc491 (the three item-28 relay strikes), each verified from this host; the defect record is closed and the record's two relocated citations noted; one precision is ours - fb9fff0 entered the repo 2026-10-07T14:03:22Z by committer date, so the struck sentence's window closed 8h38m06s before created_at, not at 20:47Z; nothing executed, no another-party file touched, Q10 stays active, three executable unclaimed so no item opened

WORK-QUEUE.md

@@ -1704,3 +1704,16 @@ Nothing new is publishable. Standing public status unchanged: **15 live / 2 clos
 **Correction, 2026-10-08 — the blob cited for `decisions/2026-10-07.md` in the `9da1b71` addendum is wrong; no text above is altered.**
 
 - The `9da1b71` addendum reads *"`decisions/2026-10-07.md`, blob `b0…` 20 lines"*. The file's blob is **`51142d701b18448e5bcf71927615cf51bad4d39c`** — `git rev-parse 22d353d:decisions/2026-10-07.md`, **20 lines**, **`+20/−0`** — which is the value the monitor listing carries (`decisions/2026-10-07.md 51142d701b18`). `b0d73540756b` is **`checkins/2026-10-07-zephyrus-02.md`**'s blob. The relay file itself is unchanged; only the citation is corrected.
+- **Blob note (2026-10-08, later the same day):** that citation was correct when written; `decisions/2026-10-07.md` has since moved to **`f126eba75613`** at `4fbc491` (see the addendum below).
+
+
+**Addendum, 2026-10-08 (monitor run, second tick) — both owed one-liners landed and are verified: `8950228` (Q10 pilot: census `21→22` / `29→30`, clause 5 `unsupported → holds`) and `4fbc491` (the item-28 relay strikes). Nothing executed; Q10 stays active.**
+
+- **Two counterparty commits this tick**, both zephyrus-sparkborn, both subject *"corrections per reply 45/46"*: **`8950228`** (13:09:28Z, `recoveries/summary-fidelity-nonmagazine-pilot.md`, **+28/−13**, blob `af0871b8769e` → **`5cc9ea97ed79`**); **`4fbc491`** (13:09:29Z, `decisions/2026-10-07.md`, **+33/−2**, blob `51142d701b18` → **`f126eba75613`**) — the monitor's `head`. Reply 47 filed at `2bad1ac`.
+- **Reply 45's two pilot appends landed and are verified from this host, not from the label.** Census `21 → 22` events / `29 → 30` pages: the file's 22 `event-*` slugs are **set-identical** to the live index's 22 (matcher `event-[0-9]{4}-[0-9]{2}-[0-9]{2}-[a-z0-9-]+`, index `200 / 34,488 B`, 13:12Z), and the block-page list is the same **8**. Clause 5 re-graded to **`holds`** against the entry's own sources: `sip-0001.txt` `200 / 1,610 B` names the genesis URL verbatim in **PROCESS step 1** (quote matches byte-for-byte; its only other `twitter.com` string is the header handle); raw `README.md` `200 / **9,663 B**` carries the URL as the *"decided to buy"* link; the live URL resolves `twitter.com → 301 → x.com → 404`. **Pilot totals `5 / 0 / 0 / 0`.** The wording-flag candidate is withdrawn on its stated ground and kept only as a readability note, correctly **not** on Q13. **Documented.**
+- **The three item-28 relay strikes landed** (`4fbc491`): the §2a stale *"no check-ins or commits from him … as of 2026-10-07"* sentence, the §2b *"could not be made on his behalf"* premise, and the §2c restored *"applied by Timmy … `3ef32bb`"* clause are each struck inline and restated in an appended block. Verified here: `cassian`'s three commits predate `created_at` (earliest `fb9fff0` entering the repo **2026-10-07T14:03:22Z**); the only collaborator mutation in any retained log is the `127.0.0.1` `PUT …/collaborators/cassian` → **204** at **2026-10-06T23:49:28Z**, and no `settings/collaboration` POST exists (grep over the 10-01…10-08 rotated logs **and** the live `gitea.log`); `14e69c6` retracts the attribution and `3ef32bb` is the pre-correction file. The defect record directly above is **closed**, and the file no longer disagrees with itself. **Documented.**
+- **One precision is ours, logged not struck.** `fb9fff0`'s *author* date is 2026-10-06 but its *committer* date — when it entered this repo — is **2026-10-07T14:03:22Z** (parent `0fb98f9`, 13:20:17Z). So the struck sentence's true window closed **8h38m06s** before `created_at`, not at the 10-06 `20:47Z` pre-grant moment the append names; the strike is unaffected either way. The author-date/committer-date split is named so the record carries it once.
+- **Executed this tick: nothing.** No permission change, no revert, no edit to another party's file; the relay append was his and it is received. The two relocated citations (`decisions/` blob, now `f126eba75613`) are noted above, not renumbered.
+- **Privacy, unchanged and now ruled rather than a blocker:** the Telegram chat identifier still stands in the **three** public files (`14e69c6` ours, `22d353d` the relay, `9da1b71` the concurrent run); neither of this tick's counterparty files reprints it and none of ours does. Redaction in `decisions/` versus a visibility change remains **Alexander's**; the repository is public under his 2026-10-06 *keep public* ruling (`ef7593c`), so this is exposure by decision, not a misconfiguration.
+- **Queue state, measured — nothing opened, nothing closed as an item.** `Q10` **active** (zephyrus; pilot = 1 of 30; next batch **A `ev-001…ev-011`**, minus the pilot = **10**); open and unclaimed **Q6, Q11, Q12** (three); `Q9` blocked (audio handover); `Q13` (18 flags) and `Q19` gated on Alexander. Three executable unclaimed is not thin — **no item opened, none invented.**
+- **Nothing new is publishable.** Standing public status unchanged: **15 live / 2 closed / 0 re-posted**.