Clear the shared pipeline dependency blocker

docs/roadmap/features/0009-shared-pipeline-filesystem-and-execution.md

@@ -1,6 +1,6 @@
 # Feature 0009: Shared Pipeline Filesystem and Execution
 
-Status: ready
+Status: in_progress
 
 ## Summary
 

docs/roadmap/implementation.md

@@ -844,9 +844,10 @@ The final handoff must:
 
 ## Progress Notes
 
-No implementation stages have begun. Record only concise stage commit hashes
-and blockers here during execution; preserve detailed evidence in the stage
-commits and final handoff.
+Stages 1 through 4 and the dependency-publication checkpoint are complete.
+Resume at Stage 5. Continue recording only concise stage commit hashes and
+blockers here; preserve detailed evidence in the stage commits and final
+handoff.
 
 - [x] Stage 1 complete — `ansible-role-audita` commit `66ebea9`; full
   integration, native validation, and clean repeats passed. No deviations.
@@ -858,9 +859,6 @@ commits and final handoff.
   deviations.
 - [x] Stage 4 complete — `ansible-role-narratio` commit `eeb1105`; full
   integration, native validation, and clean repeats passed. No deviations.
-- Blocked before Stage 5: fresh canonical-origin fetches cannot resolve
-  Audita `66ebea9a47ce82bfdbdc5e2855f3dfaaff8e2a16`, Notarius
-  `e9ae2dc34023e1e8462bf0991de62b97d8c0e0ee`, Scriptorium
-  `8b4c86e48e7d8655e479b26dc510bf01683a0c8f`, or Narratio
-  `eeb1105590e638c1f46b42c98a5dbbce4ddeea86`. Publication is required;
-  implementation does not push.
+- [x] Dependency publication checkpoint complete — the four Stage 1–4 commits
+  are available from their canonical `origin/main` branches at the exact
+  immutable revisions listed above. Stage 5 may begin.

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.