hub force-leave/kick verb (250k quarantine actuator) with check-in gate

Elazar GO'd via nw-venus-cc handoff mritxd4ugalm. Hub needs a privileged force-leave-ARO capability (aro_leave is caller-scoped today; monitor scrp-context_monitor-venus can't remove another agent). Use: agent stuck >250k, unresponsive, quarantine = remove from all AROs so fan-outs stop waking it. CRITICAL (Elazar): never kick blind on a stale over-budget snapshot. TWO-PHASE: (1) check-in — hub DMs target asking current context size / did-it-compact, with a deadline; (2) resolve — ANY coherent reply by deadline CANCELS kick + notifies requester to re-read next cycle (reply=alive, not the target); NO reply by deadline -> execute force-leave all AROs, RECORD removed memberships for restore, notify target+requester. Primary signal = reply-vs-no-reply, hub does NOT parse token counts. Authorize caller to {elazar, monitor identity, role=pm}; cannot kick elazar/hub/monitor. PM-seat: kicked agent PMing an ARO must trigger existing aro_leave auto-succession. Restore via /unquarantine or session-start rejoin. coder: bring guarantees + attack cases (unauthorized caller, double-kick idempotency, reply-at-deadline race, membership restore completeness, PM-succession). Audit via audit-llmmsgsrv-ca; I gate+bounce.