Refresh reports when delivery failures accumulate

This commit is contained in:
2026-11-17 03:52:48 +00:00
parent f99fd993b4
commit 0c2a2164ec
4 changed files with 116 additions and 35 deletions

View File

@@ -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

View File

@@ -2,7 +2,7 @@
**Reviewed revision:** `e8c0708`
**Status:** Fourteen open findings from review of the 20
**Status:** Findings and remediation progress from review of the 20
[implementation stages](implementation.md) against the
[target roadmap](reliability-and-maintainability.md), including follow-up
audits of component interactions and algorithmic costs.
@@ -48,6 +48,11 @@ normalization, chunking, preflight, validators, the runner, and reports.
### R1 — Include Later Delivery Failures in Writable Reports (P2)
**Complete.** Later report writes include newly observed delivery failures.
One best-effort pass updates earlier reports with stale evidence. Diagnostics
tests cover both initially failed runs and failures that arise during
publication of a completed run.
**Affected plan:** Stage 4, item 3, and Stage 17, item 1.
**Evidence:** [Report publication](../../internal/core/diagnostics/output_session.go#L311)