scout-update

Scout Update

You are the Scout updater. This command upgrades an existing vault against the current plugin templates without clobbering vault customizations. It runs an 8-stage pipeline (pre-flight → migrations → plugin-owned files, keeping the vault's edits to them → .gitignore merge → cat-4 3-way merge → job lifecycle → version stamp → doctor).

This command is for existing vaults only. If no vault exists, refuse and tell the user to run /scout-setup.

Locating scoutctl — canonical resolver

Every shell block in this command runs in a fresh process, so variables set in one block do not carry into the next. Each block that needs the plugin root must re-resolve it at its top using the canonical resolver snippet below.

Canonical resolver (copy verbatim into every block that needs $NEW_ROOT / $SCOUTCTL):

NEW_ROOT=""
if [ -e "$HOME/scout-plugin/.git" ] && [ -f "$HOME/scout-plugin/.claude-plugin/plugin.json" ]; then
  NEW_ROOT="$HOME/scout-plugin"           # legacy single-repo scout-plugin clone
elif [ -e "$HOME/scout-plugin/.git" ] && [ -f "$HOME/scout-plugin/plugin/.claude-plugin/plugin.json" ]; then
  NEW_ROOT="$HOME/scout-plugin/plugin"    # Raven-Scout/Scout monorepo clone: plugin under plugin/
fi
[ -n "$NEW_ROOT" ] || NEW_ROOT="$(claude plugin list --json 2>/dev/null \
  | python3 -c 'import sys,json;d=json.load(sys.stdin);e=d if isinstance(d,list) else [p for ps in d.get("plugins",{}).values() for p in ps];print(next((p["installPath"] for p in e if p.get("id")=="scout@scout-plugin"),""))' 2>/dev/null)"
[ -n "$NEW_ROOT" ] || NEW_ROOT="$(ls -d "$HOME"/.claude/plugins/cache/scout-plugin/scout/*/ 2>/dev/null | sort -V | tail -1)"
NEW_ROOT="${NEW_ROOT%/}"
[ -n "$NEW_ROOT" ] || { echo "PLUGIN_ROOT_NOT_FOUND"; exit 1; }
SCOUTCTL="$NEW_ROOT/.venv/bin/scoutctl"

This prefers a maintainer git checkout at ~/scout-plugin — a legacy single-repo scout-plugin clone (.claude-plugin/plugin.json at its root) is the plugin root itself; a Raven-Scout/Scout monorepo clone (plugin/.claude-plugin/plugin.json) has its plugin root at ~/scout-plugin/plugin; a .git alone is not enough — then the scout@scout-plugin entry of claude plugin list --json (which has emitted both a flat list and a {"plugins": {...}} map — the snippet accepts either), then the newest version directory in the marketplace cache. It never yields an empty root: if all three miss it prints PLUGIN_ROOT_NOT_FOUND and stops — tell the user the plugin isn't installed and to re-run the installer. Do NOT use ${CLAUDE_PLUGIN_ROOT:-$HOME/scout-plugin} in any block — after Step 0.5 refreshes the plugin, $CLAUDE_PLUGIN_ROOT may still point at the pre-refresh path.