hive-agent: remove the in-container questions mirror

This commit is contained in:
damocles 2026-08-29 21:28:37 +02:00
commit c865114743
7 changed files with 59 additions and 528 deletions

View file

@ -40,19 +40,25 @@ pub fn harness_dir() -> PathBuf {
hive_agent_sock::paths::harness_dir()
}
/// Consolidated harness-local state db — todos + reminders + the questions
/// mirror, one table each — mutable per-agent state the harness owns, kept
/// out of the append-only `hyperhive-events.sqlite` sink. Per mara's call
/// ("not yet another sqlite! todos, reminders, questions should be like
/// three tiny tables in one 500kb sqlite"), this file is the shared home
/// for all loose-ends-v2 stores; each store's `open()` only applies its own
/// Consolidated harness-local state db — todos + reminders, one table
/// each — mutable per-agent state the harness owns, kept out of the
/// append-only `hyperhive-events.sqlite` sink. Per mara's call ("not yet
/// another sqlite! todos, reminders, questions should be like three tiny
/// tables in one 500kb sqlite"), this file is the shared home for the
/// loose-ends-v2 stores; each store's `open()` only applies its own
/// `CREATE TABLE IF NOT EXISTS`, so opening multiple stores against the
/// same path is safe (distinct table names, no schema collision).
/// All three stores (todos, reminders, questions) open this same path
/// directly (see their `open()` call sites) — distinct table names mean no
/// schema collision, so there's no need for per-store path wrapper fns here.
/// same path is safe (distinct table names, no schema collision). Both
/// stores (todos, reminders) open this same path directly (see their
/// `open()` call sites) — distinct table names mean no schema collision,
/// so there's no need for per-store path wrapper fns here.
///
/// Before this consolidation, todos and reminders lived in their own
/// ⚠️ A pre-existing harness may still carry a third table here, `questions`
/// — the mirror this file's own doc comment used to describe as one of
/// three. It's gone now that the ask/answer mechanism itself has been
/// removed: nothing opens or writes it any more, so any rows already in
/// it are inert, harmless leftovers, not a store to migrate or clean up.
///
/// Before the todos/reminders consolidation, they lived in their own
/// `hyperhive-todos.sqlite` / `hyperhive-reminders.sqlite` files; a
/// one-time boot migration (`db_migrate::run`) folds those into this path
/// the first time a harness boots after the upgrade.