updatelisted

Outcome to produce: tell the user their installed version, the newest available version, whether they match, and the exact update steps for their install path. Run the mechanical command `python3 "${CLAUDE_PLUGIN_ROOT}/tools/brothermode_cli.py" update` (the packaged console script is `brothermode update`) and read its output; it is a read-only report and issues no command that writes anything itself. A plugin install exports `${CLAUDE_PLUGIN_ROOT}` for skill and command content, so that path resolves on its own; on a clone install, where the variable is unset, run `python3 tools/brothermode_cli.py update` instead, from the BrotherMode root (`~/.claude/skills/brothermode`). If the network refuses, the command says plainly the check could not run; never guess a version yourself. The command already applies the safety rules that matter: it never sends a development copy (a version ending `.dev1`, or anything newer than the newest release) toward a checkout, because that would be a downgrade wearing the word "update"; and it reports "up to date" or "development copy" and stops, with nothing further to do, before ever reaching the steps below. When an update is genuinely available, give the exact steps for the user's own install path: - **Pinned clone** (inside the skill folder): `git fetch --tags`, then `git checkout <the newest tag the command named>`, then `python3 scripts/doctor.py` to confirm the checkout landed clean (its CHECKSUMS.sha256 self-check catches a half-finish