Avoid paginated resume requests for verified legacy rollouts (#38604)

## Why

Resuming a known legacy rollout with `excludeTurns` first requires the TUI to
retry after the app server rejects paginated history loading.

## What changed

- Carry the history mode reported by the session picker into the resume flow.
- For embedded app-server sessions, resume a legacy rollout with its turns when
  the rollout is still legacy and background migration cannot race the check.
- Keep requesting paginated history when the picker metadata may be stale,
  migration is enabled or active, or the app server is remote.

## Testing

Added coverage for picker server replacement, background migration, maintenance
lock contention, stale history metadata, and paginated resume requests.

GitOrigin-RevId: 2300d1ad93a817eeeeb8f8ed60b073400ddf7106
This commit is contained in:
Charlie Marsh authored and copyberry committed 2026-08-14 16:33:28 +00:00
1 parent 588ee89324
commit 1bb6384c19
13 files changed
+455 -90

No files matched your search

+3
View File
@@ -946,6 +946,9 @@ impl App {
(chat_widget, None)
}
SessionSelection::Resume(target_session) => {
if let Some(history_mode) = target_session.history_mode {
app_server.remember_thread_history_mode(target_session.thread_id, history_mode);
}
let model_settings = config_persistence::resume_model_settings_for_overrides(
&config,
&harness_overrides,