Files
codex/codex-rs
ioanbudea-OAI 6d94d4af10 Isolate Guardian v2 score caches by policy revision (#62083)
## Why

Overlapping turns can use different Guardian policies. Scores and retained classifier conversations must stay with their policy revision, while late actions from older turns must still age or invalidate the current policy's cached approval.

## What changed

- Select and retain a policy-specific conversation backend for each turn, with separate scores, authorization, and classifier history.
- Share action tracking, wrapper lag, JavaScript execution allowances, and classification admission capacity across policy backends.
- Record scoring failures across policies and require the cached score's source action to cover them before reusing an approval. Report missing scores and scoring failures before checking lag.
- Retire all retained policy backends when the thread stops or its backend is replaced, preventing late results from being published.

## Testing

Add regression coverage for separate classifier histories, shared admission capacity, late actions and failures from older turns, and delayed scores that do not cover a recorded failure.

GitOrigin-RevId: 020fa07f9269a28635cbe2cfd40bb5acd90de090
2026-11-17 17:17:02 +00:00
..
…
…
…
…