Charlie Marsh ffda54f5b8 Reuse current model context across paginated resume config loading (#56224) ...

## Why

Resuming a paginated thread rechecks stored history after loading configuration. Unchanged model context can be reused instead of loading it again.

## What changed

Retain the prepared model context across configuration loading and reuse it when the thread ID, rollout path, and history revision still match. Add `ThreadStore::is_model_context_current` to validate revisions, with a fresh read when validation fails or is unavailable.

## Testing

Add coverage for revision invalidation after history is appended or removed. Extend resume tests to cover paginated history, concurrent metadata and lifecycle changes, workspace-root changes, and preservation of saved user messages in model requests.

GitOrigin-RevId: bad2ca0caddb63523264ac530ffb801db3961f2b

2026-10-22 17:15:06 +00:00

..

common

Recheck account login ownership for enterprise MCP (#55680)

2026-10-20 21:34:24 +00:00

suite

Reuse current model context across paginated resume config loading (#56224)

2026-10-22 17:15:06 +00:00

all.rs

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

prompt_prefix.rs

Add an app-server prompt prefix compatibility test (#51857)

2026-10-07 22:21:33 +00:00