Update stabilization checkpoint after app contract
This commit is contained in:
@@ -25,7 +25,7 @@ State Hub active workstreams queried on 2026-06-27:
|
||||
| `cust-wp-0051` | This metaplan is the coordination layer for remaining cross-workplan gates. |
|
||||
| `activity-wp-0016-llm-output-robustness-trust-boundary` | Repo-side output robustness bundle is prepared; live deploy/smoke proof remains. |
|
||||
| `three-phoenix-ha-cluster` | HA substrate remains future critical-workload work, not the current State Hub cutover blocker. |
|
||||
| `staged-promotion-lifecycle` | Start T02 to make promotion gates concrete before broad production migrations. |
|
||||
| `staged-promotion-lifecycle` | T02 `railiance/app.toml` contract is done; continue with T03 overlay repo pattern and T04/T05 command/canary implementation before broad production migrations. |
|
||||
| `rail-ho-wp-0005` | Forgejo production migration is parked behind explicit design, SMTP, backup, runner, and cutover decisions. |
|
||||
| `net-wp-0020` | OpenBao unseal/token custody remains an operator design and smoke gate. |
|
||||
| `issue-wp-0003` | issue-core service is healthy; activity-core REST emission wiring remains. |
|
||||
@@ -106,8 +106,8 @@ Resume from `docs/daily-triage-stabilization-status.md` and
|
||||
`ISSUE_SINK_TYPE=rest` and one known-safe emission smoke.
|
||||
5. Request explicit State Hub cutover approval for `CUST-WP-0011-T07`, or
|
||||
record that WSL2 remains primary for the next operating period.
|
||||
6. Start staged-promotion T02 and artifact-store D7.1/D7.2 so Forgejo and
|
||||
storage work inherit clear production promotion gates.
|
||||
6. Continue staged-promotion T03/T04/T05 and start artifact-store D7.1/D7.2
|
||||
so Forgejo and storage work inherit clear production promotion gates.
|
||||
7. Keep Forgejo cutover and State Hub HA work parked until their human decision
|
||||
and drill gates are satisfied.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user