Please force-remove the orphaned Cloudflare-for-SaaS custom hostnames tastelab.recipes and www.tastelab.recipes — they were deleted from the taste-lab-app service but the edge is still routing them to Railway.

Details:

• Project: taste-lab (ae20f280-8c5a-46e6-90e0-1e7194be41fd), service taste-lab-app (b80016eb-67ec-4745-a952-da8393f6a852), production environment.
• • Both custom domains were removed from the service earlier today (they had briefly been orphaned on a deleted service, were re-adopted onto taste-lab-app, then deleted). The dashboard now shows only taste-lab-app-production.up.railway.app — no custom domains anywhere in the account.
• • Our Cloudflare DNS for both hostnames points at our own Cloudflare Tunnel (proxied CNAME to cfargotunnel.com), yet 60+ minutes after deletion every request still returns x-railway-edge: bcn1 / x-railway-request-id — i.e. Cloudflare O2O is still handing traffic to Railway's Cloudflare-for-SaaS zone.
• • This suggests the custom_hostname entries for tastelab.recipes and www.tastelab.recipes are still present in Railway's Cloudflare-for-SaaS configuration and need manual removal.

Could you please purge those two custom hostnames from Railway's Cloudflare-for-SaaS zone so the domains resolve to our own origin again? Thank you!