docs: record state-hub Forgejo CI promotion main-0ca9c27 (Helm rev 8)

Update Phase 5 cutover evidence and CUST-WP-0054 T05 notes after
image.yaml #31 build and railiance01 deploy with working-memory sweep.
This commit is contained in:
codex
2026-07-07 01:14:11 +02:00
parent 26a3dca511
commit b8412994b7
2 changed files with 5 additions and 3 deletions

View File

@@ -96,8 +96,9 @@ succeeds, and operator approves coulombcore hub teardown window.
1. **Sweep budget** — 300s processes ~810 dirty repos per tick; expect gradual
reconciliation across 15m cron cycles (not a blocker).
2. ~~**Image tag**~~**resolved 2026-07-06T18:15Z**: Forgejo CI `image.yaml #26`
published `main-375961c`; Helm rev 7 deployed; post-upgrade sweep `exit_code=0`.
2. ~~**Image tag**~~**resolved 2026-07-07T01:10Z**: Forgejo CI `image.yaml #31`
published `main-0ca9c27` (working-memory sweep commit support); Helm rev 8
deployed; `/state/health` ok. Prior `main-375961c` (rev 7) superseded.
3. **Stale tunnel**`state-hub-coulombcore` shows `[STALE]`; safe to retire after
stabilization if unused.
4. **issue-core** — still coulombcore-chained; tracked under Wave 4 / T06, not T05.

View File

@@ -234,7 +234,8 @@ clone tree + sweep hostname override, remote-all sweep exit_code=0 —
**Phase 5 in progress** (2026-07-06 → 2026-07-09): 72h stabilization window open;
kickoff baseline green — `docs/state-hub-railiance01-cutover-phase5-2026-07-06.md`.
Post-cutover daily triage verified (manual 2026-07-06T17:50Z, event `a99e644e`).
Forgejo CI image promoted (`main-375961c`, Helm rev 7). Day-1 check (2026-07-06T22:35Z):
Forgejo CI image promoted (`main-0ca9c27`, Helm rev 8; working-memory sweep).
Day-1 check (2026-07-06T22:35Z):
640/4002/14, pod 0 restarts, 6/6 sweeps exit_code=0 proc=11 missing=0,
`state-hub-primary` LIVE. Phase 5 checks scheduled in activity-core:
`phase5-stabilization-daily` (09:00 Europe/Berlin) and one-shot closeout