tegwick 669a98ce1c T07: reuse-surface escalated — live federation dependency, not just a stale image ... At the deployed commit, registry/federation/sources.yaml points at gitea.coulomb.social for 50 of 61 sources; all 61 are forgejo at HEAD after d1c1313. Production is actively federating from the host being switched off, so it breaks on 2026-08-31 with no restart required — a different and worse failure mode than the ImagePullBackOff risk it was first filed under. This also inverts the conservative option: rebuilding the pinned commit onto forgejo does not fix federation, because the gitea URLs are in the code at that commit. Deploying HEAD is the smaller intervention once the runtime dependency is counted. Side finding routed to the repo: REUSE-WP-0019 is archived as finished and records a production deploy of T01/T02, but T04-T06 — including hub freshness monitoring — landed after the deployed commit and appear never to have shipped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-08-20 22:37:19 +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: reuse-surface escalated — live federation dependency, not just a stale image	2026-08-20 22:37:19 +02:00