remove request_next_turn: same-turn continuation is always worse than an external wake

docs/turn-loop/mcp.md

@@ -80,7 +80,7 @@ shapes and routing logic in
 
 **Inbox** (`inbox` group): `get_loose_ends(agent?)`,
 `cancel_loose_end(kind, id)`, `remind(message, delay_seconds? |
-at_unix_timestamp?)`, `request_next_turn()`.
+at_unix_timestamp?)`.
 
 - `get_loose_ends(agent?)` — list pending questions (asked/owed),
   scheduled reminders, and active local tasks published by external MCP
@@ -97,9 +97,15 @@ at_unix_timestamp?)`, `request_next_turn()`.
 - `remind` — schedule a reminder in this agent's own inbox. Large
   payloads spill to `/agents/<self>/state/reminders/`. Pending count
   capped at 50 per agent (`HIVE_REMIND_MAX_PENDING_PER_AGENT`).
-- `request_next_turn` — ask the harness to start another turn
-  immediately after this one ends, even if the inbox is empty.
-  Next turn fires with `from: "self"` and `body: "continue"`.
+
+There is no same-turn self-continue tool (`request_next_turn` was
+removed — unanimous consensus across every agent that used the harness
+that ending the turn and letting an external wake drive the next one
+is strictly better: it checkpoints the session and observes wakes that
+only reach the harness between turns, forge #2777). 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?)`.