Escalate completion budgets on length-truncation instead of scoring the death

[MaxGhenis]

Closes #150 — a completion-cap exhaustion is an environment error, not a serving fact (the onboarding gauntlet's principle, applied at run time). Gates the #139 v2 rerun.

• finish_reason=length with missing cells → retry with the budget doubled, capped at a per-model ceiling (128k default; model-card/provider maxima where lower, e.g. Gemini 3.6's documented 64k output limit). next_completion_budget returns None at the ceiling → remaining cells become ordinary misses with the distinct failure source budget_exhausted_at_ceiling (vs format/parse sources), so the Explanation contract is unenforced — set the v2 scoring policy #145 parse-failure column can bucket them separately.
• Finish-reason normalization across transports: chat + Responses API (incomplete-response mapping); filters/refusals are not escalated.
• Partial payloads from a truncated response keep their valid cells; escalated retries go through the Repair rounds resample and overwrite valid answers #143 fill-only merge and only re-ask remaining variables.
• Escalations logged (model, scenario, from→to budget) and counted in spend records, run manifest, and supervisor state.

Verification (independent of the implementing agent): full non-slow suite rerun locally — 569 passed, 5 skipped (+35 new tests); zero test deletions; ruff clean; core hunks reviewed (escalation loop, ceiling function, finish-reason normalization). Published v1 artifacts unaffected.

Authored by GPT-5.6 Sol via codex (ultra), reviewed and independently re-tested by Claude. Motivated by review feedback on the v2 contract.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
policybench-site	Ready	Preview	Aug 11, 2026 12:03pm