observelisted

# observe , the control plane from an agent session ## Scope and triggers More trigger phrases: "cache hit rate", "debt score", "replay run <rid>", "gate log for <rid>", "conformance", "observability numbers". All surfaces are CLIs under `lib/bench`; agents should prefer the JSON verbs over parsing HTML. Every observability surface is a stdlib-only CLI in `lib/bench/` (resolve the kit root via `$DWARVES_KIT` or this skill's own location). Prefer JSON verbs; render HTML only when a human will look at it. ## Query numbers (agent surface, JSON) ```sh python3 lib/bench/dashboard.py stats # fleet + money + debt + alerts, one blob python3 lib/bench/dashboard.py debt --format json # cognitive-debt score alone python3 lib/bench/dashboard.py allocation --period week --budget N --format json ``` `allocation` answers the lead's question: where the pool went (member → feature, feature = git branch), period over period, plus a proposed next-period allowance plan. `--format md` emits the weekly/monthly report as paste-ready markdown. `stats` keys: `fleet` (runs, gate counts, override/misfire rates, conformance), `money` (computed spend, token mix, cache-hit, per-model), `debt` (score, open defers, last paydown), `alerts` (rule id + firing). Money is COMPUTED from list prices, an estimate, not an invoice; say so when reporting spend. ## Replay and inspect runs The run TUI is a forge product (`forge/cli/forge-tui`), standalone stdlib, and it mirrors the agent verb