upgrade-canarylisted

Invoke ONLY when you suspect Claude Code may have upgraded, when you are about to cut a plugin release, or when the user says "run the upgrade canary", "did the update break the workflows", "re-check the runtime surface", or "what changed in the runtime". Re-verify both runtimes the toolkit depends on: the interactive `claude` binary and the SDK-bundled one. Run the full matrix only when versions changed since the last pass, when forced, or when the last verdict failed. Maintainer tool only; requires this repo's `toolkit/` tree plus local Claude Code auth.
home-dev-lab/workflow-toolbox · ★ 1 · AI & Automation · score 67

Install: claude install-skill home-dev-lab/workflow-toolbox

# Upgrade canary — re-verify the runtime after a Claude Code upgrade Claude Code's Workflow tool is a **research preview**: parts of the surface the `@workflow-toolbox` toolkit relies on (the 512 KB script cap, the "`meta` must be the first statement" rule, the bundled-artifact launch path) are locally-verified, not publicly contracted, and can drift on an upgrade. This canary re-checks that surface, on **both runtimes you actually use**, so a breakage — or a behavior change worth adopting — is surfaced here, deliberately. It is **version-triggered, not scheduled**. Claude Code updates almost daily; the canary first asks "did the runtime change since it last passed?" and only does the expensive work when the answer is yes, when you pass `--force` — or when the last recorded verdict is a FAIL, which forces a re-run until green even with no version change (a real regression is never silently suppressed by an unchanged version). > **Maintainer tool.** Every command below runs from this repo's `toolkit/` > directory and drives the real runtime via the Agent SDK under your local Claude > Code subscription (the SDK reuses `~/.claude` credentials — no API key). The > canary harness lives in `@workflow-toolbox/smoke`, a **private** workspace > package that is not published to npm — so unlike `workflow-toolbox scaffold/build/check/ > debug/report`, this skill is **not expected to run from a consumer project**. > It is not runnable from an end-user plugin install either, which ships