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

docs/conventions.md

@@ -171,46 +171,6 @@ cutoff so a later `AckTurn` doesn't double-update and a stale
 redelivery tag can't outlive its row. The operator-side sibling is
 the dashboard's "mark all read" (unbounded, per-agent).
 
-### Question routing (Ask / Answer)
-
-`AgentRequest::Ask` (and the manager-flavour mirror) surfaces a
-structured question that either lands in the operator-question queue
-or in a peer agent's inbox. The recipient is the `to` field:
-
-- `to = None` or `to = Some("operator")` — routes to the
-  operator-question queue. ⚠️ The dashboard's whole ask/answer
-  surface (the UI that used to render this queue and let the operator
-  reply) has been removed — an operator-targeted question currently
-  has no reader anywhere; this routing case is being removed too as
-  the same effort continues. The legacy `AskOperator` variant
-  collapses into this case.
-- `to = Some(<agent>)` — peer Q&A. The target agent receives a
-  `HelperEvent::QuestionAsked { id, asker, question, options, multi }`
-  in their inbox. They reply via `AgentRequest::Answer` (or
-  `ManagerRequest::Answer` if they're the manager); the answer
-  threads back to the asker as a `HelperEvent::QuestionAnswered`
-  event.
-
-Shape fields are uniform across both targets:
-
-- `options` is advisory — a list is never enforced; peer-agent
-  recipients see it in their `QuestionAsked` event and can return any
-  string regardless.
-- `multi = true` is a hint that the answerer should treat `options` as
-  a multi-select rather than pick-one. The answer comes back as a
-  single string with selections joined by `", "`.
-- `ttl_seconds` auto-cancels with answer `[expired]` (and `answerer:
-  "ttl-watchdog"`) when the wait becomes moot. `None` = wait
-  indefinitely or until manual cancel.
-
-Response shape is always `QuestionQueued { id }` — the asker stores
-the id and correlates the asynchronous answer event when it lands.
-Authorisation on `Answer`: only the question's `target` agent, or the
-operator, is permitted to reply; an answer attempt from anyone else
-fails the wire-side check. (The operator's only path to invoke this
-was the now-removed dashboard — see the note above; the
-authorisation rule itself is unchanged.)
-
 ### Loose-ends wire shape
 
 `LooseEnd` is the per-row response shape for `GetLooseEnds` (both
@@ -220,15 +180,12 @@ privileged bot, etc.) can land later without breaking existing
 handlers. Each row carries enough context that the caller renders
 it directly as a bulleted list, no follow-up fetch needed.
 
-Per-flavour scoping is uniform across the three variants:
+Per-flavour scoping is uniform across the two cancellable variants:
 
 - **agent-flavour** `GetLooseEnds` only surfaces rows the calling
   agent has standing in. `Approval` rows only appear when the
   calling agent is the manager (sub-agents don't submit
-  approvals). `Question` rows surface where the agent is `asker`
-  OR `target` (the routing semantics from the Ask/Answer
-  subsection above). `Reminder` rows are scoped to `owner ==
-  self`.
+  approvals). `Reminder` rows are scoped to `owner == self`.
 - **manager-flavour** `GetLooseEnds` lists every pending row in
   the swarm — full audit view.
 
@@ -240,9 +197,6 @@ Per-variant fields:
   blurb shown on the dashboard card. `commit_ref` is the
   kind-specific payload (see `docs/approvals.md::Approval kinds
   (wire shapes)`).
-- `Question { id, asker, target?, question, age_seconds }` —
-  `target = None` = operator-routed (dashboard); `Some(agent)` =
-  peer-to-peer thread.
 - `Reminder { id, owner, message, due_at, age_seconds }` —
   `due_at` is the absolute time the scheduler is targeting (RFC
   3339 on the wire, see *Timestamps on the wire* below); clients
@@ -265,10 +219,9 @@ unsynchronised wall clock, etc.) so the bulleted list never
 shows nonsense ages.
 
 `CancelLooseEnd { kind, id }` is the matching write surface. The
-`kind` enum (`Question` / `Reminder` / `Approval`) selects which
-underlying store the dispatcher reaches into. `Question` and
-`Reminder` cancel from either surface subject to ownership
-checks (asker for the question, scheduler for the reminder).
+`kind` enum (`Reminder` / `Approval`) selects which underlying store
+the dispatcher reaches into. `Reminder` cancels from either surface
+subject to an ownership check (the scheduling agent).
 `Approval` is manager-only — sub-agents don't submit approvals
 so they have nothing of their own to withdraw; their wire
 surface returns a clear error if they try. Cancelling an approval