Store deployment configs locally for binary deployments

For binary and static deployments, .ship/service and .ship/Caddyfile are
now written to the local working directory (similar to git deployments)
instead of being regenerated on every deployment.

- On initial deployment, create local .ship/ directory with generated configs
- On subsequent deployments, upload from local .ship/ files
- Caddyfile is never regenerated, preserving custom routes
- Systemd service is regenerated only when --memory, --cpu, or --args change

This prevents custom Caddyfile routes from being overwritten and makes
binary deployment workflow consistent with git deployment workflow.

0 files changed, 0 insertions, 0 deletions