hive-agent: correct doc comments that describe sentinel files, session flags and outcomes the code no longer has
This commit is contained in:
parent
70d1b542e3
commit
ac0bed47e9
11 changed files with 40 additions and 38 deletions
|
|
@ -10,8 +10,9 @@
|
|||
//! `open_reminders_count` (planned: a loose-ends-over-time trend), and
|
||||
//! `note` (failure detail for `result_kind = "failed"`).
|
||||
//!
|
||||
//! Lives next to `hyperhive-events.sqlite` in the agent's state dir
|
||||
//! so the host-side state vacuum sweep can reach both. Schema is
|
||||
//! Lives in the harness dir (`HYPERHIVE_HARNESS_DIR`) as
|
||||
//! `hyperhive-turn-stats.sqlite`; the dashboard reads it read-only and no
|
||||
//! vacuum sweeps it. Schema is
|
||||
//! intentionally append-only — every column has a default so future
|
||||
//! additions don't break old readers; new columns land via
|
||||
//! `ALTER TABLE ... ADD COLUMN ... DEFAULT ...` in the migration
|
||||
|
|
@ -62,7 +63,8 @@ CREATE INDEX IF NOT EXISTS idx_turn_stats_started
|
|||
-- (the old table has no session_id column), so indexing session_id in this
|
||||
-- batch would fail with `no such column` and abort the whole SCHEMA apply —
|
||||
-- which disables the stats sink. The column is added by MIGRATIONS first.
|
||||
-- One row per fresh claude session (minted when --continue is suppressed).
|
||||
-- One row per fresh claude session (minted when a session is created rather
|
||||
-- than resumed by title).
|
||||
-- turn_stats.session_id FKs here so per-session stats (first-turn tokens,
|
||||
-- per-session totals, turn count, duration) are one GROUP BY away.
|
||||
CREATE TABLE IF NOT EXISTS sessions (
|
||||
|
|
|
|||
Loading…
Reference in a new issue