Record the coordinated suite upgrade in progress

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implementation Plan 0022: Coordinated Suite Upgrade
 
-Status: blocked — reviewed role publication requires Gitea Git authentication
+Status: in_progress
 
 Target executor: GPT-5.6-Terra
 
@@ -47,6 +47,8 @@ state, and policy. No operational deployment or tagged release is included.
 
 ## Stage 1: Make Reviewed Standalone Dependencies Public
 
+Completion: complete (2026-09-29).
+
 ### Required Policy Review
 
 Read `AGENTS.md`, `docs/orientation.md`, `docs/conventions.md`, and
@@ -384,9 +386,14 @@ reviewed revisions were present locally; clean worktrees and expected Gitea
 origins were confirmed. After fetching, each `origin/main` was three reviewed
 feature commits behind the selected revision and could fast-forward. The first
 normal push, for Scriptorium, failed because HTTPS Git could not read a
-username. No role revision was published, no downstream stage was started, and
-no stage is marked complete. Resume with authenticated access to the existing
-Gitea origins, then re-fetch and recheck outgoing history before pushing.
+username. At that time no role revision was published and no downstream stage
+had started.
+
+- Stage 1 resumed on 2026-09-29: authenticated pushes of the exact reviewed
+  Scriptorium `b174c8c`, Audita `c3dd59f`, Notarius `6aef48b`, and Narratio
+  `3c0700b` revisions to their existing Gitea `origin/main` branches succeeded.
+  A fresh fetch and ancestor check verified all four public references. No
+  standalone code or dependency pin changed in this stage.
 
 ## Open Questions