jif 6a828ca26f Read approval policy from the current turn configuration (#36912) ...

## Why

Thread settings can update the approval policy after a turn context is created.
Keeping a separate copy on `TurnContext` could leave tool approval checks using
the previous policy.

## What changed

- Remove the duplicated approval-policy field from `TurnContext`.
- Resolve the policy through the turn's current configuration everywhere it is
  needed, including tool execution, Guardian routing, MCP handling, and
  permission requests.

## Testing

- Update the shell escalation test to apply a thread-level policy override and
  verify that the next turn rejects an escalation using the updated policy.

GitOrigin-RevId: e5966ba08f179d53fd76871ad904762958c0f5ea

2026-08-04 15:32:31 +00:00

..

common

Negotiate MCP extensions per app-server session (#36910)

2026-08-04 15:23:43 +00:00

remote_env_windows

Scope runtime workspace roots to execution environments (#32952)

2026-07-14 04:41:08 +00:00

suite

Read approval policy from the current turn configuration (#36912)

2026-08-04 15:32:31 +00:00

all.rs

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

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

responses_headers.rs

Allow custom providers to opt into standalone web search (#34846)

2026-07-23 00:02:15 +00:00