Commit module changes only after successful execution
This commit is contained in:
@@ -40,9 +40,14 @@ explicit `not_started`/`interrupted`/`completed` work units, compact model
|
||||
operation outcomes, and per-module results. Candidate payloads are retained
|
||||
in the returned output only when debug capture is requested. A work unit can
|
||||
complete with model errors and applied corrections. Recoverable model failures
|
||||
never trigger shared cancellation. Fatal setup, internal, application, or
|
||||
parent-cancellation errors cancel peers, join workers, and preserve earlier
|
||||
committed module text for partial reports; no completed transcript is published.
|
||||
never trigger shared cancellation. Fatal failures and parent cancellation stop
|
||||
further dispatch and join active workers. The initiating error carries its
|
||||
processing phase and available origin. Work-unit evidence preserves each peer's
|
||||
interruption or error. Usable proposal results from later sections are indexed
|
||||
in order after joining, even when the runner could not validate them. The
|
||||
working transcript advances only at the module's successful commit boundary.
|
||||
Earlier committed text remains available to an interrupted run, and transcript
|
||||
delivery requires successful processing.
|
||||
|
||||
Required transcript/report write failures are fatal. Optional debug writes
|
||||
report safely to stderr without changing decisions or exit status. See
|
||||
|
||||
Reference in New Issue
Block a user