jif feadd9441e Preserve enterprise MCP authorization across runtime refreshes (#55696) ...

## Why

Configuration reloads must cancel stale enterprise MCP startups while preserving access for running threads that still pass validation. Replacing a runtime during `thread/revert` must also leave the replacement able to use enterprise tools.

## What changed

- Separate pending startup cancellation from published thread lifetimes, with independent startup state for forks and replacement runtimes.
- Retain eligible enterprise MCP connections across refreshes and explicit reconnects while applying updated tool restrictions and approvals. Do not create replacement enterprise connections after initial startup.
- Revoke enterprise authorization when a thread is removed, drain requests when access is disabled, and revoke a connection's authority when token renewal requires authentication.

## Testing

Extend regression coverage to verify enterprise tool calls survive `thread/revert`, inherited fork configurations are cancelled after a reload, and enterprise calls fail after logout while ordinary MCP calls remain available.

GitOrigin-RevId: 2d634be3011854b57f73c741bd1ec6b5aed94ee5

2026-10-20 23:03:56 +00:00

..

v2

Preserve enterprise MCP authorization across runtime refreshes (#55696)

2026-10-20 23:03:56 +00:00

auth.rs

Expose selected workspace routing in app-server account reads (#45529)

2026-09-14 22:31:32 +00:00

conversation_summary.rs

Apply shared network policy throughout embedded Codex startup (#47411)

2026-09-23 00:49:19 +00:00

fuzzy_file_search.rs

Simplify app-server integration test setup (#34786)

2026-07-22 16:30:12 +00:00

logging.rs

Keep submission logs useful without exposing payloads (#51467)

2026-10-06 19:34:02 +00:00

mod.rs

app-server: structure and test JSON shutdown logs (#30314)

2026-06-26 18:19:56 -07:00

strict_config.rs

Expose effective login methods in config requirements (#45495)

2026-09-14 19:11:29 +00:00