Owen Lin 5f79a92e39 Persist response token usage in rollout history (#41912) ...

## Why

Resumed threads need to continue per-turn and per-thread token totals without scanning arbitrarily far beyond the latest compaction checkpoint.

## What changed

- Add durable `TokenUsageRecord` rollout items with response, turn, thread, session, and root-turn attribution.
- Restore accumulated usage on resume and snapshot the latest record plus the compaction response ID in compaction checkpoints.
- Preserve root-turn lineage in persisted turn context, while ensuring forked child threads start with their own usage totals.

## Testing

- Cover usage accumulation across multiple responses and resumed turns.
- Cover local and remote compaction checkpoints, invalid remote compaction output, rollout reconstruction, and fork isolation.

GitOrigin-RevId: ef9e0c4a9102a08a2c382be4cdac68c84353c90a

2026-08-31 21:15:38 +00:00

..

src

Persist response token usage in rollout history (#41912)

2026-08-31 21:15:38 +00:00

templates

Densify and version memory summaries (#23148)

2026-05-18 09:59:34 +02:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

2026-06-13 21:43:39 -07:00

Cargo.toml

feat: use provider defaults for memory models (#27129)

2026-06-09 23:49:09 +00:00