docs(CUST-WP-0054): record Phase 2 data migration evidence

coulombcore frozen; pg_restore to railiance01 with exact-count gate pass.
Phase 3 access rewire still pending.
This commit is contained in:
codex
2026-07-06 18:51:59 +02:00
parent 149afb104d
commit 5961e74bfc
2 changed files with 68 additions and 6 deletions

View File

@@ -218,12 +218,12 @@ so file writebacks no longer touch workstation paths.
`fleet-state-hub-coulombcore``:18000`. Target hostname for sweep paths:
`239.62.205.92.host.secureserver.net`. **Phase 0 preflight done** (2026-07-06):
baseline counts recorded — `docs/state-hub-railiance01-cutover-preflight-2026-07-06.md`.
**Phase 1 complete** (2026-07-06): empty stack on railiance01 — CNPG `state-hub-db`
healthy, Alembic at head, `/state/health` ok, baseline tables 0 rows; Service
ClusterIP `10.43.68.154:8000`. Deploy uses `gitea…:f2e042a` workaround (Forgejo
`main-f9f0091` empty venv); rebuild before Phase 2 —
`docs/state-hub-railiance01-cutover-phase1-2026-07-06.md`. **Blocked on operator
approval** before Phase 2 freeze/restore.
**Phase 1 complete** (2026-07-06): `docs/state-hub-railiance01-cutover-phase1-2026-07-06.md`.
**Phase 2 complete** (2026-07-06): coulombcore writer frozen (Deployment 0);
`pg_dump` restored to railiance01 with exact-count match (640 wp / 4002 tasks /
8723 progress); railiance01 API on `forgejo…:main-d1a4fcf`, ClusterIP
`10.43.68.154:8000``docs/state-hub-railiance01-cutover-phase2-2026-07-06.md`.
Workstation `:8000` still points at frozen coulombcore until **Phase 3 rewire**.
## Task: Working-memory and sink path decoupling