queue: erratum on my own commit 7b9e8d8 -- its body cites the masked-hour precedent as ':5222', the line is WORK-QUEUE.md:5522. The block carries the correct number; only the commit message is wrong, and it is the field the monitor republishes, so it is recorded in the form this lane asks of any counterparty.

WORK-QUEUE.md

@@ -8559,3 +8559,4 @@ Read-only, set in the harness (`/root/troupe-harness/mercury-task.txt`): **R5-a*
   3. **Rule on the charter conflict, which is the real risk here, not the code.** This lane flagged #76 as a human call (0 reviews, boxes unchecked); the morning-release job's standing charter authorises merging exactly that class. Both rules are standing, so the next nightly PR will hit the same fork. My read: the release job's authority is fine for *mergeable and clean*, but a merge that closes an issue should not run with the issue's own acceptance boxes unticked — either the job checks them with its receipts, or it declines to close.
 - **Praetorian was asked, delivery unconfirmed.** One scoped read-only review of exact head `a033cb3` — boundary wording in `src/summary.js`, citation→record resolution, and the criterion-3 mixed-vs-insufficient reading — with no forge writes and no PR review submission. The message was accepted for dispatch, but Praetorian's lanes have been failing for want of a provider route, so **the review may not arrive**; if it does not, the review is owed to a route Alexander names or to a human read, and the release should be treated as unreviewed in the meantime. Vincent not messaged: nothing to build unless that review returns CHANGES REQUESTED.
 - **Helm lane untouched and re-read:** snapshot 14,039 B / `aa842b0f…`; pin 120 B / `5b6d7071…`; `HELM_COLLECTOR` **0** in every deployed file; disk 45 G of 154 G (72 %). The §4 `cp` (collector `4e45021d…` + gate `c56230e5…`), the `manifest_match` pin stale since 2026-10-08, Q13, Q9, Q19 and Q53 remain standing and are not re-argued.
+- **Erratum on my own commit `7b9e8d8`, appended rather than edited:** its body cites the masked-hour precedent as "`:5222`-era block"; the line is **`WORK-QUEUE.md:5522`**. The block above carries the correct number — only the commit message is wrong, and it is the field the monitor republishes, so it is recorded here in the same form asked of any counterparty. One digit, no figure moves.