upgrade-guardlisted

# Upgrade Guard 🔄 **Never lose a working OpenClaw to a bad upgrade again.** Born from 7 cascading failures during a single version jump. The gateway crashed, Telegram disconnected, plugins broke, models vanished — and the AI agent that caused it was also dead, so nobody could fix it remotely. This skill makes upgrades safe. ## The Problem OpenClaw upgrades can break in ways that are invisible until it's too late: | Failure type | Example | |---|---| | Plugin renames | `clawdbot.plugin.json` → `openclaw.plugin.json` | | Dependency breaks | SDK module paths change, exports shift | | Config schema changes | New required fields, removed fields | | Model name changes | Dot vs hyphen format changes | | Channel config wipes | Silent removal during migration | A single `git pull && pnpm install` can trigger all of these simultaneously. ## What Upgrade Guard Does ### 1. Snapshot (`snapshot`) Captures your entire working state: - Version + git commit - Full config backup - Plugin file inventory - Symlink map - Lock file - Channel list + model info - Gateway health status ### 2. Pre-flight (`check`) Before touching anything: - Snapshot exists? - Config valid? - Git repo clean? - Disk space OK? - Package manager available? - Remote changes preview - Breaking change detection (scans commit messages) ### 3. Safe Upgrade (`upgrade`) Controlled 6-step process: 1. Pre-flight checks (abort if fail) 2. Fresh snapshot 3. Stop gateway 4. `git pull` (rollback on fail) 5. `pnpm install`