ask: rename ask_operator → ask + optional 'to' for agent-to-agent Q&A

docs/turn-loop.md

@@ -107,10 +107,18 @@ it as a stdio child via `--mcp-config`. The hyperhive socket name is
   "anything pending?" peek. Positive value parks the turn up
   to that many seconds (cap 180) — incoming messages wake
   instantly, otherwise returns empty at the timeout.
-- `ask_operator(question, options?, multi?, ttl_seconds?)` —
-  surface a question on the dashboard. Same shape as the manager's;
-  answer routes back to the asker's own inbox as
-  `HelperEvent::OperatorAnswered` via `coord.notify_agent`.
+- `ask(question, options?, multi?, ttl_seconds?, to?)` —
+  surface a structured question. Same shape as the manager's;
+  recipient defaults to the operator (dashboard) but can be set
+  to a peer agent name via `to: "<agent>"`. Answer routes back
+  to the asker's own inbox as `HelperEvent::QuestionAnswered`
+  via `coord.notify_agent`. For peer questions the recipient
+  sees a `HelperEvent::QuestionAsked` event and replies with
+  `answer(id, answer)`.
+- `answer(id, answer)` — respond to a `question_asked` event
+  routed to this agent. Authorisation is strict: only the
+  declared target (or the operator via the dashboard) can
+  answer.
 
 ### Waking the agent from inside the container
 
@@ -167,16 +175,22 @@ meta's.
 - `request_apply_commit(agent, commit_ref)` — submit a config
   change for any agent (`hm1nd` for the manager's own config) for
   operator approval.
-- `ask_operator(question, options?, multi?, ttl_seconds?)` —
-  surface a question on the dashboard. Non-blocking — returns the
-  queued question id; the operator's answer arrives later as
-  `HelperEvent::OperatorAnswered` in the manager inbox. Options
-  always render alongside a free-text fallback; `multi=true`
-  renders options as checkboxes. `ttl_seconds` auto-cancels with
-  answer `[expired]` after the deadline (useful for time-sensitive
-  decisions that become moot if the operator hasn't responded).
-  The operator can also manually cancel with `[cancelled]` via the
-  dashboard.
+- `ask(question, options?, multi?, ttl_seconds?, to?)` —
+  surface a structured question to the operator (default) or a
+  sub-agent (`to: "<agent>"`). Non-blocking — returns the
+  queued question id; the answer arrives later as
+  `HelperEvent::QuestionAnswered { id, question, answer,
+  answerer }` in the asker's inbox. Options always render
+  alongside a free-text fallback; `multi=true` renders options
+  as checkboxes. `ttl_seconds` auto-cancels with answer
+  `[expired]` (and `answerer: "ttl-watchdog"`) after the
+  deadline (useful for time-sensitive decisions that become moot
+  if no one has responded). The operator can also manually
+  cancel with `[cancelled]` via the dashboard.
+- `answer(id, answer)` — respond to a `question_asked` event
+  that was routed to the manager (a sub-agent did
+  `ask(to: "manager", ...)`). Surfaces in the asker's inbox as
+  the same `question_answered` event.
 
 The boundary: lifecycle ops on *existing* sub-agents
 (`kill`/`start`/`restart`) are at the manager's discretion — no