Reconcile ordered pipeline documentation

docs/roadmap/implementation.md

@@ -1,11 +1,19 @@
 # Implementation Plan: Ordered Pipeline Follow-Up
 
+## Status
+
+Completed on 2026-07-22. This document retains the implementation sequence for
+historical context; current contracts are maintained in the canonical CLI,
+configuration, operations, integration, and internal documentation linked from
+the [development guide](../development.md).
+
 ## Purpose
 
-Close the remaining correctness, observability, test, and maintainability gaps
-in the implemented [Ordered Pipeline Steps](ordered-pipeline-steps.md) feature.
-That feature roadmap remains the authority for product intent, policy choices,
-acceptance criteria, and exclusions. This document is the ordered,
+Record the work that closed the correctness, observability, test, and
+maintainability gaps in the implemented
+[Ordered Pipeline Steps](ordered-pipeline-steps.md) feature. That feature
+roadmap remains the authority for product intent, policy choices, acceptance
+criteria, and exclusions. This document preserves the ordered,
 decision-complete implementation sequence for the follow-up work.
 
 ## Background
@@ -18,19 +26,18 @@ output provenance, support `--recompute-step`, and use generated NPC output at
 operation time in the D&D spell and combat consumers. Current documentation and
 maintained examples describe that model.
 
-The remaining work is narrower:
+The completed follow-up addressed these narrower gaps:
 
-- selective recomputation currently treats an unselected predecessor as
-  reusable only when all of its extract, merge, and normalize stage checkpoints
-  are reusable, although the architectural dependency is its accepted
-  normalized artifact;
-- the failed stage decision is not always recorded before a required-predecessor
+- selective recomputation now hydrates an unselected predecessor from its
+  accepted normalized artifact without requiring its extract and merge state;
+- the failed checkpoint decision is recorded before a required-predecessor
   error returns;
-- checkpoint reason codes are inferred from human-readable prose instead of
-  being assigned explicitly;
-- the runner's lane and checkpoint orchestration has become too concentrated in
-  large functions; and
-- the roadmap-required CLI and resumed-producer acceptance coverage is absent.
+- checkpoint reason codes are assigned explicitly rather than inferred from
+  human-readable prose;
+- runner lane and checkpoint orchestration has explicit responsibility seams;
+  and
+- CLI and resumed-producer acceptance coverage exercises the complete recovery
+  contract.
 
 No new product feature is introduced by this plan. Preserve configuration file
 version 3 and checkpoint workspace schema `notarius.workspace.v3`; the fixes do