docs: one deploy verb — deploy targets wherever the stack lives
`deploy` now resolves its target from the stack's topology and `release` is an
alias for `deploy --require-remote` (strut#415). The wiki taught the opposite
rule — Deployment.md literally advised "use release for VPS deployments, not
deploy" — so the framing is inverted throughout.
- Deployment: rewrite the opening, add "Where a Deploy Lands", document the
alias and the compatibility promise, --require-remote, and the pipeline skip
flags (--no-sync / --no-migrate / --no-rollback / --backup-first / --strict).
- GitHub-Action: `deploy` is the primary CI command and the action passes
--require-remote. Drop the "deploy has an interactive prompt and will hang a
hosted runner" guidance — the prompt no longer exists. Replace the "deploy
hangs in CI" entry with the failure that can actually bite now: a deploy that
silently targeted the runner.
- MCP-Server: strut_deploy runs deploy --require-remote and never falls back
to a local deploy.
- Sweep command examples across the wiki; leave `lock release` alone.
Add lead-in paragraphs to 7 wiki pages
docs: comprehensive wiki for strut CLI
20 pages covering:
- Getting Started (Installation, Quick Start)
- Core Concepts (Architecture, Configuration, CLI Reference)
- Operations (Deployment, Backups, Key Rotation, Drift, Domain/SSL, Monitoring, Volumes)
- Advanced (VPS Audit/Migration, Stack Validation, Debugging, Local Dev)
- Contributing (Conventions, Adding Commands, Project Structure)
- Sidebar navigation and footer