Hi Railway team - I just published the Stackray template from my workspace, but Railway assigned it the code stackray-1 instead of stackray.

Current published template:

• code: stackray-1
• id: 3c39a30a-467f-4b7e-9157-fd30f5c5ac0d
• workspaceId: c374462a-d073-487c-8507-bfe535ecc7a4
• status: PUBLISHED
• updatedAt: 2026-07-06T01:05:45.527Z

What looks wrong:

• Authenticated GraphQL template(code: "stackray-1") returns the published template.
• Authenticated GraphQL template(code: "stackray") returns Template not found.
• railway templates list --json only shows stackray-1.
• railway templates search stackray --json only returns stackray-1.
• curl -I https://railway.com/deploy/stackray returns HTTP 404 with x-cache: DYNAMIC.
• But a real browser request to https://railway.com/deploy/stackray returns HTTP 200 with x-cache: STALE and renders an older Stackray template page. The stale page links to /new/template/stackray.
• Adding a query string, e.g. https://railway.com/deploy/stackray?codex_cache_bust=..., correctly returns the 404/dynamic page.

So it looks like the bare /deploy/stackray path is stale edge/frontend cache, while the backend no longer has a stackray template code. Can you purge the stale /deploy/stackray cache and/or release/reassign the stackray code to my published stackray-1 template?

For now I am using https://railway.com/deploy/stackray-1, but I would prefer the canonical https://railway.com/deploy/stackray if possible.