Refresh reports when delivery failures accumulate
This commit is contained in:
@@ -29,10 +29,10 @@ files and supplies those source paths to CLI;
|
||||
no second filename-based discovery rule is used.
|
||||
CLI composes it after configuration, transcript acquisition, and preflight
|
||||
readiness and before dispatching model work. It does not create ordinary report parents.
|
||||
Final report rendering uses the delivery and cleanup errors already observed.
|
||||
If a report write first fails, the remaining writes use the failed bundle and
|
||||
one pass attempts to update the reports still missing failed evidence. A
|
||||
published transcript remains available after a later report failure.
|
||||
Final report rendering includes delivery and cleanup errors observed so far.
|
||||
When another failure becomes known, later writes use updated failed reports.
|
||||
One best-effort pass refreshes earlier reports with stale evidence. A published
|
||||
transcript remains available after a later report failure.
|
||||
|
||||
Debug is independent. The shared `--debug` flag enables a unique retained child
|
||||
under `diagnostics.work_dir`. The CLI creates one interaction sink rooted in
|
||||
|
||||
Reference in New Issue
Block a user