Credits railiance-apps for the org-level Forgejo webhook (they picked it
up after I flagged the /health ingress bug via State Hub, and reused the
same K8s Secret value rather than inventing a new one). Records this
repo's own migration: created on Forgejo (private:false, matching every
other migrated repo -- confirmed via API, then got explicit user sign-off
specifically on that parameter), ci.yml/ci-smoke.yaml/image.yaml all
verified green on the live push, recompose-fallback.yaml deployed but
blocked on a repo secret write pending separate sign-off (same boundary as
the T02 K8s Secret write). Gitea remote kept read-only per the migration
playbook's safety contract, not deleted.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
tegwick
bd6fcf0d45