jackz d04b0561d3 Preserve account network policy for ChatGPT backend requests (#47703) ...

## Why

ChatGPT backend requests could bypass the configured network policy by using a default HTTP client. Requests using captured credentials must also retain the corresponding account policy so revocation continues to block them.

## What changed

- Use the configured HTTP client factory for ChatGPT GET and POST requests, enforcing managed network policy while retaining cookies.
- Capture authentication and network policy together for app reads and plugin reads and installs, preserving that policy across the post-install configuration reload.
- Bind GET requests to the current account policy before loading credentials.

## Testing

Add regression tests for revoked account policies, blocked connector destinations, and network policy enforcement after configuration reload with a cached app client.

GitOrigin-RevId: 5298842eec9664af49df70e89624653d1452fb33

2026-09-24 00:50:02 +00:00

..

common

Persist thread creator identity in rollouts and SQLite (#47113)

2026-09-21 21:22:01 +00:00

suite

Preserve account network policy for ChatGPT backend requests (#47703)

2026-09-24 00:50:02 +00:00

all.rs

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

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