coulomb/state-hub
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(statehub): record railiance data restore

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-25 16:00:39 +02:00
parent 7661146b48
commit cf00d3bba5
1 changed files with 16 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
workplans/CUST-WP-0011-state-hub-threephoenix-migration.md
View File

@@ -303,8 +303,9 @@ returning `{"status":"ok","db":"connected"}`.
```task
id: CUST-WP-0011-T06
status: todo
status: done
priority: high
completed: "2026-06-25"
state_hub_task_id: "03753b88-824c-4448-97b2-f7315d145060"
```
@@ -322,6 +323,20 @@ Required comparison:
**Done when:** cluster data is a verified copy of WSL2, but not yet the only
writer.
Completed 2026-06-25: restored a fresh WSL2 State Hub PostgreSQL dump into
the cluster `state-hub-db` database while WSL2 remained the live source of truth.
Scaled the cluster API to zero during restore, restored the newer dump after a
one-row live `progress_events` drift was detected, then scaled the API back
to one replica. Verified all public table row counts match between WSL2 and
the cluster, including `workplans=569`, `tasks=3673`,
`decisions=71`, `progress_events=6232`, `managed_repos=71`,
and `token_events=1881`. Representative restored-data checks found this
workplan, the T06 task, decisions, progress events, the `state-hub` repo,
and token events queryable. Cluster API `/state/health` returned
`{"status":"ok","db":"connected"}` through a temporary port-forward,
and `/state/summary` returned expected totals. Temporary dump files and
port-forwards were removed after verification.
---
### T07 — Cut over private access to cluster State Hub