muggle-upgradelisted

# Muggle Test Upgrade > Telemetry first step: see [`_shared/telemetry-emit.md`](../_shared/telemetry-emit.md). Use `skillName: "muggle-upgrade"`. Update all Muggle AI components to the latest published version. This means **both** the `@muggleai/works` CLI on npm **and** the Electron runner the CLI manages. ## Steps 1. Run `/muggle:muggle-status` checks to capture current versions. 2. Capture CLI versions: - Installed CLI: `muggle --version` - Latest on npm: `npm view @muggleai/works version` - Detect install location: `npm ls -g @muggleai/works --depth=0` (falls back to `pnpm ls -g @muggleai/works` if not found) 3. **If installed CLI < latest on npm**, upgrade the CLI itself before touching Electron: - npm global install: `npm install -g @muggleai/works@latest` - pnpm global install: `pnpm add -g @muggleai/works@latest` - If neither is detected, report the situation and ask the user how the CLI was installed before proceeding. 4. Run `muggle upgrade` to pull the Electron runner version that the (now-latest) CLI expects. - Note: `muggle upgrade` only manages the Electron runner — it does NOT upgrade the CLI npm package. That is why step 3 must run first. 5. **Reload plugins** — the npm install (step 3) triggers a postinstall script that updates the plugin cache at `~/.claude/plugins/cache/`, but Claude Code only picks up new skills/agents/hooks after a reload. Tell the user: > Run **`/reload-plugins`** to load the updated skills, agents, and h