hive-c0re/hive-sh4re: remove the ask/answer wire protocol + core routing

hive-agent-mcp/README.md

@@ -9,7 +9,7 @@ would hit. HTTP is the sole transport; there is no stdio mode here.
 ## When to use it
 
 This is where the core hyperhive tool surface lives: `send`, `recv`,
-`ask`/`answer`, `remind`, `get_loose_ends`, `set_status`,
+`remind`, `get_loose_ends`, `set_status`,
 `get_agent_meta`, lifecycle (`kill`/`start`/`restart`/`update` on
 direct children), scheduling, and the approval-request tools. Reach
 for this crate when you're adding or changing a built-in tool rather
@@ -25,7 +25,7 @@ or their own daemon instead of living here.
   in-agent socket the `hive-agent` harness serves.
 - **`client.rs`** — socket client to the hyperhive broker.
 - **`send_allow.rs`** — enforces the per-agent
-  `hyperhive.allowedRecipients` allow-list on `send`/`ask`.
+  `hyperhive.allowedRecipients` allow-list on `send`.
 - **`paths.rs`** — socket + state path resolution shared with the
   harness's own `paths.rs` conventions.