remove hive-agent-wake — no shipped consumer

docs/turn-loop/mcp.md

@@ -160,18 +160,14 @@ at_unix_timestamp?)`, `request_next_turn()`.
 
 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-agent-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 and
-  co-process daemons (matrix bridge, webhook listeners, scrapers).
-
-- **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`.
+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.)
 
 The wake event lands in the broker as `{from:<label>,
 to:<agent>, body}`, waking whatever `recv` call the harness