diff --git a/docs/turn-loop/mcp.md b/docs/turn-loop/mcp.md
index 40fcc11b..86f6b121 100644
--- a/docs/turn-loop/mcp.md
+++ b/docs/turn-loop/mcp.md
@@ -95,12 +95,11 @@ at_unix_timestamp?)`.
   payloads spill to `/agents/<self>/state/reminders/`. Pending count
   capped at 50 per agent (`HIVE_REMIND_MAX_PENDING_PER_AGENT`).
 
-There is no same-turn self-continue tool: ending the turn and letting
-an external wake drive the next one is always the right move — it
-checkpoints the session and observes wakes that only reach the harness
-between turns. Multi-step work rides `remind` for a durable self-wake,
-or an in-container todo wake (bash-task completion, forge notification,
-matrix activity) for work already in flight.
+There is no same-turn self-continue tool — see
+[Turn outcomes](README.md#turn-outcomes) for why. Multi-step work rides
+`remind` for a durable self-wake, or an in-container todo wake
+(bash-task completion, forge notification, matrix activity) for work
+already in flight.
 
 **Meta** (`meta` group): `set_status(text)`, `get_agent_meta(name?)`.
 
@@ -164,11 +163,9 @@ inject a wake-up event into the agent's inbox via the per-agent
 socket at `/run/hive/mcp.sock`. Speak the wire protocol directly —
 JSON-line over the unix socket: `{"cmd":"wake","from":"matrix","body":
 "new dm from @alice"}\n`. Same shape as any other `AgentRequest`; see
-`hive-sh4re::AgentRequest::Wake`. (An earlier `hive-agent-wake` CLI
-wrapper existed for this but was removed — no shipped co-process
-daemon actually shelled out to it; every one that wakes the harness
-(matrix, bash) dials the socket directly, so the raw protocol is the
-only path now.)
+`hive-sh4re::AgentRequest::Wake`. Every built-in producer that wakes
+the harness (matrix, bash) dials the socket directly — there is no
+CLI wrapper, just the raw protocol.
 
 The wake event lands in the broker as `{from:<label>,
 to:<agent>, body}`, waking whatever `recv` call the harness
@@ -199,7 +196,7 @@ than deriving from SSE events.
 
 `mcp::run_tool_envelope`: every MCP tool handler logs the request,
 runs the body, logs the result. Pre-/post-log only — the inbox
-status hint moved to the wake prompt + UI header.
+status hint lives in the wake prompt + UI header, not here.
 
 ## Tool whitelist (`mcp_config::ALLOWED_BUILTIN_TOOLS`)