aware-updatelisted

# aware-update Check the user's installed AWARE CLI version against the latest published release, surface what's changed, and (with user consent) update in place using whichever install method they're on. ## When to invoke - User asks: "is AWARE up to date?", "what's new in aware?", "should I update?", "update aware" - User invokes `/aware-update` - During other AWARE workflows, if a behavior the user is hitting was fixed in a newer version, surface this skill as the path to upgrade Do NOT invoke this skill speculatively when the user is doing unrelated work — only when they ask, or when a version mismatch is directly relevant to their current task. ## What the skill does 1. **Detect installed version.** Run `aware --version`. Capture the version string (format: `aware 0.8.1`). 2. **Detect install method.** Determine how `aware` was installed so the update command matches: - `which aware` → look at the resolved path - If path is under a `node_modules` / `npm` / `pnpm` / `yarn` / `bun` global dir → **npm wrapper** (`@aware-aeco/cli`) - If path is `C:\Program Files\AWARE\aware.exe` → **MSI** (Windows) - If path is `/usr/local/bin/aware`, `/opt/aware/...`, `~/.aware/bin/...` → **curl-pipe / PowerShell** installer - Otherwise: ambiguous, ask the user 3. **Fetch latest version.** Try in order: - `npm view @aware-aeco/cli version` (fastest, no auth) - Fallback: `gh release view --repo aware-aeco/aware --json tagName,name,body,publishedAt` 4. **Compare