Rename an app (routing alias, owner only)
Renaming is fully open (not limited to zero-Release apps): the app name is a routing alias, so a rename publishes no version, invalidates no old version, and does not affect runs in flight (all persistent references pin app_id).
Broken caller references are the developer’s own responsibility:
old owner/old-name references (MCP ?tools= / SDK / REST / detail
page URLs) return a clean 404 after the rename, with no redirect;
historical runs and billing echo the new name. The old name cannot
be taken by others under your namespace, but you yourself may later
create a new app with it — at which point stray external references
would point at that new app (you are reminded again at creation).
Consumers are advised to integrate against app_id instead, which is
immune to future renames.
The validation chain mirrors identity creation: pattern → reserved
words → new name != current name; colliding with someone else’s
historical binding is 409 app-name-reserved, with another app of
your own 409 app-name-taken.