Canonicalize registry docs and read-only ops

docs/first-migration-plan.md

@@ -2,6 +2,9 @@
 
 Date: 2026-06-05
 
+Status: Phase 1 is underway. The remote repository exists and is pushed, so the
+earlier Gitea API blocker no longer applies.
+
 This plan starts the extraction of forge ownership from `railiance-apps` into
 `railiance-forge` without changing the live Gitea deployment.
 
@@ -85,7 +88,7 @@ Review gates:
 
 - `railiance-forge` remote exists and is pushed.
 - State Hub workplans are synced in both repos.
-- Operator confirms the Gitea token/remote creation issue is fixed.
+- Operator confirms deploy-capable Gitea ownership should move now.
 - `railiance-apps` has compatibility pointers for old paths.
 - The plan distinguishes current Gitea operation from future Forgejo cutover.
 
@@ -112,19 +115,13 @@ Validation:
 - `railiance-apps` no longer claims forge runtime ownership.
 - App operators can still find registry instructions through pointers.
 
-## Open Blocker
+## Remote Status
 
-The local `tea` login named `coulomb` is configured but currently fails with
-`invalid username, password or token`. This blocks creation of the remote
-`coulomb/railiance-forge` repository through the Gitea API.
-
-Until refreshed credentials are available:
-
-- keep `railiance-forge` local and State Hub-registered;
-- do not add an `origin` remote that points to a missing repository;
-- avoid claiming remote publication is complete.
+`railiance-forge` now has `origin` configured as
+`gitea-remote:coulomb/railiance-forge.git` and the local `main` branch is
+aligned with `origin/main`.
 
 ## Next Recommended Action
 
-Proceed with Phase 1 documentation canonicalization after the operator confirms
-that compatibility pointers in `railiance-apps` are acceptable.
+Complete Phase 1 documentation canonicalization and Phase 2 read-only operator
+targets, then review the deploy-capable Gitea file move separately.