hive-c0re: remove the dashboard's ask/answer surface

hive-c0re/src/coordinator.rs

@@ -445,19 +445,6 @@ pub struct ApprovalAdded<'a> {
     pub pr_number: Option<u64>,
 }
 
-/// Field-named payload for [`Coordinator::emit_question_added`].
-/// Mirrors the `QuestionAdded` dashboard-event fields; all references
-/// share the caller's lifetime.
-pub struct QuestionAdded<'a> {
-    pub id: i64,
-    pub asker: &'a str,
-    pub question: &'a str,
-    pub options: &'a [String],
-    pub multi: bool,
-    pub deadline_at: Option<i64>,
-    pub target: Option<&'a str>,
-}
-
 impl Coordinator {
     pub fn open(
         db_path: &Path,
@@ -839,71 +826,6 @@ impl Coordinator {
         });
     }
 
-    /// Emit `QuestionAdded` after a question is inserted. Fires for
-    /// both operator-targeted (`target = None`) and peer-to-peer
-    /// (`target = Some(agent)`) threads — the dashboard surfaces
-    /// both, distinguishing visually + offering operator override.
-    pub fn emit_question_added(&self, ev: &QuestionAdded<'_>) {
-        let &QuestionAdded {
-            id,
-            asker,
-            question,
-            options,
-            multi,
-            deadline_at,
-            target,
-        } = ev;
-        let asked_at = std::time::SystemTime::now()
-            .duration_since(std::time::UNIX_EPOCH)
-            .ok()
-            .and_then(|d| i64::try_from(d.as_secs()).ok())
-            .unwrap_or(0);
-        let question_refs = crate::dashboard::scan_validated_paths(question);
-        self.emit_dashboard_event(DashboardEvent::QuestionAdded {
-            seq: self.next_seq(),
-            id,
-            asker: asker.to_owned(),
-            question: question.to_owned(),
-            options: options.to_vec(),
-            multi,
-            asked_at: hive_sh4re::wire_time::from_secs(asked_at),
-            deadline_at: deadline_at.map(hive_sh4re::wire_time::from_secs),
-            target: target.map(str::to_owned),
-            question_refs,
-        });
-    }
-
-    /// Emit `QuestionResolved` when a question transitions to
-    /// answered (operator answer, peer answer, operator override on
-    /// a peer thread, operator cancel, or ttl watchdog). Both
-    /// operator-targeted and peer threads fire so the dashboard's
-    /// derived store can move the row from pending to history.
-    pub fn emit_question_resolved(
-        &self,
-        id: i64,
-        answer: &str,
-        answerer: &str,
-        cancelled: bool,
-        target: Option<&str>,
-    ) {
-        let answered_at = std::time::SystemTime::now()
-            .duration_since(std::time::UNIX_EPOCH)
-            .ok()
-            .and_then(|d| i64::try_from(d.as_secs()).ok())
-            .unwrap_or(0);
-        let answer_refs = crate::dashboard::scan_validated_paths(answer);
-        self.emit_dashboard_event(DashboardEvent::QuestionResolved {
-            seq: self.next_seq(),
-            id,
-            answer: answer.to_owned(),
-            answerer: answerer.to_owned(),
-            answered_at: hive_sh4re::wire_time::from_secs(answered_at),
-            cancelled,
-            target: target.map(str::to_owned),
-            answer_refs,
-        });
-    }
-
     /// Rebuild the per-container snapshot, diff it against the last
     /// one cached on `self`, and emit one
     /// `DashboardEvent::ContainerStateChanged` per added/changed row