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
This commit is contained in:
Owen Lin authored and copyberry committed 2026-08-31 21:15:38 +00:00
1 parent a7913390f7
commit 5f79a92e39
67 files changed
+932 -162

No files matched your search

+2 -4
View File
@@ -3544,8 +3544,6 @@ async fn guardian_ephemeral_retry_preserves_parallel_trunk_and_fork_history() ->
)
.await;
// A conflicting input removes the known root while the trunk review is in flight.
turn.turn_metadata_state.mark_root_turn_ambiguous();
let third_decision = review_approval_request(
&session,
&turn,
@@ -3570,8 +3568,8 @@ async fn guardian_ephemeral_retry_preserves_parallel_trunk_and_fork_history() ->
for (body, expected_root) in [
(&first_request_body, Some("causal-root-turn")),
(&second_request_body, Some("causal-root-turn")),
(&failed_ephemeral_request_body, None),
(&retried_ephemeral_request_body, None),
(&failed_ephemeral_request_body, Some("causal-root-turn")),
(&retried_ephemeral_request_body, Some("causal-root-turn")),
] {
assert_parent_turn(body, Some(turn.sub_id.as_str()))?;
assert_root_turn(body, expected_root)?;