setup-auto-updaterlisted

# Set up the streamer auto-updater The streamer can update itself from GitHub Releases via three independent triggers (manual / scheduled / webhook). This skill handles the common case: an operator who already has the streamer deployed and wants it to stay current without manual `npm run deploy` runs. **Authoritative reference**: [`docs/guides/auto-update.md`](../../../docs/guides/auto-update.md). Read it before going beyond the steps below — it has the full command list, env-var overrides, failure modes, the Windows pre-swap stop ordering, and the release/branching model. Don't paraphrase from memory; quote or link. ## Step 1 — Create the config ```sh cp docs/update.yaml.example ~/.threadbase/update.yaml ``` That's enough for manual updates. The only required field is `github_repo`; everything else has sensible defaults. Without this file, `threadbase-streamer update` exits with a no-op message — that's the disabled state. ## Step 2 — Verify with `--check` ```sh threadbase-streamer update --check ``` Should print `Current`, `Latest`, `Channel`, `Diff`, `Status`. If `Status` is `Already up to date` or `Would install X → Y (...)`, GitHub auth + config are good. If the streamer can't reach GitHub, `--check` is where it surfaces. ## Step 3 — One manual install ```sh threadbase-streamer update ``` Runs the full pipeline: download → sha256 verify → unpack → atomic swap → service restart. On macOS/Linux the swap is a symlink rename; on Windows the updater stops the serv