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

docs/approvals.md

@@ -598,12 +598,6 @@ renders only for the root agent. The root agent's approval-gating
 behaviour comes from its CLAUDE.md / agent-specific instructions, not
 the system prompt template.
 
-Any agent (root or not) can also ask a structured question of the
-operator or a peer agent via the `ask`/`answer` MCP tools, independent
-of the approval flow above — see
-`docs/conventions.md#question-routing-ask--answer` for the routing
-rules, `ttl_seconds` expiry, and cancellation.
-
 ## Helper events to the submitting agent
 
 `Coordinator::notify_submitter(approval_id, &HelperEvent)` routes the
@@ -635,18 +629,6 @@ root agent. Variants (`hive_sh4re::manager::HelperEvent`):
 - `NeedsUpdate { agent }` — sub-agent's recorded flake rev is
   stale. The root agent calls `update(name)` to rebuild — idempotent,
   no approval required.
-- `QuestionAnswered { id, question, answer, answerer }` — peer
-  `Answer` request (answerer = agent name) or ttl watchdog expiry
-  (answerer = `"ttl-watchdog"`, answer = `"[expired]"`). The dashboard's
-  own `/answer-question/{id}` trigger (answerer = `"operator"`) is
-  gone — removed along with the rest of the dashboard's ask/answer
-  surface, so an operator-targeted question now has no path to an
-  answer at all.
-- `QuestionAsked { id, asker, question, options, multi }` —
-  fired when an agent calls `Ask { to: Some(<this-agent>), ... }`.
-  The recipient responds via `Answer { id, answer }` and the
-  asker sees the matching `QuestionAnswered`.
-
 The remaining lower-urgency lifecycle notices — `Rebuilt`, `Killed`,
 `Destroyed`, `NeedsLogin`, `LoggedIn`, `ConfigReady` — are "FYI, check
 when convenient" events with no reason to drive an immediate turn, so
@@ -668,11 +650,11 @@ or the dashboard `↻ R3BU1LD` button when the lock didn't move). When set,
 bootstrap container yields the exact tree that was referenced.
 
 To add a new lifecycle notice: if it needs to drive an immediate turn
-(a live conversation like `Ask`/`Answer`, or something genuinely
-urgent), add a `HelperEvent` variant + call sites + update
-`prompts/system.md`'s message-event list. If it's "FYI, check when
-convenient," call `push_todo`/`push_todo_submitter` directly instead —
-no new wire type needed.
+(something genuinely urgent, like `ContainerCrash`), add a
+`HelperEvent` variant + call sites + update `prompts/system.md`'s
+message-event list. If it's "FYI, check when convenient," call
+`push_todo`/`push_todo_submitter` directly instead — no new wire type
+needed.
 
 ## Auto-update on startup