WP-0005: promote tier-2 tooling repos and refresh hub drift
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s

Promote ops-bridge, open-reuse, and artifact-store to Forgejo (wave-2).
Re-patch all Forgejo-hosted registered hub remotes after drift. Update
workplan and inventory: backup gate 2/7, Forgejo org 20 repos, hub 16/46.
This commit is contained in:
tegwick 2026-07-08 00:29:07 +02:00
parent ef886f66ea
commit eda797bd37
2 changed files with 24 additions and 16 deletions

View file

@ -311,17 +311,19 @@ before T11 wave for remaining ~40 repos.
| Metric | Value |
| --- | ---: |
| Gitea `coulomb` repos | 50 |
| Forgejo `coulomb` repos | 16 |
| On Gitea only (not mirrored to Forgejo) | 40 |
| Forgejo `coulomb` repos | 20 |
| On Gitea only (not mirrored to Forgejo) | ~37 |
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
51 registered repos still use `gitea-remote`.
All Forgejo-hosted **registered** repos now point at `forgejo-remote` (tier-2.5
stack, tier-3 services, `ops-warden`, `ihp-railiance-probe`, `ops-bridge`,
`open-reuse`, `artifact-store`). Unregistered Forgejo repos (`disaster-control`,
`reuse-surface`) have no hub entry. Remaining ~51 registered repos still use
`gitea-remote`.
### Wave 2 promotion queue (T10/T11)
@ -330,8 +332,9 @@ for tier 3):
| Tier | Repo | Notes |
| ---: | --- | --- |
| 1 | `ihp-railiance-probe` | Integration probe; promote before tier-3 wave |
| 2 | `artifact-store`, `ops-bridge`, `open-reuse`, … | Non-production / tooling |
| 1 | `ihp-railiance-probe` | **done** 2026-07-08 |
| 2 | `artifact-store`, `ops-bridge`, `open-reuse` | **done** 2026-07-08 |
| 2 | `repo-scoping`, `guide-board`, `phase-memory`, … | Non-production / tooling (next) |
| 3 | `llm-connect`, `the-custodian`, `user-engine`, `flex-auth`, `vergabe-teilnahme`, `railiance-fabric` | Production-adjacent; gated |
Per-repo procedure: `railiance-enablement/tools/promote-repo-to-forgejo.sh`,

View file

@ -256,8 +256,8 @@ decided (Option A, Nextcloud).** **Automation:** `railiance-platform`
`make forgejo-backup` / `docs/forgejo-backup.md` — daily `forgejo dump` +
`pg_dump` → age → Nextcloud `forgejo/`. **First production backup succeeded
2026-07-07** (~686M dump + 2.1M pg_dump uploaded). Daily cron installed
(02:15 UTC). Remaining: 7-day success gate (1/7), restore drill from Nextcloud
artifact (not `/tmp/forgejo-drill/`).
(02:15 UTC). **Nextcloud restore drill passed 2026-07-08.** Remaining: 7-day
success gate (2/7 as of 2026-07-08).
**Done when:** platform dependencies can be deployed and restored without the
Forgejo app running.
@ -512,9 +512,12 @@ Forgejo also hosts `issue-core`, `activity-core`, `hub-core`, `core-hub`,
**Hub drift (2026-07-08):** tier-2.5 + `ops-warden` `remote_url` patched.
Hub: **12 Forgejo** / 51 Gitea remotes (Forgejo-hosted registered repos aligned).
**Remaining:** tier-3 promotion for remaining production repos; scheduled
backups 7-day gate (1/7); stabilization closeout + operator signoff before
coulombcore teardown.
**Wave 2 tier-2 (2026-07-08):** `ops-bridge`, `open-reuse`, `artifact-store`
promoted to Forgejo + hub `remote_url` patched. Forgejo org now **20 repos**.
**Remaining:** tier-3 promotion for remaining production repos (`llm-connect`,
`the-custodian`, `flex-auth`, …); scheduled backups 7-day gate (2/7);
stabilization closeout + operator signoff before coulombcore teardown.
**Done when:** tiers 02 pass with written result matrices and no unknown
critical migration gaps remain for production repos. **Tiers 02.5: met.**
@ -597,10 +600,12 @@ T03 isolated probe: CANCELLED (superseded by T05 + in-production pilots)
```
**Current focus (2026-07-08):** T05/T06/T07/T08 **done**; T09 restore drill **passed**;
backup 7-day gate **1/7** (chunked `forgejo-backup` fix in `railiance-platform`;
intermittent kubelet 502 on manual rerun). T10: `ihp-railiance-probe` promoted
tier-1 + hub `remote_url` patched; wave-2 queue in inventory (29 hub-registered
Gitea-only repos). Next: backup gate, tier-3 wave with operator approval.
backup 7-day gate **2/7** (chunked `forgejo-backup` fix in `railiance-platform`;
cron 02:15 UTC). T10: tier-1 `ihp-railiance-probe` + tier-2 `ops-bridge`,
`open-reuse`, `artifact-store` promoted; Forgejo org **20 repos**; hub remotes
patched for all promoted registered repos.
Next: backup gate (passive), tier-3 wave with operator approval (`llm-connect`,
`the-custodian`, `flex-auth`).
**Absorbed by `CUST-WP-0054-T04`:** forge + CI on railiance01; workstation
build retirement; staged repo promotion before State Hub primary move (T05).