Release session export gates whose recovery is exhausted or overdue

An exhausted export recovery job left its run parked forever in the
export wait, reserving the workspace and refusing later scheduled runs
(runs 221/226: OpenCode sessions above the 8 MiB export bound are
always truncated, so every retry stays partial).

A gate is now releasable when its job is exhausted: the visit keeps its
partial/unavailable evidence and diagnostic (still repairable), the run
continues to its next stage or terminal, and the workspace is freed.
Gates older than 15 minutes with a pending, lease-expired or missing job
are exhausted by a bounded wait. The worker reconciles on its first
tick after startup and every 30 seconds, so existing wedged runs recover
after a restart. Truncation diagnostics now name the size bound.
This commit is contained in:
2026-11-01 17:24:56 +00:00
parent c742bb17f0
commit d35739cb49
8 changed files with 405 additions and 46 deletions
+7
View File
@@ -1015,3 +1015,10 @@ run settles: up to three durable runtime attempts, with backoff and restart-safe
leases. `inspect RUN_ID --json` includes each visit's `session_export_recovery`
status/attempt count/diagnostic and preserved `session_export_repairs`. Exhausted
automatic recovery remains a warning; manual versioned repair is still available.
A run parked on an export handoff never waits beyond that: once its job is
exhausted (or the wait exceeds 15 minutes with the job pending or past its
lease), the visit keeps its partial/unavailable evidence and diagnostic, the run
continues to its next stage or terminal, and its workspace is released. The
server applies this at startup and every 30 seconds, so a run parked before an
upgrade recovers after the next restart. A native session larger than the 8 MiB
export bound (typically inline image payloads read by a tool) is always partial.
+2 -1
View File
@@ -47,7 +47,8 @@ only**, not credentials, projects, sessions, drafts, or history.
Model stages settle their exact native session and verify its export before
handoff. An export failure retains computed output and waits for export-only
recovery. **Retry export only** reads that session again; it does not rerun the
recovery; when that bounded recovery is exhausted the run continues with the
incomplete export recorded as a warning. **Retry export only** reads that session again; it does not rerun the
stage. A genuinely missing historical conversation cannot be reconstructed by
inventing messages.