Advance WP-0005 T01/T10: Gitea inventory and hub drift cleared
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 35s

Record partial Gitea org inventory, 40-repo migration gap, and patch
ops-warden hub remote_url so all Forgejo-hosted registrations align.
This commit is contained in:
tegwick 2026-07-08 00:03:48 +02:00
parent 1da9c3269b
commit 826fd93603
2 changed files with 101 additions and 12 deletions

View file

@ -234,6 +234,95 @@ Remaining T01 gaps: authenticated Gitea admin inventory (users, teams, deploy
keys, tokens, webhooks, LFS, attachments) and classification of the ~36 Gitea
repos not yet mirrored to Forgejo.
## Addendum (2026-07-07) — refresh and Forgejo admin snapshot
### Forgejo org (14 repos)
Public API `GET /api/v1/orgs/coulomb/repos` on `forgejo.coulomb.social`:
| Repo | Tier | Notes |
| --- | ---: | --- |
| `forgejo-actions-probe` | 0 | Disposable runner/OCI probe |
| `glas-harness` | 1 | Git+SSH+CI pilot |
| `key-cape` | 2 | Image CI + `crictl pull` on railiance01 |
| `railiance-enablement` | 2.5 | S4 workflow templates |
| `railiance-infra` | 2.5 | Stack promotion |
| `railiance-apps` | 2.5 | Stack promotion |
| `railiance-platform` | 2.5 | Stack promotion |
| `railiance-cluster` | 2.5 | Stack promotion |
| `state-hub` | 3 | Primary hub cutover 2026-07-06 (`CUST-WP-0054-T05`) |
| `issue-core` | 3 | Production service repo on Forgejo |
| `activity-core` | 3 | Production coordination repo on Forgejo |
| `hub-core` | 3 | On Forgejo; hub `remote_url` may still reference Gitea |
| `core-hub` | 3 | On Forgejo; hub `remote_url` may still reference Gitea |
| `ops-warden` | 3 | Tier-3 promotion 2026-07-07; hub `remote_url` still Gitea |
Gitea public org count unchanged at **50** repos (2026-07-07).
### State Hub `remote_url` cross-check (2026-07-07)
| Category | Count | Slugs |
| --- | ---: | --- |
| Forgejo remotes | 5 | `activity-core`, `core-hub`, `hub-core`, `issue-core`, `state-hub` |
| Gitea remotes | 58 | (majority of registered repos) |
| No remote URL | 12 | includes `railiance-bootstrap` alias |
**Hub drift** — on Forgejo but State Hub still points at Gitea:
`key-cape`, `ops-warden`, `railiance-apps`, `railiance-cluster`,
`railiance-enablement`, `railiance-infra`, `railiance-platform`
Update `remote_url` during tier-3 promotion (T10/T11), not before backup gate.
### Forgejo admin inventory (authenticated API)
Captured with operator Forgejo token (not secret-bearing values):
| Item | Count / state |
| --- | --- |
| Users | 2: `forgejo_admin` (admin), `tegwick` (admin) |
| Org teams | 1: `Owners` |
| Org webhooks | 0 |
| Operator SSH keys (`tegwick`) | 1 |
| Sample repo (`state-hub`) deploy keys | 0 |
| Sample repo (`state-hub`) webhooks | 0 |
| LFS | Disabled on Forgejo (dump logs: "LFS not enabled") |
### Gitea inventory (authenticated partial, 2026-07-08)
Workstation token (`~/.railiance_gitea.conf`) has org/repo scopes but **not**
`read:admin` / `read:user` — site-wide user list and SSH key inventory blocked.
| Item | Count / state |
| --- | --- |
| Org repos | 50 |
| Org members | 2: `tegwick`, `bubble-reader` |
| Org teams | 2: `Owners`, `Readers` |
| Org webhooks | 0 |
| Sample deploy keys (`state-hub`, `issue-core`, `ops-warden`, `llm-connect`) | 0 each |
| Sample repo webhooks (same set) | 0 each |
| LFS | Not surveyed repo-by-repo; Forgejo side disabled |
**Gap:** mint Gitea PAT with `read:admin` for full user/token/deploy-key sweep
before T11 wave for remaining ~40 repos.
### Migration gap (2026-07-08)
| Metric | Value |
| --- | ---: |
| Gitea `coulomb` repos | 50 |
| Forgejo `coulomb` repos | 16 |
| On Gitea only (not mirrored to Forgejo) | 40 |
Examples not yet on Forgejo: `llm-connect`, `the-custodian`, `flex-auth`,
`ops-bridge`, `markitect-main`, `inter-hub`, `ihp-railiance-probe`, …
### State Hub `remote_url` (2026-07-08)
All Forgejo-hosted registered repos now point at `forgejo-remote` (12 hub
remotes including tier-2.5 stack, tier-3 services, `ops-warden`). Remaining
52 registered repos still use `gitea-remote`.
## Addendum (2026-07-04) — migration ladder and new repos
`RAIL-HO-WP-0005` now uses a **staged per-repo ladder** instead of an isolated