Charlie Marsh 3047741b63 Preserve acknowledged permissions when resuming and forking threads (#57227) ...

## Why

A running turn can record stale permissions after the thread accepts a settings update. Resuming or forking from that history should preserve the accepted approval and permission settings.

## What changed

- Prefer settings snapshots owned by the source thread over stale turn contexts, including later legacy updates associated with that thread's checkpoint.
- Restore unnamed permission profiles from attributable settings updates while honoring explicit request overrides. Avoid restoring raw permission grants from history without an identifiable owner.
- Share permission restoration logic between resume and fork.

## Testing

Add regression coverage for stale turn contexts, legacy updates across thread ownership boundaries, and unnamed permission restoration on resume and fork.

GitOrigin-RevId: 450bc1688be78c7ec685f6dc56bcc5e5dd2d130a

2026-10-26 20:17:38 +00:00

..

common

Add experimental attached thread forks (#56351)

2026-10-23 04:52:47 +00:00

suite

Preserve acknowledged permissions when resuming and forking threads (#57227)

2026-10-26 20:17:38 +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