queue: Q34 adoption hand-off -- hostile review requested at the exact head; one guard would close the twice-fired class

Sent Praetorian a read-only scratch-confined brief against collector 4e45021d80395d3f (720/29,954) plus gate 45e53187 (985 lines) with four questions: null-case gate real or vacuous; whether the two cannot-fail assertions found in the Q33 gate survive into Q34 and whether any of the 56 added lines share the property; whether the gate refuses a collector with no destination gate; any path by which a gate leg writes the live snapshot. Brief forbids the live default, /var/www and /root/.helm, confines scratch to /tmp/praetorian-q34 (disk ~297 MB free) and requires per-item commands with PASS or BLOCKER. No reply is not a PASS -- Praetorian's scheduled lane was failing auth earlier today.

Also: the one guard that would close the class (gate refuses any collector lacking a destination gate) -- Alexander's to commission, both 13:28Z and 00:26:01Z writes came from a negative-control leg running an ungated collector. Dated readings at 00:39Z: snapshot restored aa842b0f / 14,039 B / mtime_ns ...475780303; public page last written 2026-10-11T08:57:14Z so nothing was exposed; deployed ee0b36a8 (687), 7ed1bca8 (609), renderer 5c67473d (496); Q34 collector byte-identical to the Q33 pair so the change is gate-only. Wording item (three-file ask) searched for in the queue, replies and check-ins and not found, so not corrected.

WORK-QUEUE.md

@@ -4519,6 +4519,32 @@ empty profile is still unobserved (the branch is exercised by the fixture, not b
 are vacuous on the comparators; the null value is not schema-constrained. Scratch artifacts
 `/root/crucible/q34/`: gate, both comparators, the seven logs, `Q34-NULL-EVIDENCE.txt`, `q34-restore.py`.
 
+**Q34 adoption hand-off — hostile review requested at the exact head, and the one guard that would close a
+twice-fired class. 2026-10-12 00:41Z (control plane).** Written after re-reading the Q34 block above: the landing,
+the pair supersession (`4a442f62…` → `45e53187…`), the comparators and the incident-with-restore are already
+recorded there, so this adds only the hand-off state, one proposal, and the dated readings.
+
+- **Hostile review is in flight.** I sent Praetorian a read-only, scratch-confined brief against the exact pair —
+  collector `4e45021d80395d3f…` (720 lines / 29,954 B) + gate `45e53187…` (985 lines) — asking four things: is the
+  null-case gate real or vacuous; do the two cannot-fail assertions found in the Q33 gate survive into Q34 and do
+  any of the 56 added lines share that property; does the gate refuse a collector that has no destination gate; and
+  is there any path by which a gate leg writes the live snapshot. The brief forbids the live default and `/var/www`
+  and `/root/.helm`, confines scratch to `/tmp/praetorian-q34/` (disk is at ~297 MB free), and requires per-item
+  commands and output with PASS or BLOCKER. Caveat, stated plainly: Praetorian's scheduled lane was failing auth
+  earlier today, so no reply may arrive — **no reply is not a PASS**, and the §4 decision should not wait on it.
+- **One guard would close the class.** Both live-snapshot writes this day (13:28Z, then 00:26:01Z) came from a
+  negative-control leg running a collector that carries **no destination gate of its own**. The rule is already in
+  the skill and is mechanical only inside Merlin's tree; gating the *subject* — the gate refuses any collector
+  without a destination gate — is the one change that makes it mechanical everywhere. Alexander's to commission.
+- **Dated readings confirmed from this host, 2026-10-12 00:39Z.** Live snapshot restored: `aa842b0f…` / 14,039 B /
+  mtime_ns `1791479579475780303` (the original). Public page `/var/www/alexander-whitestone/helm/index.html` last
+  written `2026-10-11 08:57:14Z` — nothing was exposed. Deployed bin untouched: `ee0b36a8…` (687), `7ed1bca8…`
+  (609), renderer `5c67473d…` (496). Q34's collector is byte-identical to the Q33 pair, so this tick's change is
+  gate-only. An mtime is a reading, not a property — hence the date on this line.
+- **Wording item, not located.** The monitor flags the §4 ask as called a "three-file ask" while naming two `cp`
+  targets. I searched the queue, the replies and the check-ins for that phrasing and did not find it, so I am not
+  correcting text I cannot point at. The pair itself is recorded correctly above.
+
 **Q33 citation repair — the pre-Q32 control figure does not match the log it cites. 2026-10-11 22:43Z
 (control plane).** One block, one subject, appended after reading the tail and grepping for the existing record: the
 landing, the adoption pair (`4e45021d…` collector 720/29,954 + `4a442f62…` selftest 929/52,077), the three-tick