Answer round 1 of the domain review of the approval mark and marked waits

The bus withholds a marked subject from a runner that does not honour the
mark again, as ADR 0286 has it; marks follow G's catalog half; a recording,
a stuck gate, an absent router and a start before the marks are read each
have a stated answer, so nothing runs unasked and nothing fails silently.

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

00-META/glossary.md

@@ -1120,8 +1120,8 @@ asking, never the act. **Decided by** ADR 0152, 0175, 0234, 0259, 0272, 0383, 03
   (ADR 0286). It covers a module's events and streams too (the operator, 2026-11-11; design 34 every-event §32): a
   module may mark one of its events, a restricted stream is marked whole, and a `mesh_wait` on a marked event runs
   only on the operator's warrant for that one wait, with the exact names it waits on and its bound, which the tool
-  runner asks and checks before it subscribes. The tool runner reads every mark from the manifests and the seat list
-  on the bus (design 46 7-approval-mark §5).
+  runner asks and checks before it subscribes. The tool runner reads every mark from the catalog half on the bus
+  (design 46 7-approval-mark §5).
 - **operator message / input** — what arrives on `intake`, once the router has checked the sender
   against its own list of the operator's identities: a **trusted** one is an operator message,
   addressed to an agent by `@name` or thread or else to the **responder** (`@mesh`, the router's own