docs: post-#598 catch up — hive-ag3nt/hive-m1nd → unified hive binary in turn-loop.md + CLAUDE.md

docs/turn-loop.md

@@ -5,7 +5,9 @@ claude has access to in return.
 
 ## The loop
 
-Each agent harness (`hive-ag3nt serve` or `hive-m1nd serve`) runs:
+Each agent harness (`hive serve`, with role picked from `$HIVE_ROLE`
+— `"agent"` for sub-agents, `"manager"` for the manager; post-#598
+this is one binary not two) runs:
 
 1. Long-poll `Recv` on its socket. The host-side broker
    (`broker.rs::recv_blocking_batch`) returns immediately if there's
@@ -263,10 +265,12 @@ External MCP servers (and any other in-container process) can
 inject a wake-up event into the agent's inbox via the per-agent
 socket at `/run/hive/mcp.sock`. Two equivalent paths:
 
-- **Shell out to `hive-ag3nt wake --from <label> --body <text>`**
+- **Shell out to `hive wake --from <label> --body <text>`**
   (use `--body -` to read body from stdin). Already on the
   container's `PATH` since the harness binary is in
   `systemPackages`. Convenient for shell-script integrations.
+  Agent-only today (refused when `HIVE_ROLE=manager`); see
+  [#693](http://localhost:3000/hyperhive/hyperhive/issues/693).
 
 - **Speak the wire protocol directly** — JSON-line over the
   unix socket: `{"cmd":"wake","from":"matrix","body":"new dm