DL-211

The agent-side ask round-trip rides the comms transport: raise = a dedicated native comms_post_ask tool posting PostMessage(MessageBlock{ask}) onto the agent’s home channel into a named topic/thread (like comms_post_message), non-blocking; consume = AskAnswerControl over the control lane, correlated by server-minted ask_id. The session stays observe+stop only (no promptable session; no reply path). The session-id keying of the answer wake is a wart — an owed answer is keyed on the agent HANDLE, delivered to whatever session is next live for it (a runner/hub delivery-lane fix, entangled RIG-1310); when the asking agent is not live the human decides recovery (relaunch it, or route the answer to a new agent) — deliberately no agent-side boot poll

Status: Active (Matt, 2026-08-18)

Record: ../../agent/compass-ask-comms-roundtrip/design.md#approach