upgrade

Upgrade components: $ARGUMENTS

Core references. A citation of the form workflows-core:<name> names a shared reference in the workflows-core plugin. Load it with Skill(skill: "workflows-core:reference", args: "<name>") — never by path: ${CLAUDE_PLUGIN_ROOT} resolves to this plugin, which does not carry it.

Strip --no-commit first, before parsing any component token: an unstripped flag is read as a component name and the run fails resolving it. When present, steps 6.5 and 7.5 are both skipped and the changes are left in the working tree. It is the one opt-out from a commit that is otherwise prompt-free (${CLAUDE_PLUGIN_ROOT}/references/code-handoff.md §1 rule 5) — typed rather than clicked, which is the difference — and a run under it says once what it costs: the work is recoverable only on this machine.

Each token is one of: component:1.2.3 (exact), component:minor (latest patch on current minor), component:latest (latest stable), component:lts (latest LTS), or bare component (latest compatible with everything else).

component can be a library, framework, language runtime, build tool, or path like .github/workflows.

Each component is committed on its own as soon as its gates pass — see Phase 2's step 6.5 and step 7.5 (${CLAUDE_PLUGIN_ROOT}/references/code-handoff.md); the branch is pushed once for the batch where §2.4's consent choice, an origin and §2.5's push itself all allowed it, and a pull request opened where §2.4's consent choice, §2.8's base-branch ladder and §2.6's gh capability probe allowed one as well — §3.1's rows rather than any list written out here are the authority on which line the run emitted. §2.4 is named in both halves rather than carried forward from the first, because its second option ("Push the branch only — no pull request") allows the push and refuses the pull request: a clause that let the push's own §2.4 term stand for the pull request's would assert one in a state §3.1 has its own row for. The commit is prompt-free; only the push and the pull request sit behind a consent choice, asked once for the batch. --no-commit skips both steps.

Phase 0 — Specs-repo preflight

Invoke Skill(skill: "workflows-core:reference", args: "specs-repo-git specs-preflight") and execute its specs-preflight entry point (§3) inline: flush any leftover session artifacts from an earlier run, retry an artifact commit that failed to push, and settle the branch. This runs against $SPECS_PATH only — git -C "$SPECS_PATH", never a cd, so the code repo this run is about to upgrade is untouched (§1 rule 1). Prompt-free and silent when the specs repo is clean and on its default branch. If a guard fires, emit its §5 notice; if it returns specs_git: blocked (§3.3 G0), carry that flag for the whole run — the terminal commit-artifacts step skips on it.