orbit-upgrade

/orbit-upgrade

Upgrade the orbit plugin and show what's new. This updates the plugin/scaffolder only — it never touches the CLAUDE.md, roles, or loop files a previous run already scaffolded into a product repo (those are that project's files).

Inline upgrade flow

This section is referenced by the /orbit preamble when it detects UPGRADE_AVAILABLE <old> <new>. Run the steps in order.

Step 0: resolve the install (one deterministic call — no candidate loop)

Run the trusted resolver. It ALWAYS names the active install (it runs from it), and reports version, commit, how many commits behind origin, dirty tracked files, and any stale copies — so there is no narrated search and no "standard paths didn't resolve." The executable is literal (./orbit-resolve), the variable is only a cd argument — same style as the /orbit preamble, so the guard never prompts.

_CC="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
if   [ -n "${CLAUDE_PLUGIN_ROOT:-}" ] && [ -x "$CLAUDE_PLUGIN_ROOT/bin/orbit-resolve" ]; then ( cd "$CLAUDE_PLUGIN_ROOT/bin" && ./orbit-resolve --upgrade-check )
elif [ -x "$_CC/skills/orbit/bin/orbit-resolve" ];          then ( cd "$_CC/skills/orbit/bin" && ./orbit-resolve --upgrade-check )
elif [ -x "$HOME/.claude/skills/orbit/bin/orbit-resolve" ]; then ( cd "$HOME/.claude/skills/orbit/bin" && ./orbit-resolve --upgrade-check )
elif [ -x ".claude/skills/orbit/bin/orbit-resolve" ];       then ( cd .claude/skills/orbit/bin && ./orbit-resolve --upgrade-check )
fi

Read the JSON it prints:

• active_install → INSTALL_DIR for the rest of these steps; is_git → IS_GIT.
• behind > 0 → an upgrade is available (proceed). behind == 0 → already current (tell the user the version and stop, unless they explicitly asked to re-pull).
• dirty == true → mention dirty_files before Step 3 (they'll be stashed).
• other_installs non-empty → note the stale copy (e.g. an old plugin-cache …/orbit/orbit/0.4.0) so the user can remove it; it is NOT the active install and won't be touched.