sayan-oai d75c85f651 Separate thread settings from environment configuration (#39597) ...

## Why

Environment-owned permission profiles and workspace roots must remain effective
without being persisted or restored as thread-owned settings.

## What changed

- Keep thread settings snapshots and restore data separate from the effective
  configuration supplied by the primary environment.
- Use resolved environment permissions, active profiles, workspace roots, and
  network policy when building turn context and session events.
- Preserve environment selections when agents are evicted, resumed, or spawned,
  and validate owner configuration when it becomes ready.
- Start memory initialization only after the primary environment is configured.

## Testing

- Extend remote-environment and multi-agent tests to cover settings persistence,
  owner permission profiles, workspace roots, spawning, eviction, and resume.

GitOrigin-RevId: d82f126981cd0190233020bbdd61d96c70558868

2026-08-20 05:29:12 +00:00

..

common

Read plugin authentication state from AuthManager (#39087)

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

remote_env_windows

Carry environment config in turn selections (#38521)

2026-08-14 07:52:38 +00:00

suite

Separate thread settings from environment configuration (#39597)

2026-08-20 05:29:12 +00:00

all.rs

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

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

responses_headers.rs

Include sandbox mode in response metadata (#37507)

2026-08-07 22:41:20 +00:00