prj-state-hub-retirement/WORK-RECORDS.md

# Work Records — prj-state-hub-retirement

> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
> stage 3). Do not edit by hand — edit the source file/block listed for
> each record and re-run fix-consistency to refresh this index. Archived
> workplans are omitted; closed decisions/intakes/engagements stay listed
> so recently-resolved work is still visible. [auto]

| Kind | ID | Status | Lane | Source |
| --- | --- | --- | --- | --- |
| workplan | SHR-WP-0001 | finished | — | workplans/SHR-WP-0001-foundation.md |
| workplan | SHR-WP-0002 | proposed | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0001-T01 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T02 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T03 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T04 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T05 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0001-T06 | done | — | workplans/SHR-WP-0001-foundation.md |
| task | SHR-WP-0002-T01 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T02 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T03 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T04 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T05 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T06 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
| task | SHR-WP-0002-T07 | todo | — | workplans/SHR-WP-0002-predecessor-and-deployment-reality.md |
Seed State Hub retirement project 2026-08-09 16:36:17 +02:00			`# Work Records — prj-state-hub-retirement`

			> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
			`> stage 3). Do not edit by hand — edit the source file/block listed for`
			`> each record and re-run fix-consistency to refresh this index. Archived`
			`> workplans are omitted; closed decisions/intakes/engagements stay listed`
			`> so recently-resolved work is still visible. [auto]`

			`\| Kind \| ID \| Status \| Lane \| Source \|`
			`\| --- \| --- \| --- \| --- \| --- \|`
chore(consistency): refresh WORK-RECORDS after foundation finish 2026-08-09 21:47:22 +02:00			`\| workplan \| SHR-WP-0001 \| finished \| — \| workplans/SHR-WP-0001-foundation.md \|`
SHR-WP-0002: correct the premise — gen 2 was retired properly T01 executed and disproved the workplan's own first draft. core-hub's archive shows CORE-WP-0005 closed the production cutover gates on 2026-07-03 and CORE-WP-0007 retired the Haskell/IHP infrastructure by 2026-07-08, with a stabilization window and explicit operator approval to retire the Inter-Hub rollback deployment. The 0/0 Deployment on railiance01 is that rollback standby at its designed end state, not a lapse. The surviving finding is sharper and more urgent: hub.coulomb.social resolves to 92.205.130.254 — CoulombCore — so Core Hub's production runtime, in service since July, sits on the host being decommissioned, with no core-hub presence on railiance01 and hub-core still a package rather than a service. The workplan is retitled and re-centred on that. DECISIONS.md records the correction and why it generalises: the live documents described a retirement that had already happened while the completed evidence sat in an archived workplan, so a reader checking current files reaches the wrong conclusion. That requirement applies directly to the State Hub retirement this project is planning. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 2026-08-20 08:07:53 +02:00			`\| workplan \| SHR-WP-0002 \| proposed \| — \| workplans/SHR-WP-0002-predecessor-and-deployment-reality.md \|`
chore(consistency): refresh WORK-RECORDS after T01 2026-08-09 17:27:36 +02:00			`\| task \| SHR-WP-0001-T01 \| done \| — \| workplans/SHR-WP-0001-foundation.md \|`
chore(consistency): refresh WORK-RECORDS after T02 2026-08-09 17:37:03 +02:00			`\| task \| SHR-WP-0001-T02 \| done \| — \| workplans/SHR-WP-0001-foundation.md \|`
chore(consistency): refresh records after T03 2026-08-09 17:45:24 +02:00			`\| task \| SHR-WP-0001-T03 \| done \| — \| workplans/SHR-WP-0001-foundation.md \|`
chore(consistency): refresh WORK-RECORDS after T04 2026-08-09 18:00:53 +02:00			`\| task \| SHR-WP-0001-T04 \| done \| — \| workplans/SHR-WP-0001-foundation.md \|`
chore(consistency): refresh WORK-RECORDS after T05 2026-08-09 21:40:12 +02:00			`\| task \| SHR-WP-0001-T05 \| done \| — \| workplans/SHR-WP-0001-foundation.md \|`
chore(consistency): refresh WORK-RECORDS after foundation finish 2026-08-09 21:47:22 +02:00			`\| task \| SHR-WP-0001-T06 \| done \| — \| workplans/SHR-WP-0001-foundation.md \|`
SHR-WP-0002: correct the premise — gen 2 was retired properly T01 executed and disproved the workplan's own first draft. core-hub's archive shows CORE-WP-0005 closed the production cutover gates on 2026-07-03 and CORE-WP-0007 retired the Haskell/IHP infrastructure by 2026-07-08, with a stabilization window and explicit operator approval to retire the Inter-Hub rollback deployment. The 0/0 Deployment on railiance01 is that rollback standby at its designed end state, not a lapse. The surviving finding is sharper and more urgent: hub.coulomb.social resolves to 92.205.130.254 — CoulombCore — so Core Hub's production runtime, in service since July, sits on the host being decommissioned, with no core-hub presence on railiance01 and hub-core still a package rather than a service. The workplan is retitled and re-centred on that. DECISIONS.md records the correction and why it generalises: the live documents described a retirement that had already happened while the completed evidence sat in an archived workplan, so a reader checking current files reaches the wrong conclusion. That requirement applies directly to the State Hub retirement this project is planning. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 2026-08-20 08:07:53 +02:00			`\| task \| SHR-WP-0002-T01 \| todo \| — \| workplans/SHR-WP-0002-predecessor-and-deployment-reality.md \|`
			`\| task \| SHR-WP-0002-T02 \| todo \| — \| workplans/SHR-WP-0002-predecessor-and-deployment-reality.md \|`
			`\| task \| SHR-WP-0002-T03 \| todo \| — \| workplans/SHR-WP-0002-predecessor-and-deployment-reality.md \|`
			`\| task \| SHR-WP-0002-T04 \| todo \| — \| workplans/SHR-WP-0002-predecessor-and-deployment-reality.md \|`
			`\| task \| SHR-WP-0002-T05 \| todo \| — \| workplans/SHR-WP-0002-predecessor-and-deployment-reality.md \|`
			`\| task \| SHR-WP-0002-T06 \| todo \| — \| workplans/SHR-WP-0002-predecessor-and-deployment-reality.md \|`
Correct T07: reuse-surface is live and stale; state-hub was mostly a false alarm Checking each image reference's liveness separated the two cases the first pass treated alike. reuse-surface is a live Deployment on gitea, pinned to a 2026-07-07 commit and 22 commits behind main. Its CI moved to forgejo at 21:25 that same day, three hours after the pinned commit, and has published :latest and :main-<short> there ever since. Producer migrated, consumer did not. state-hub's Deployment is already on forgejo with the current tag scheme. Its only gitea reference is a completed one-shot alembic-init Job that does not re-run on its own, so "unable to run its schema migration" was wrong. Residual risk is a chart template recreating it. No repository rename occurred — this is a registry migration in which one consumer was left behind. An image reference is not a dependency until something can act on it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 2026-08-20 08:54:21 +02:00			`\| task \| SHR-WP-0002-T07 \| todo \| — \| workplans/SHR-WP-0002-predecessor-and-deployment-reality.md \|`