Scott Werner 04309977e5 Commit checkpoint failures through required finalization ... A failed checkpoint cancels the run, so Petri recorded it as cancelled and the worker overrode its own outcome in memory. Runs that checkpoint now declare required finalization, and finalize_run rejects with checkpoint_failed before publishing. The projection and the engine outcome report a cancelled finish carrying that failure as a workflow failure with the checkpoint's message, and the in-memory override is gone. A run whose checkpoint failed is never published. Retry a host failure that storage rejects with a short backoff, so a brief storage fault does not leave the run active and holding its scheduler slot. A failure that never commits still leaves the run's status alone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-09 11:00:01 -04:00
..
cmd	Commit checkpoint failures through required finalization	2026-10-09 11:00:01 -04:00
scenario	Bind Petri scenario servers to OS-assigned ports	2026-10-08 10:33:38 -04:00
support	Build the run's display graph from Petri's admission	2026-09-19 11:41:58 -04:00
workflow	fix: address review of the in-process sandbox providers	2026-09-25 12:31:37 -04:00
main.rs	refactor: organize crates into three layers	2026-07-23 17:59:34 -04:00