Complete the test suite review documentation

docs/internal/llm.md

@@ -132,8 +132,8 @@ handling of debug data is defined in [Operations](../operations.md#debug).
 
 ## Tests To Inspect
 
-- `internal/framework/llm/scriptorium_client_test.go` and
-  `scriptorium_api_test.go`: adapter mapping and local HTTP integration.
+- `internal/framework/llm/scriptorium_client_test.go`: adapter mapping and local
+  HTTP integration.
 - `internal/framework/llm/scheduler_test.go` and
   `scheduled_client_test.go`: permits, FIFO behavior, cancellation, and wrapper
   release.

docs/roadmap/implementation.md

@@ -1,12 +1,19 @@
 # Test Suite Policy Review Implementation
 
+## Status
+
+Completed on 2026-07-18 by the commit series ending with `4f96abf`. This
+document is retained as the execution record for the completed test-suite
+policy review; its stages are no longer active implementation instructions.
+
 ## Purpose
 
-This document is the decision-complete execution plan for implementing the
-target revisions in [Test Suite Policy Review](tests.md). Follow the stages in
-order. The feature roadmap owns the review evidence, desired test ownership,
-required dispositions, and target state; this document owns sequencing,
-file-level work, validation, and stop conditions.
+This document records the decision-complete execution plan used to implement
+the target revisions in [Test Suite Policy Review](tests.md). The stages were
+followed in order. The feature roadmap owns the review evidence, desired test
+ownership, required dispositions, and target state; this document records the
+sequencing, file-level work, validation, and stop conditions used during
+implementation.
 
 This is test-suite harmonization, not a production feature change. Do not
 modify production behavior. If a new durable test exposes incorrect production