Write terminal debug reports for failed runs

docs/internal/state.md

@@ -43,6 +43,12 @@ boundaries redact sensitive metadata and credential-shaped bytes while allowing
 application-owned trace material. Debug data is never a checkpoint source or
 cache input.
 
+After allocation, one CLI-owned state value accumulates the known report paths,
+pipeline outcome counts, and validation status. A single guarded terminalization
+operation writes the success report, or makes one attempt each to write the
+failure report and error log. Terminal persistence failures are reported
+separately and never replace the command's primary error.
+
 ## Tests To Inspect
 
 - `internal/cli/state_surfaces_test.go`: debug allocation and configuration

docs/operations.md

@@ -140,16 +140,20 @@ supported Unix systems.
 Notarius never automatically deletes a requested bundle. If allocation
 succeeds, its path is reported on success and failure. A requested summary or
 trace write failure makes the command fail, preserving whatever bundle data was
-already written for inspection.
+already written for inspection. Every allocated bundle makes one best-effort
+attempt to record a terminal `run-report.json`.
 
 ## Failures And Warnings
 
 Failures before debug allocation are reported on stderr without a bundle.
-Failures after allocation report the bundle path on stderr and write `error.log`
-when that summary write succeeds. An output-write failure leaves the allocated
-bundle in place. A successful run with warnings exits `0`, reports a warning
-count on stderr, and records warnings in durable output and any requested debug
-summary.
+Failures after allocation report the bundle path on stderr and make independent
+attempts to write a failure `run-report.json` and `error.log`. The report retains
+the paths and pipeline outcome fields known at the failure point. If either
+terminal write fails, the original command error remains first on stderr,
+followed by the persistence error and bundle path. An output-write failure
+leaves the allocated bundle in place. A successful run with warnings exits `0`,
+reports a warning count on stderr, and records warnings in durable output and
+any requested debug summary.
 
 ## Cleanup
 

docs/roadmap/implementation.md

@@ -277,7 +277,7 @@ all repository checks pass.
 
 ## Stage 3: Write terminal run reports for failures
 
-**Status:** Not started
+**Status:** Complete
 
 ### Objective