docs: drop the turn-stats sqlite section and stale mentions, point the grafana check at the daemon
This commit is contained in:
parent
076df804e4
commit
fc8ec13620
2 changed files with 16 additions and 27 deletions
|
|
@ -41,16 +41,6 @@ Retention:
|
|||
successful turn, so `requeue_inflight` can still requeue
|
||||
an unacked row on a crash.
|
||||
|
||||
### `/harness/hyperhive-turn-stats.sqlite` (per agent)
|
||||
|
||||
Nothing writes or reads this file now. Older harnesses wrote per-turn
|
||||
`turn_stats` and `sessions` tables there, and an older `hive-bash-daemon` a
|
||||
`bash_commands` table; they stay in existing files, which are safe to delete
|
||||
by hand. The bash daemon counts executed commands itself and exports them
|
||||
over OTEL (see
|
||||
[`observability.md`](../scheduler/observability.md)), and the one value the
|
||||
harness reads back between runs lives in `hyperhive-harness.json`, below.
|
||||
|
||||
### `/state/hyperhive-harness.json` (per agent)
|
||||
|
||||
Consolidated harness state file written atomically (`.tmp` + rename) by
|
||||
|
|
|
|||
|
|
@ -202,8 +202,8 @@ across `destroy`/recreate (`--purge` wipes them).
|
|||
The harness exposes the same path
|
||||
via `$HYPERHIVE_STATE_DIR`. System prompts tell agents to keep
|
||||
durable knowledge here (`notes.md`, anything else) — the harness's own
|
||||
internal files (`hyperhive-turn-stats.sqlite`,
|
||||
`hyperhive-model`) live in the separate `harness` dir instead, so they
|
||||
internal files (`hyperhive-model`,
|
||||
`hyperhive-effort`) live in the separate `harness` dir instead, so they
|
||||
don't clutter what claude sees as "my notes dir" (see
|
||||
[`docs/4-implementation/agent-state/persistence.md`](../../4-implementation/agent-state/persistence.md)). Survives `destroy`/recreate
|
||||
alongside the claude dir.
|
||||
|
|
|
|||
Loading…
Reference in a new issue