Ruslan Nigmatullin 340a18ed7c Preserve model-facing ID allocations in saved history (#60771) ...

## Why

Restoring model-facing ID sequences requires allocation ordinals alongside the rendered IDs. Responses API payloads still require string IDs.

## What changed

- Add allocation metadata to `ResponseItemId` while keeping equality, hashing, and ordering based on the rendered ID.
- Preserve optional `id_allocation` metadata in rollout items, inter-agent messages, compaction replacement history, and Guardian checkpoints. Continue accepting legacy string IDs.
- Support structured context-window allocations alongside UUIDv7 strings, validate the `window` salt on restoration, and keep request metadata IDs as strings.

## Testing

Add tests for allocation round trips, legacy ID compatibility, string-only raw response item IDs, and context-window allocation validation.

GitOrigin-RevId: ce1fd964bde9a4e7c527432be99aea87ada30169

2026-11-11 09:58:13 +00:00

..

schema

Preserve model-facing ID allocations in saved history (#60771)

2026-11-11 09:58:13 +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