docs(action): document the inputs the published action actually has The GitHub Action page described a different action. Its input table came from the action.yml that used to sit in the strut repo — an orphaned copy that was never published — while every `uses:` line on the page correctly points at gfargo/strut-action, which has a different interface. Anyone following this page passed inputs that do not exist. GitHub warns on unknown inputs but does not fail, so `ssh-port: 2222` was silently dropped and the deploy used port 22. ssh-port -> port version -> strut-version (default is `latest`, not a pinned v0.28.0) env-vars -> env-file (whole file contents, not KEY=VALUE lines) deploy-dir -> removed (no equivalent input) Adds the inputs that were missing entirely: args, known-hosts, working-directory. Corrects `host` to optional and `env` to defaulting empty. Rewrites the extra-secrets section, since env-file has different semantics from the env-vars it replaces. The orphaned action.yml is now deleted from the strut repo.
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.
docs: update for v0.42.x — deploy health gate, version bump - CLI-Reference: add --skip-health-gate flag to deploy command - Deployment: new 'Deploy Health Gate' section documenting DEPLOY_HEALTH_TIMEOUT, DEPLOY_SKIP_HEALTH_GATE, and the --skip-health-gate flag - Home: bump version badge to 0.42.1
docs: add briefing + preflight commands and MCP tools - CLI-Reference: briefing (situation report) and preflight (deploy go/no-go) under Monitoring & Status (since v0.41.0) - MCP-Server: add strut_briefing + strut_preflight to the read-only tools table with a note on their synthesis (aggregation) nature
Restructure Installation as two clear choices (git-based vs Homebrew) Previously stacked Quick Install, Manual Install, and Homebrew as three sequential sections with Homebrew buried under Upgrade Details. curl-script and manual git clone are the same underlying mechanism (automated vs by hand), so they're now framed as one 'Git-based' choice with Homebrew as the other — a clear two-way decision instead of a pile of options.
Document v0.30.0-v0.35.0 features: MCP server, webhooks, fleet status, SSL auto-provision, restore rehearsal, drift images, unified skills
docs: replace GitHub-Actions with comprehensive GitHub-Action page Merges the full action documentation (inputs, command semantics, security notes, troubleshooting) from the main repo's wiki/ dir into the canonical wiki. Renames to singular 'GitHub-Action' to match the wiki link convention.
docs: update wiki for v0.29.0 — fleet sync, hooks, data safety, upgrade
docs: list Tier-2 recipes (gitea, umami, wg-easy, paperless-ngx, audiobookshelf, ghost)
docs: document strut doctor --deep VPS preflight New in the doctor family — full VPS readiness check.
docs: list minecraft, pihole, nextcloud recipes Add the three new first-party recipes to the built-in recipes table.
docs: add GitHub Actions page (gfargo/strut-action) Document the official GitHub Action for CI deploys: quickstart, inputs table, required secrets, release-vs-deploy in CI, security, and versioning. Linked under Operations in the sidebar.
docs: fix CLI inaccuracies and sync to v0.28.0 - Version badges → 0.28.0 (Home, _Footer); Multi-Host 'since' → v0.22.0 - CLI-Reference: correct audit:diff signature (<host> [user] [key] [port]) - Deployment: logs --tail 50 → --since 30m (no --tail flag exists) - Configuration + Volume-Management: volume.conf is shell vars + VOLUME_OWNERS, not colon rows - Key-Rotation: ssh:keygen stores in ~/.ssh/strut_<host>_*; ci:init also supports gitlab/manual - Database-Backups: backup cleanup → backup retention enforce - Data-Anonymization: hash uses HEX() on SQLite (no SHA256) - Local-Development: local env file is stacks/<stack>/.env.local - Agent-Steering: add development-workflow.md steering file - VPS-Audit-and-Migration: fix reversed audit key/port args - Monitoring: remove nonexistent flags/commands (--env/--vps, reload/update/restart/backup, alert-route, webhook --method); correct env-file reference - Domain-and-SSL: document Caddy reverse-proxy backend (automatic HTTPS)
docs: update wiki for v0.27.0 — expanded secrets lifecycle, ssh:keygen, ci:init
docs: update for v0.27.0 — secrets lifecycle, registry rotation, CLI reference - Sync Secrets-Management.md with comprehensive provider/lifecycle docs - Add secrets hydrate/status/rotate/template/export/lock/unlock to CLI Reference - Add keys rotate-registry and registry-status to Key-Rotation and CLI Reference - Update version badge to 0.27.0
docs: add ci:init command to CLI Reference
docs: remove Agent Smoke Test page (smoke-test cleanup)
Wiki: add an Agent Smoke Test page (wiki update via horizon-agent)
docs: remove Agent Smoke Test page (cleanup)
docs: add Agent Smoke Test page (wiki-mode smoke test)
docs: update wiki to v0.26.0 — add pages for ship, rebuild, secrets, gateway, certs, provisioning
docs: add secrets push/pull/diff/validate to CLI Reference (v0.26.0)
docs: update Contributing and Project Structure for v0.24.0 test expansion
docs: add Multi-Host Topology page, BUILD_MODE docs, rebuild command
docs: add Remote Host Setup page and update CLI Reference for remote:init
Document v0.20.0: blue-green deploy mode New Blue-Green-Deploy page covers opt-in via DEPLOY_MODE=blue-green or --blue-green flag, the 9-step orchestration flow, the .bluegreen state file, tunables (BLUE_GREEN_HEALTH_TIMEOUT / BLUE_GREEN_DRAIN), compose file requirements (no container_name, no port collisions), proxy hook contract with shared-nginx and Caddy admin-API examples, fast state-file rollback, timeout tuning guidance, and common failure modes. CLI-Reference notes the new --blue-green/--standard flags and blue-green rollback behavior. Configuration gains the new strut.conf keys. Deployment links out to the new page, Home and Sidebar list it.
Updated Shell Completions (markdown)
Updated Interactive TUI (markdown)
docs: Interactive TUI page + v0.19.0 CLI reference updates Adds Interactive-TUI.md with usage, backends, --print, and disabling instructions. Sidebar links it under Getting Started. CLI-Reference picks up --no-tui, STRUT_NO_TUI, and the no-arg TUI form (since v0.19.0).
Document v0.18.0: scaffold recipes