jif 5eea8d0dd3 Review terminal input against retained permissions (#41328) ...

## Why

An existing terminal keeps the sandbox, network settings, and grants it had at launch. Later `write_stdin` calls must account for that retained authority, including when permissions change between turns.

## What changed

- Capture each terminal's effective launch permissions and compare them with the current environment before accepting non-empty input.
- Request approval when the terminal bypassed the sandbox, retains additional grants, strict auto-review is active, or its sandbox or network settings differ from the current policy.
- Reject input when current denied-read or environment-owned network restrictions cannot be enforced by the existing terminal, while keeping empty polls and non-TTY interrupts available without review.
- Include the effective sandbox mode and user-visible additional grants in `write_stdin` approval actions without exposing host-owned grant paths.

## Testing

Added unit and end-to-end coverage for retained cross-turn grants, strict auto-review, sandbox and network policy changes, denied reads, Windows sandbox backends, and private grant redaction.

GitOrigin-RevId: e2d71daf9358474c885998786c4928069100711c

2026-08-28 11:38:03 +00:00

..

common

Harden core test fixture startup assertions (#41194)

2026-08-27 19:58:09 +00:00

remote_env_windows

Standardize shell execution on unified exec (#39772)

2026-08-20 18:29:35 +00:00

suite

Review terminal input against retained permissions (#41328)

2026-08-28 11:38:03 +00:00

all.rs

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

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

responses_headers.rs

Sanitize credentials from Git remote metadata (#40713)

2026-08-25 21:34:05 +00:00