vps-opslisted

# vps-ops — VPS deploy & management (Coolify) Takes a project built by `buildout` and ships it to a real server: bootstrap the VPS, install Coolify, point the domain, deploy, and then run the whole "user asks for a change → it ships" loop — all from the harness, without the user ever touching the server. ## When to use - The user wants to deploy/host/go live, mentions a VPS, Coolify, domain/DNS/SSL, or "put my app online". - Any post-deploy request: check status, read logs, ship a change, roll back, backups, updates. - The buildout skill finished in the project — deploy is the next phase. - The user has no VPS/domain yet, or wants a $0 live preview → Track F: `references/11-oracle-free-tier.md` (+ `21` for the free domain). - The user wants to leave the preview (or move any server → server) → `references/60-migrate-to-paid.md`. ## The promise (what the user does vs what you do) First read the user's portable files — `~/.deckhand/profile.md` (accounts, providers, defaults) and `~/.deckhand/pending.md` (the ledger of human tasks; skill `deckhand-profile`). Never re-ask what the profile answers. **Surface open pending items in every report** (short, with ages) and **record new human tasks the moment they appear** — keys to paste, clicks, escrows, rotations. The user provides ONLY: VPS + domain (+ optionally a provider API token). Everything else is your job. One-time browser moments are unavoidable and guided click-by-click in `references/00-user-checklist.md` — on Track P