Interrupted work needs an honest state and a recoverable path.
A long-running Review can lose access to an external service, exceed an execution limit, or be interrupted. None of those events means that the uncompleted tests passed.
Preserve what happened
The intended workflow records durable progress and evidence as work completes. A failure should leave a clear account of completed work, unfinished areas, and whether recovery is possible.
Keep recovery bounded
A retry needs limits too. Repeating expensive work without tracking what has already completed can waste both time and credits. VibeCheck’s approved approach does not charge Builders for lost work and recovery caused by its own faults.
Controlled local recovery flows have been exercised. That evidence is a development milestone, not proof that every external service or customer application is supported.