Follow-up to plat/mcp#45. delete_app{repo_deleted} refuses when a repo of the same name exists (safe), but if a user re-creates owner/name before the delete relay lands, the old namespaces/overlay remain and create_app's re-join could attach the new repo to the old app's resources. Stamping the Forgejo repo id on app namespaces at create_app (plat.sh/repo-id) lets deleteApp remove exactly the old repo's resources and lets create_app refuse to re-join a different repo's overlay. Low urgency: needs a re-create within the seconds-long relay window.
Follow-up to plat/mcp#45. delete_app{repo_deleted} refuses when a repo of the same name exists (safe), but if a user re-creates
owner/namebefore the delete relay lands, the old namespaces/overlay remain and create_app's re-join could attach the new repo to the old app's resources. Stamping the Forgejo repo id on app namespaces at create_app (plat.sh/repo-id) lets deleteApp remove exactly the old repo's resources and lets create_app refuse to re-join a different repo's overlay. Low urgency: needs a re-create within the seconds-long relay window.