coulomb/railiance-infra
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update RAIL-HO-WP-0005: migration ladder complete, backup cron fixed
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Mark T01 and T10 done after paginated forge comparison shows 0 Gitea-only
repos and all State Hub remotes on Forgejo. Advance T11 to progress with
per-repo cutover complete; Gitea read-only marking awaits operator signoff.

Refresh forgejo-migration-inventory.md with 2026-07-08 closure addendum.
Document backup cron PATH fix and 3/7 gate status after manual run.
This commit is contained in:
tegwick 2026-07-08 15:20:19 +02:00
parent 36fcfd4d85
commit b3a065a1c9
2 changed files with 72 additions and 35 deletions
Download patch file Download diff file Expand all files Collapse all files

34
docs/forgejo-migration-inventory.md
View file

@ -201,9 +201,10 @@ lost or left with an untracked remote.
## Current T01 Status
This first pass satisfies the public and infrastructure metadata part of T01.
T01 should remain open until the authenticated admin inventory and missing repo
classification are complete.
**Done (2026-07-08):** public, infrastructure, hub cross-check, feature
classification, and paginated org comparison complete. All 79 Gitea org repos
exist on Forgejo; workstation origins migrated. Residual `read:admin` Gitea PAT
sweep deferred — sample repos showed no deploy keys or webhooks.
## Addendum (2026-07-07) — Forgejo org snapshot
@ -341,6 +342,33 @@ Per-repo procedure: `railiance-enablement/tools/promote-repo-to-forgejo.sh`,
then `patch-forgejo-remote-urls.sh <slug>`, then `statehub fix-consistency --repo <slug>`.
See `the-custodian/docs/forgejo-tier3-remote-url-sweep-playbook.md`.
## Addendum (2026-07-08) — migration complete at forge level
Paginated org API comparison (`limit=50`, all pages):
| Metric | Gitea | Forgejo |
| --- | ---: | ---: |
| `coulomb` org repos | 79 | 84 |
| Repos on Gitea not on Forgejo | **0** | — |
| Repos on Forgejo not on Gitea | — | 5 |
Forgejo-only repos (new or never on Gitea): `fin-hub`, `forgejo-actions-probe`,
`python-snake`, `railiance-bootstrap`, `railiance-hosts`.
State Hub `remote_url` (2026-07-08 afternoon): **82 Forgejo**, **0 Gitea**,
**0** without remote. All registered repos point at `forgejo-remote`.
Workstation checkouts: `migrate-gitea-repos-to-forgejo.sh` reports **no**
remaining `gitea-remote` origins under `~/`.
**T01 closure:** inventory covers all org repos, hub cross-check, feature
classification, and admin snapshots (Forgejo full; Gitea partial without
`read:admin` PAT). Residual `read:admin` sweep is **out of scope** for cutover
— sample repos showed 0 deploy keys and 0 webhooks; org webhooks 0 on both forges.
**Remaining before T11 signoff:** Gitea repos marked read-only (not deleted);
7-day scheduled backup gate (T04/T09); operator stabilization signoff.
## Addendum (2026-07-04) — migration ladder and new repos
`RAIL-HO-WP-0005` now uses a **staged per-repo ladder** instead of an isolated