Record Gitea publication blocker

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implementation Plan 0022: Coordinated Suite Upgrade
 
-Status: ready
+Status: blocked — reviewed role publication requires Gitea Git authentication
 
 Target executor: GPT-5.6-Terra
 
@@ -379,7 +379,14 @@ mark F0022 done, begin another feature, or push unrelated workspace history.
 
 ## Progress Notes
 
-Plan approved; implementation has not started.
+Plan approved. Stage 1 publication is blocked. On 2026-09-29, all four exact
+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.
 
 ## Open Questions