RAIL-HO-WP-0005: record tier 2.5 railiance stack Forgejo promotion
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Inventory and workplan updates for enablement templates, tegwick SSH, and
railiance-* repos canonical on forgejo-remote.
This commit is contained in:
tegwick 2026-07-04 12:51:05 +02:00
parent 67beab1525
commit c664aebd1d
2 changed files with 18 additions and 4 deletions

View file

@ -216,6 +216,11 @@ refresh:
| `forgejo-actions-probe` | — | yes | 0 | Disposable runner/OCI probe |
| `glas-harness` | yes (not in table above) | yes (canonical) | 1 | Git+SSH+CI pilot |
| `key-cape` | yes | yes (canonical) | 2 | Image CI + `crictl pull` on railiance01 |
| `railiance-enablement` | yes | yes (canonical) | 2.5 | S4 workflow templates |
| `railiance-infra` | yes | yes (canonical) | 2.5 | Stack promotion |
| `railiance-apps` | yes | yes (canonical) | 2.5 | Stack promotion |
| `railiance-platform` | yes | yes (canonical) | 2.5 | Stack promotion |
| `railiance-cluster` | yes | yes (canonical) | 2.5 | Stack promotion |
Evidence: `the-custodian/docs/forgejo-repo-migration-pilot-glas-harness.md`

View file

@ -101,6 +101,7 @@ Integration evidence now comes from **in-production probes and repo pilots**:
| 0 | `coulomb/forgejo-actions-probe` | Runner scheduling, DinD, OCI image-build | **done** |
| 1 | `coulomb/glas-harness` | Non-production git+SSH+CI routing drill | **done** |
| 2 | `coulomb/key-cape` | Image-build workflow + registry pull on railiance01 | **done** |
| 2.5 | `railiance-enablement`, `railiance-infra`, `railiance-apps`, `railiance-platform`, `railiance-cluster` | Stack repos on Forgejo + S4 templates | **done** |
| 3 | Production set (`state-hub`, `issue-core`, …) | Canonical remotes, sweep paths, deploy loops | **gated** |
Each tier must pass before the next. T03 (isolated probe namespace) is cancelled;
@ -366,8 +367,10 @@ non-root (static docker-cli, no `apk add`); `actions/checkout@v4` fails — use
`railiance-enablement` (S4); resource limits review; no cluster-admin on runner.
**Partial (2026-07-04):** tier-2 satisfied by `key-cape` (`container-build`,
archive checkout, static docker-cli). Remaining: publish reusable workflow
template in `railiance-enablement` (S4).
archive checkout, static docker-cli). **Templates (2026-07-04):** S4
`railiance-enablement/workflows/` (`ci-smoke`, `container-build-push`,
`container-build-push-multirepo` for `hub-core` contexts) +
`docs/forgejo-actions-workflow-templates.md`. Remaining: resource limits review.
**Done when:** tier-2 pilot repo runs Forgejo Actions end-to-end and publishes
a pullable image without privileged cluster-wide credentials. **Tier 2: done.**
@ -448,8 +451,13 @@ pushed via archive-checkout workflow; `crictl pull` on railiance01 succeeded.
Evidence in `the-custodian/docs/forgejo-repo-migration-pilot-glas-harness.md`
(tier 2 section).
**Not ready:** `state-hub` (tier 3) until hub-core build context template and
sweep `remote_url` playbook exist.
**Tier 2.5 complete (2026-07-04):** railiance stack repos on Forgejo with
`origin=forgejo-remote`, `gitea` legacy remote, `ci-smoke` workflows; operator
`tegwick` SSH on Forgejo; enablement templates published. Evidence: pilot doc
tier 2.5 section.
**Not ready:** `state-hub` (tier 3) until sweep `remote_url` playbook exists and
scheduled backups gate is closed (disaster-control).
**Done when:** tiers 02 pass with written result matrices and no unknown
critical migration gaps remain for production repos.
@ -525,6 +533,7 @@ T05+T08 ──► T10 migration ladder ──► T11 production cutover ──
tier0 probe ✓
tier1 glas-harness ✓
tier2 key-cape ✓
tier2.5 railiance-stack ✓
tier3 production (gated)
T03 isolated probe: CANCELLED (superseded by T05 + in-production pilots)