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.
Document v0.9.0-v0.16.0 features - Add pages: Stack Groups, Lifecycle Hooks, Notifications, Security Posture - Update CLI Reference with new commands: posture, status-all, diff, group, rollback diff, backup offsite - Update Deployment (diff preview, concurrency locks, hooks) - Update Deploy Rollback (snapshot diff, prune protection) - Update Database Backups (offsite sync for S3 / R2 / B2) - Cross-reference posture and notifications from Monitoring - Reference status-all dashboard from Debugging - Bump Home.md to v0.16.0