Shijie Rao 539a09cb28 Restore permission profiles when resuming threads (#39153) ...

## Why

Cold resumes and forks could lose the thread's active permission profile and
fall back to the current configured default.

## What changed

- Restore the latest persisted approval policy, approvals reviewer, and active
  permission-profile ID when resuming or forking a thread.
- Re-resolve persisted profile IDs through current configuration and
  requirements. Missing or invalid profiles fall back to the configured
  default, while threads without a persisted profile continue to use current
  configuration.
- Keep explicit permission and approval overrides ahead of persisted settings.

## Testing

Added coverage for legacy and paginated histories, settings updates, explicit
overrides, removed or changed profiles, requirement fallbacks, and forks.

GitOrigin-RevId: 2289af2f3206bf131a6ffe0e8447e8d402e76c47

2026-08-18 06:22:04 +00:00

..

src

Restore permission profiles when resuming threads (#39153)

2026-08-18 06:22:04 +00:00

tests

Use paginated history for persistent exec threads (#38774)

2026-08-15 15:24:30 +00:00

BUILD.bazel

[codex] Shard exec Bazel integration test (#19862)

2026-04-27 21:22:53 +00:00

Cargo.toml

Extract persisted history types into a dedicated crate (#37871)

2026-08-10 19:26:52 +00:00