jif bf4ca52b61 Restore saved thread permissions during configuration loading (#53419) ...

## Why

Restoring unnamed thread permissions after configuration loading leaves network proxy initialization and permission validation using the configured default. A saved read-only thread should also resume when that default is incompatible with current managed requirements.

## What changed

Apply eligible saved permission profiles during configuration loading, before network preparation and final validation. Keep explicit permission overrides and managed requirements authoritative, preserve managed deny-read restrictions, and reject saved external enforcement or materialized filesystem grants. Include the saved profile in the app-server's prepared resume configuration state.

## Testing

Add regression coverage for resuming saved read-only permissions with an incompatible full-access default and for retaining managed, remembered, and newly approved network domains in the restored profile's proxy allowlist.

GitOrigin-RevId: 73e32b0a31ac678fd3f60a8ccf8fa9df627f16c3

2026-10-12 16:09:41 +00:00

..

src

Restore saved thread permissions during configuration loading (#53419)

2026-10-12 16:09:41 +00:00

tests

Remove the patched zsh shell execution backend (#52160)

2026-10-08 16:19:09 +00:00

BUILD.bazel

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

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

Cargo.toml

Preserve executor path conventions in permission summaries (#45852)

2026-09-16 03:40:53 +00:00