Clear the shared pipeline dependency blocker

docs/roadmap/remediation.md

@@ -19,11 +19,12 @@ documents the interface. No redundant inspection, corrective convergence,
 private state, or unrelated application behavior was introduced. All four
 repository-local integration suites passed independently during review.
 
-Feature 0009 as a whole is not implemented. The active implementation plan and
-workspace status correctly record a publication blocker after Stage 4. The
-pipeline repository remains at pre-feature commit `3e253d7`; Stages 5 through
-8 have not been executed. The following findings therefore describe missing
-target architecture rather than defects in the completed standalone commits.
+Feature 0009 as a whole is not implemented. The pipeline repository remains at
+pre-feature commit `3e253d7`; Stages 5 through 8 have not been executed. The
+publication blocker encountered after Stage 4 has now been cleared: all four
+standalone commits are available from their canonical origins. The following
+findings therefore describe the remaining target architecture rather than
+defects in the completed standalone commits.
 
 ## Finding 1: The Pipeline Does Not Select the Shared Configuration Policy
 
@@ -45,8 +46,8 @@ before the other configuration-bearing dependencies run.
 
 ### Required Remediation
 
-- Publish the four reviewed standalone-role commits so immutable dependency
-  installation can resolve them; do not replace commit pins with branches.
+- Use the four published, immutable standalone-role commits recorded above;
+  do not replace their commit pins with branches.
 - Execute Stage 5 of `docs/roadmap/implementation.md` in full.
 - Add the four suite defaults and argument-spec entries, run Narratio first,
   pass the selected identity and modes through every generic role interface,
@@ -166,3 +167,5 @@ implementation repositories remained clean after testing.
 The pipeline suite was not presented as Feature 0009 validation evidence
 because the pipeline repository contains no Feature 0009 implementation
 commits. Its current test suite exercises the prior Feature 0008 architecture.
+After review, each standalone commit was pushed to its canonical `origin/main`
+branch and the local and remote-tracking revisions were confirmed identical.