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

docs/persistence.md

@@ -20,8 +20,8 @@ keeps its state, purging it doesn't.**
 
 Beyond that:
 
-- **Approvals and questions are kept forever** — they're audit trails,
-  not caches. Nothing about them ever ages out.
+- **Approvals are kept forever** — they're an audit trail, not a
+  cache. Nothing about them ever ages out.
 - **Broker messages**: acked ones vacuum after 30 days; anything
   undelivered or delivered-but-not-yet-acked is always kept, however
   old.
@@ -55,20 +55,11 @@ power-intent registry:
   ⚠️ The `mcp__hyperhive__remind` queue is **not** here any more: it
   moved to a harness-local, per-agent store as part of the
   loose-ends-v2 migration — see [`/harness/` contents
-  below](#state-dirs-per-agent) for where reminders (and todos, and
-  the questions mirror) actually live now.
+  below](#state-dirs-per-agent) for where reminders (and todos)
+  actually live now.
 - `approvals` — the queue. `agent / kind (merge_config_pr | spawn |
   init_config | update_meta_inputs | schedule_prompt) /
   commit_ref / requested_at / status / resolved_at / note`.
-- `operator_questions` — `ask` / `answer` queue (despite the
-  table name, stores both operator-targeted + agent-to-agent
-  questions since the `ask` rename).
-  `asker / question / options_json / multi / asked_at /
-  deadline_at (ttl) / answered_at / answer / target`. `target IS
-  NULL` = operator path (dashboard); `target = '<agent>'` = peer
-  Q&A (`HelperEvent::QuestionAsked` pushed into target's inbox,
-  answered via `Answer` request). Migrated via `ALTER TABLE ADD
-  COLUMN` against `pragma_table_info`.
 - `scheduled_prompts` — recurring + one-shot prompt queue.
   `owner / body / interval_seconds (NULL = one-shot) /
   next_fire_at_unix / created_at_unix / source ("operator" or
@@ -98,9 +89,8 @@ Retention:
   rows are always kept — the harness `ack_turn`s only after a
   successful turn, so an unacked row can still be requeued via
   `requeue_inflight` on a crash.
-- Approvals and questions are kept indefinitely — both are
-  audit trails. `actions::destroy` and answered questions stay
-  visible to anything that queries by id.
+- Approvals are kept indefinitely — an audit trail. `actions::destroy`
+  rows stay visible to anything that queries by id.
 - Scheduled prompts: one-shot rows are deleted on fire by the
   worker; recurring rows live until the operator cancels them
   (`cancel_schedule` MCP / dashboard ✗) which tombstones via
@@ -301,9 +291,9 @@ Under `/var/lib/hyperhive/agents/<name>/`:
     hours; non-terminal (still-running) tasks are never deleted. This
     used to be a host-side `hive-c0re` vacuum, moved in-container for
     the same privsep-ownership reason as the events vacuum above.
-  - `hyperhive-state.sqlite` — consolidated loose-ends-v2 store: todos,
-    reminders, and a questions mirror, one small table each in a single
-    file (in-container daemons — `hive-bash-daemon`, `hive-matrix-daemon`,
+  - `hyperhive-state.sqlite` — consolidated loose-ends-v2 store: todos
+    and reminders, one small table each in a single file (in-container
+    daemons — `hive-bash-daemon`, `hive-matrix-daemon`,
     `hive-forge-notify` — upsert keyed todos here over the harness's
     in-agent socket, `HIVE_AGENT_SOCKET`; the harness merges them into
     `get_loose_ends` output and clears a row on `mark_todo_done`).