Map processing outcomes to versioned YAML reports

docs/roadmap/implementation.md

@@ -619,6 +619,16 @@ filesystem requirements for disabled features.
 
 ## Stage 8 — Map Outcomes to Versioned YAML Reports
 
+**Completed 2026-09-24.** The old ordinary JSON report DTO was replaced with
+versioned errors/recoveries YAML DTOs and one processing snapshot. Mapping derives
+nullable summary counts, grouped recoverable work-unit failures, run failures,
+combined recovery reasons, and deterministic semantic order without raw causes or
+transcript payloads. Tests cover partial and empty work, multiple failures,
+initialization unknowns, ordered run errors, safe redaction, and YAML scalar
+types. `go test ./internal/core/reporting ./internal/framework/processreport`
+and `git diff --check` passed. CLI and diagnostics consumers of the removed JSON
+schema remain to be reconnected in later stages.
+
 **Work:** Replace ordinary report DTOs and assembly in `core/reporting` and
 `framework/processreport` with F. Map actual runner state once into an immutable
 report snapshot consumed by all presentations. Preserve debug-specific ledger and