## Context
Railpack builds a Node SPA but no Caddyfile is auto-generated, so the deploy step `caddy run --config /Caddyfile --adapter caddyfile` fails. The build log shows no `caddy` step even though the app is detected as a vite static site.

## Verified resolution
Maintainer coffee-cup: Railpack disables the Caddy/static-site flow when it detects a custom start command (`if a user has specified a custom start command, then assume thats what they want to run`). Fix: remove the custom start command, or set the `RAILPACK_SPA_OUTPUT_DIR` env var to the static output directory (e.g. `dist`) to force SPA/Caddy handling.