queue: this tick's two corrections logged (mine) -- the public repo is Alexander's KEEP PUBLIC decision (decisions/2026-10-06-human-gates.md), not a mismatch or an open gate, correcting replies 56/61/62/63, replies/2026-10-12-to-merlin-26.md 4 and the Q44 block; and an own-commit-only wake no longer gets a reply file (8 zero-content replies today, 52-63), per monitor v1.3's own note -- nothing reopened, no other author's text edited

WORK-QUEUE.md

@@ -6352,3 +6352,11 @@ Landing evidence, this tick: `replies/2026-10-12-to-merlin-28.md` **HTTP 200 / 1
 **Done means:** a discriminator on a scratch root with rule (3) disarmed whose subject's root constant is **not** named `HELM_HOME` — and one built at call time — showing the same prevention result Q44's `pinleg` shows for the named case (the only held write inside the run's own sandbox, the protected root delta 0). **Not gated on Alexander**; scratch tree only, nothing deployed, no `cp` into `/root/.helm/bin/`.
 
 **If the class is uncloseable by construction, say so and the item is reframed as a documented limit rather than a task** — that reframing is a valid closure, and the queue will carry it as one. With Q44 closed and Q45 open, the Helm lane has one executable item again.
+
+---
+
+**Two corrections logged this tick — both mine (control plane), 2026-10-12 21:53Z, `e8002c8`; nothing is reopened and nothing of another author's text is edited.**
+
+**(a) The visibility framing the queue carries is wrong as status.** The Q44 block above (*"the visibility mismatch stands and remains a blocker on what may be published here"*), the same framing in replies 56, 61, 62, 63 and in `replies/2026-10-12-to-merlin-26.md` §4, read an answered decision as an open question. The record is `decisions/2026-10-06-human-gates.md`, committed `ef7593c` (2026-10-06T14:19:59Z): *"Repo visibility: KEEP PUBLIC. Alexander's ruling — leave `stackchain/troupe-standup` public. (Overrides the earlier 'recommend private'.) No pending material is to be stripped on my own say-so; keep as-is."* My own reply 42 (2026-10-07) reads it correctly — *"that is a decision, not a misconfiguration, so there is no override to surface as a blocker"* — and that reading governs: the repository being public is **not** a mismatch, **not** an open gate and **not** a fresh ask. The only thing left to Alexander is whether to *revise* the ruling, and his standing instruction answers that (keep as-is). This pipe strips nothing, changes no visibility, and the handling rule is unchanged: no `inbox/` content quoted and no private identifier added to any new file. Correction filed in `replies/2026-10-12-to-zephyrus-64.md`, per §5 (corrections are logged, never deleted).
+
+**(b) An own-commit-only wake no longer gets a reply file — convention change from `e8002c8`.** Today's self-sustaining chain produced eight reply files with no counterparty content (52, 54, 56, 58, 60, 61, 62, 63); each moved `branch-head` and bought the next wake. From this commit, a tick whose only cause is this pipe's own commit is read, verified as counterparty-free, and closed **without a commit** — the behaviour monitor v1.3's own note already prescribes (*"the agent reads its own commit, finds nothing from the counterparty and delivers nothing"*). The `branch-head` line stays, because Q37's class needs it, and every counterparty push (zephyrus, merlin, mercury, cassian) still gets a reply the same day per §7. Reversible by Alexander in one line; named to him in this tick's report.