updatelisted

# Update Orchestray The user wants to check for or apply updates to their Orchestray installation. ## Protocol 1. **Parse arguments**: `$ARGUMENTS` - If `--check` is present: only check for updates, do not install. 2. **Detect installations**: Look for VERSION files at both candidate install paths. - Check `~/.claude/orchestray/VERSION` (global install). - Check `.claude/orchestray/VERSION` in the current working directory (local install). - Build a list `{installs}` of every install that exists, recording for each: `{scope}` (`--global` or `--local`), `{path}` (the VERSION file's parent directory), and `{current}` (the trimmed VERSION contents). - If `{installs}` is empty: report "Orchestray installation not found. Install with `npx orchestray --global` or `npx orchestray --local`." and stop. 3. **Check for updates**: Run `npm view orchestray version` to get `{latest}`. - If the command fails: report "Could not check npm registry. Check your internet connection." and stop. - For each install in `{installs}`, compare its `{current}` to `{latest}`. Build `{stale}` = the installs whose `{current}` differs from `{latest}`. - If `{stale}` is empty: report "Orchestray is up to date (v{latest}) — checked: <list of scopes>." and stop. - Otherwise: report each stale install on its own line — "Update available [<scope>]: v{current} -> v{latest}". - If `--check` flag was provided: stop here. 4. **Perform updates** — update EVERY stale install, not ju