Refresh reports when delivery failures accumulate
This commit is contained in:
@@ -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)
|
||||
|
||||
Reference in New Issue
Block a user