check-updatelisted

# Check Update Owner-only worker that compares local plugin version with upstream releases for: - `produtoramaxvision/maxvision` (this plugin) - `produtoramaxvision/maxvision` (14 ports tracked) - `produtoramaxvision/maxvision` (15 ports tracked) - `produtoramaxvision/maxvision` (23 ports tracked) Gate: runs `gh api user --jq .login` and checks the result against the owner allowlist (currently `produtoramaxvision`). Non-owners get a silent exit 0. Cache: results stored in `~/.claude/cache/maxvision/upstream-drift.json` for 24h. Cache bypass via `--force` flag or `MAXVISION_CHECK_UPDATE_FORCE=1`. ## Usage ```bash set -euo pipefail python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check_update.py" "$@" ``` Flags: - `--force` — bypass 24h cache, re-fetch every upstream - `--json` — print full drift JSON to stdout instead of human banner ## Invocation paths 1. **Slash command** — `/maxvision:check-update` (this skill via slash) 2. **Monitor** — `on-skill-invoke:check-update` (background drift detection) 3. **SessionStart hook** — opportunistic check at startup (same script, silent for non-owners) ## Why owner-gated The check fetches GitHub release info for 4 repos on each invocation (1 of which is private to the owner's plan workflow). Running this on every user's machine would: 1. Burn their personal GitHub API rate-limit on data they can't act on 2. Surface latest release tags for ports they didn't install 3. Spam non-owner users with banners they can't action By gating on `