hive-c0re, docs: sweep remaining stale ask/answer-dashboard references

This commit is contained in:
damocles 2026-08-29 23:28:32 +02:00
commit 46183795dd
6 changed files with 47 additions and 50 deletions

View file

@ -7,10 +7,12 @@
//! and no longer sourced from here (loose-ends-v2's questions phase) —
//! c0re remains the `Ask`/`Answer` routing + delivery rendezvous
//! (`coord.questions`), it just isn't asked for the *pending-view*
//! rendering anymore. The
//! operator dashboard's questions pane is unaffected: it reads
//! `coord.questions.pending_all()` directly (`dashboard/state_snapshot.rs`),
//! independent of this module.
//! rendering anymore. ⚠️ The operator dashboard no longer has any
//! question-pending view either — its whole questions pane, the
//! `pending_all()`/`recent_answered_all()` reads that fed it, and the
//! `/api/answer-question`/`/api/cancel-question` endpoints are gone
//! (removed along with the rest of the dashboard's ask/answer surface).
//! An operator-targeted `ask()` now has no reader anywhere.
//!
//! Call frequency is low (an agent doing self-introspection between
//! turns), so the sweep happens fresh every time — no caching, no

View file

@ -105,13 +105,15 @@ impl OperatorQuestions {
}
/// Mark a pending question answered. `answerer` is who's actually
/// answering: `"operator"` for the dashboard path, or an agent's
/// own name when responding via `Answer`. Authorisation:
/// answering: `"operator"`, or an agent's own name when responding
/// via `Answer`. Authorisation:
///
/// - Operator-targeted questions (`target IS NULL`) can only be
/// answered by `"operator"`. (Agents must not be able to spoof
/// answers to operator questions — the dashboard is the
/// privileged path.)
/// answers to operator questions — though as of the dashboard's
/// ask/answer surface being removed, nothing currently calls
/// this with `answerer = "operator"` for a `target IS NULL` row
/// at all; the check stays as a guard, not a live path.)
/// - Agent-targeted questions can only be answered by the
/// declared target agent, OR by `"operator"` (operator override
/// for stuck threads — useful when an agent is offline/down