recall-updatelisted

<!-- Generated by scripts/build-codex-plugin.ts; do not edit. --> ## Codex routing This remains check-only and CLI-backed. Never apply an update from an attached Codex session. The canonical workflow below remains authoritative, but equivalent behavior is not assumed across hosts. Check whether Recall has a newer release on GitHub. This skill is read-only — it prints the recommended next step but NEVER runs `update.sh` inline. Running the update while a coding agent session is attached can corrupt in-flight hook invocations (the `recall` binary lives in the same process tree via `bun link`). ## What this does 1. Reads the currently installed version via `recall --version`. 2. Fetches the latest release tag from the GitHub Releases API (`/repos/edheltzel/Recall/releases/latest` — unauthenticated, 60 req/hr per IP). 3. If current == latest: reports "up to date" and exits. 4. If current is behind: prints current, latest, a short excerpt of the release notes, and the exact recipe to run the update manually: ``` cd <path-to-Recall> && ./update.sh ``` ## Why not auto-run? `update.sh` pulls, rebuilds, migrates the DB, and re-registers hooks. Rebuilding the `recall` binary mid-session can leave the running hook scripts in a half-updated state. The safe sequence is: exit the coding agent → `./update.sh` → restart it. ## Rate-limit fallback GitHub's unauthenticated rate limit is 60 requests/hour per IP. If you hit it, the command prints a graceful fallback