docs(web-ui): document the first-turn ctx stats chip
The per-agent stats page gained a "first-turn ctx" summary chip (the input tokens of the most recent fresh session's first turn — a system-prompt/CLAUDE.md sprawl proxy), but agent.md's chip-row description didn't mention it. Add it next to the reminder chips, noting the stats.rs derive and the inert-until-capture behaviour (omitted from JSON until the sessions / turn_stats.session_id capture has rows).
This commit is contained in:
parent
0d013aefbb
commit
48347a01c9
1 changed files with 9 additions and 1 deletions
|
|
@ -393,7 +393,15 @@ hit-rate** (`cache_read` over all input-side tokens) and
|
|||
**tokens/turn**. When `reminder_stats` is present (fetched via
|
||||
`ReminderRollup` RPC and merged into the snapshot in
|
||||
`web_ui.rs::api_stats`) three more chips appear: **reminders
|
||||
scheduled / delivered / pending** for the window.
|
||||
scheduled / delivered / pending** for the window. When the
|
||||
per-session capture has data, a **first-turn ctx** chip shows the
|
||||
input tokens of the most recent fresh claude session's first turn —
|
||||
a proxy for system-prompt + CLAUDE.md sprawl (a fresh session's first
|
||||
turn pays the full static prefix uncached). It's derived in `stats.rs`
|
||||
(`first_turn_ctx`: the first turn, `ORDER BY started_at LIMIT 1`, of
|
||||
the latest `sessions` row in the window) and is omitted from the JSON
|
||||
until the `sessions` / `turn_stats.session_id` capture has rows — so
|
||||
the chip stays hidden on older dbs (inert-until-capture).
|
||||
`stats.rs` opens the sqlite db read-only and degrades to an
|
||||
empty snapshot on any error — the page is decorative, never
|
||||
authoritative.
|
||||
|
|
|
|||
Loading…
Reference in a new issue