## Why
Managed approval requirements can change while an MCP runtime is still in use.
Later turns need to honor those changes without restarting MCP, while in-flight
MCP actions need to retain the mandatory review requirements of their issuing
turn.
## What changed
- Add `CodexThread::refresh_guardian_policy` to apply managed policy updates to
an existing thread. MCP configuration refreshes preserve the active Guardian
policy, including when a policy update lands while MCP configuration is loading.
- Resolve MCP tool and elicitation reviewers against the issuing turn's policy.
Live requirements can still require Guardian review, and a live policy change
cannot waive mandatory review captured by the turn.
## Testing
Extend coverage for overlapping Guardian and MCP refreshes and for an existing
MCP runtime that must prompt the user on the next turn after a policy update
allows only the `user` reviewer.
GitOrigin-RevId: 5a1649f917313f6fb152a206bc89986fe6345481