Owen Lin aac9f84247 Preserve legacy semantics during rollout migration (#37191) ...

## Why

Legacy rollouts can contain historical rollbacks, compaction checkpoints, and
subagent copies of parent history. Migrating those records verbatim can change
the visible conversation or the model context used when a thread resumes, and
can retain large amounts of duplicated subagent history.

## What changed

- Plan and replay historical rollbacks by logical turn, preserving surviving
  lifecycle events and the correct compaction anchor for future resumes.
- Migrate subagent rollouts from a safe bounded replay when possible and record
  the history boundary so copied parent context is not projected as child turns.
- Include archived and compressed rollouts while keeping their storage form and
  location intact.
- Tolerate malformed, partial, oversized, and empty JSONL records during the
  migration scan.

## Testing

Add coverage for rollback and compaction combinations, subagent replay bounds,
archived and compressed rollouts, recovery, concurrent maintenance, and damaged
JSONL input.

GitOrigin-RevId: 3948e16d43f75df8571b0a92af12a181d1d08fdf

2026-08-06 00:54:14 +00:00

..

src

Preserve legacy semantics during rollout migration (#37191)

2026-08-06 00:54:14 +00:00

BUILD.bazel

Extract rollout into its own crate (#15548)

2026-03-24 18:10:53 -07:00

Cargo.toml

Honor the configured SQLite home across state consumers (#34994)

2026-07-23 19:19:35 +00:00