Reconcile completed performance and remediation roadmaps

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Computational Efficiency Implementation Plan
 
-**Status:** Stages 1–11 complete.
+**Status:** Stages 1–11 complete; [review remediation](remediation.md) complete.
 
 ## Purpose And Baseline
 

docs/roadmap/performance.md

@@ -1,6 +1,9 @@
 # Computational Efficiency Roadmap
 
-**Status:** Ready for implementation; implementation pending.
+**Status:** All five target components implemented. The
+[implementation record](implementation.md) owns completed stages and performance
+results; the [remediation record](remediation.md) owns review findings and their
+completion status.
 
 ## Objective And Ownership
 
@@ -35,7 +38,8 @@ on one machine; overall release gains depend on consumer workloads. The probes
 were temporary and left the repository unchanged.
 
 Static review also identified repeated artifact hashing and unconditional Go
-output copying. Their workload impact remains to be measured.
+output copying. The [implementation record](implementation.md) contains their
+baseline and completed-implementation measurements.
 
 ## Desired Target State
 

docs/roadmap/remediation.md

@@ -1,6 +1,6 @@
 # Performance Implementation Remediation
 
-**Status:** Remediation in progress; R1–R3 complete.
+**Status:** Complete; R1–R4 addressed.
 
 **Review baseline:** df064bd, reviewed on 2026-10-09 against the
 [performance target](performance.md) and
@@ -152,6 +152,21 @@ record, consistent with their documentation ownership.
 **Validation:** Check status and navigation across the three roadmap documents
 against the actual implementation and remediation outcomes.
 
+**Completion:** Complete. The feature roadmap identifies all five implemented
+components and links to their implementation results and review remediation.
+The implementation record links to completed remediation. Status, ownership,
+and local navigation across all three documents were checked against the code
+and completed R1–R3 work.
+
+## Remediation Validation
+
+- The full offline Go test suite passed after the production fixes.
+- Compiled public API and dependency checks passed.
+- Race tests passed for validation, Git, and process packages.
+- The output benchmarks passed three repetitions, including exact capture and
+  forwarding checks for both chunking patterns.
+- Changed documentation links, fragments, and whitespace checks passed.
+
 ## Review Validation
 
 - The full offline Go test suite passed; some unchanged packages used cached