Retired custom deployment target remains in Caddy migration

What

The Caddy deployment work in #95 still offers and defaults to the retired custom destination. Script deployments now use only CDN and Caddy.

The deployment prompt and upload paths should reflect the active infrastructure so deployments do not contact the retired external server.

Track the cleanup in a separate pull request targeting #95's caddy branch so the change is easy to review before #95 merges into main.

Implemented in scripts#119, merged into the caddy branch. It ships with scripts#95.