Bash has no default timeout, so any command running past the 900 s system
cap ended the whole trajectory (81 of 590 finished rollouts). Give bash a
native timeout one minute before the cap; only that command fails and the
agent continues. The persisted tool call keeps the model's own arguments.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Historical r20260929-04/05/06 data: a cap of 3 would have lost 19 of 142
PASS trajectories (13%); a cap of 5 loses 2 (1.4%). Prompt states the same
number; agent/VERSION 13 -> 14.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Compile attempts are now the primary per-trajectory budget: they map to
the real compute cost, unlike turns or tokens, and make the stop reason
obvious. stagerun refuses a 4th 05-compile with COMPILE_BUDGET_EXHAUSTED
before inline calibration or slot acquisition.
- Counted from the stages ledger (05-compile rows that got a slot), so
resume/recovery cannot reset it; a compile that timed out in the queue
is free; recompiles after an accuracy miss count.
- Board/eval/review of the last artifact still run after the cap.
- Turn/token/wall budgets, per-phase deadlines, cleanup and API quota
protection are unchanged as backstops.
- e2e prompt drops "no retry limit"; SYSTEM.md names compiles as the
primary budget; agent/VERSION 12 -> 13.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pi requests could hit Node fetch's independent five-minute header deadline,
and queued requests could outlive their local client or terminal rollout.
Set header/body deadlines only for the loopback broker origin, cancel scopes
when clients disconnect or executions terminate, and retain uncertain upstream
reservations instead of retrying after cancellation. Resumable pauses remain open.
Validation: real Pi SDK accepted a response delayed 310 seconds (314.139 s test);
quota, Pi session, acceptance, cancellation, and lifecycle regression coverage.