## B. Do NOT arm a relay — you are already delivered

<!-- [doc->REQ-SKILL-LIVE-SPT-HOSTED-BRANCH] spt-hosted arm; the normal-session arm is live-normal.md -->

This session is **spt-hosted** — it was launched by the spt daemon and is
**broker-delivered**. Your perch is already bound and inbound messages already reach you
automatically, on your existing turn as the `<sptc_messages>` the hook injects, exactly as your
SessionStart brief said.

**Do NOT arm a Monitor listener.** An in-session `spt api listen` **cannot** re-arm an spt-hosted
perch and will only fault: the Monitor's `bash.exe` child breaks by-pid `host_binaries` resolution
(**ADAPTER_UNRESOLVED**), and the Monitor-child pid breaks seed lineage (**NO_SEED**).

You are already live and reachable — go straight to C, then reply-and-continue. To reach someone,
`spt send <target>` and continue; any reply surfaces on your turn on its own. Your commune/signoff
mechanics (including the `!!wake!!` marker) already rode your SessionStart brief — re-read it there
rather than expecting them here.