felixxia-oai 92bc601ad6 Reuse unchanged history snapshots when resuming threads (#49600) ...

## Why

Resuming a thread rereads persisted history even when a preloaded snapshot is unchanged. Reusing that snapshot must still account for writes committed before writer ownership is acquired.

## What changed

- Carry optional, non-serialized revisions from stored history and model context through thread and agent resume paths.
- Validate the revision under writer ownership and reuse the shared snapshot when it matches. Reload stored history when the revision is missing or changed, while preserving explicit history overrides.
- Resolve the selected rollout before loading context, validate compressed snapshots before materialization, and enforce archived-thread restrictions on canonical paths.

## Testing

Extend coverage for snapshot reuse and late-write refresh in legacy and paginated histories, compressed rollout reuse, archived rollout symlinks, and cold child restoration that includes edits made after preloading history.

GitOrigin-RevId: e1fd7aee6ef2b30f41951e6b7e6b01c3e1420cab

2026-09-30 11:59:13 +00:00

..

src

Reuse unchanged history snapshots when resuming threads (#49600)

2026-09-30 11:59:13 +00:00

BUILD.bazel

Support detect and import MCP, Subagents, hooks, commands from external (#19949)

2026-04-29 00:45:24 +00:00

Cargo.toml

Read plugin authentication state from AuthManager (#39087)

2026-08-17 22:26:27 +00:00