prj-state-hub-retirement/workplans
tegwick 9f4caa1c09 T07: full gitea sweep — CoulombCore runs two registry services, not one
gitea.coulomb.social also serves a PyPI package index, so the container-image
finding was half the exposure.

Classified every operational reference by whether anything can still act on it.
Live and must move: reuse-surface's Deployment image, and kaizen-agentic, which
never migrated at all — it publishes to gitea PyPI and its README and five docs
instruct users to pip install from it, with no forgejo equivalent in the repo.
issue-core already dual-publishes and only needs its legacy gitea target retired.

Deliberately left alone: tests asserting historical facts, inventory snapshots,
asset registers and a Dockerfile comment. They record that gitea existed, which
remains true after it is switched off; rewriting them would destroy history to
tidy a grep.

Flagged unswept: CI runners, and any credential lane authenticating to gitea.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 08:58:28 +02:00
..
SHR-WP-0001-foundation.md chore: sync foundation workplan after consistency 2026-08-09 21:47:52 +02:00
SHR-WP-0002-predecessor-and-deployment-reality.md T07: full gitea sweep — CoulombCore runs two registry services, not one 2026-08-20 08:58:28 +02:00