Ruslan Nigmatullin 9e6d1c5278 Preserve retained assistant revisions across rollout replay (#60839) ...

## Why

Replaying delivered assistant messages allocates new retained-source revisions instead of preserving those captured in live history.

## What changed

- Capture retained sources when recording assistant deliveries, persist them in rollout metadata, and reuse their revisions during replay.
- Add optional `next_item_ordinal` compaction metadata and a `next_model_id_ordinals` helper to recover item and window allocation positions from checkpoints and subsequent records. Ignore allocation metadata that refers to other threads.

## Testing

Extend tests to compare live and replayed delivery sources, preserve revisions through an older reader's rewrite, and verify ordinal recovery from checkpoints and subsequent local items.

GitOrigin-RevId: cfdeebe8e13b1700b34b9c98696880a90a99ace5

2026-11-11 18:56:47 +00:00

..

schema

Preserve retained assistant revisions across rollout replay (#60839)

2026-11-11 18:56:47 +00:00

scripts

Generate Python SDK types from repository app-server schemas (#44032)

2026-09-09 03:27:31 +00:00

src

Hand off approved plans through attachments in fresh sessions (#60763)

2026-11-11 09:01:04 +00:00

BUILD.bazel

Use a dedicated binary for Bazel schema generation (#58083)

2026-10-29 13:37:06 +00:00

Cargo.toml

Route response item IDs through a shared generator (#59312)

2026-11-04 04:02:00 +00:00

schema_generator.rs

Use a dedicated binary for Bazel schema generation (#58083)

2026-10-29 13:37:06 +00:00