Update stabilization checkpoint after overlay scaffold
This commit is contained in:
@@ -295,8 +295,23 @@ Progress 2026-06-27 staged promotion:
|
||||
rollback, and human approval gates.
|
||||
- `make fix-consistency REPO=railiance-cluster` passed with pre-existing
|
||||
C-12 warnings and synced the T02 status into State Hub.
|
||||
- Next staged-promotion picks are T03 overlay repo pattern, then T04/T05
|
||||
command and canary template implementation.
|
||||
- Next staged-promotion picks are T04/T05 command and canary template
|
||||
implementation; T03 overlay repo pattern is now complete.
|
||||
|
||||
Progress 2026-06-27 staged promotion T03:
|
||||
|
||||
- Completed `RAIL-BS-WP-0006-T03` in `/home/worsch/railiance-cluster`.
|
||||
Added `docs/overlay-repo-pattern.md`,
|
||||
`tools/create_railiance_overlay_repo.sh`, and the `bin/railiance
|
||||
create-overlay` dispatcher entry. The scaffold writes a separate overlay
|
||||
repo with `railiance/upstream.toml`, schema-valid `railiance/app.toml`,
|
||||
stage values, a thin Helm chart, Stage 1 test script, rollback runbook, and
|
||||
promotion notes without cloning upstream code or handling secrets.
|
||||
- Verified the generated Forgejo overlay sample against
|
||||
`schemas/railiance-app.schema.json`; generated Stage 1 script ran with Helm
|
||||
skipped because Helm is unavailable in this environment.
|
||||
- `make fix-consistency REPO=railiance-cluster` passed with pre-existing
|
||||
C-12 warnings and synced the T03 status into State Hub.
|
||||
|
||||
## Task: Decide State Hub Migration Strategy
|
||||
|
||||
|
||||
Reference in New Issue
Block a user