baocut

# BaoCut Use the bundled resolver for every command. On macOS/Linux: ```bash BAOCUT_SKILL_ROOT="<this-skill-directory>" "$BAOCUT_SKILL_ROOT/bin/baocut" --json version ``` On Windows, run the native PowerShell resolver (WSL is not required): ```powershell $env:BAOCUT_SKILL_ROOT = "<this-skill-directory>" & "$env:BAOCUT_SKILL_ROOT\bin\baocut.ps1" --json version ``` ## Mandatory startup version gate Run this gate once at the start of every BaoCut task, before `spec`, `doctor`, any project command, or reuse of an existing `bcut serve`: 1. Explicitly run the platform resolver's `--json version` command above and retain its `appVersion` and `commit`. A successful resolver handshake, a compatible `spec`, `doctor`, or `serve --status` is not an update check. 2. Immediately read and execute [references/updates.md](references/updates.md): fetch the published appcast and compare its version numerically with the local `appVersion`. Only an unavailable appcast may be reported as skipped. 3. When the appcast is newer, update the standalone skill and let its refreshed resolver download, verify, and cache the pinned CLI before continuing. Do not merely report the update or keep using the compatible old CLI. Never overwrite a development checkout or an App-bundled skill; use the supported source/App update path documented in the reference instead. 4. After any CLI update, run the refreshed resolver with `serve --background`, then `serve --status`. This idempo...