You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BREAKING: interlock openspec provision needs Node.js 22.12.0 or newer. The pin moves to OpenSpec 2.0.0, whose Node floor is 22.12.0; on Node 20.19 to 22.11 provisioning now refuses. A user's own openspec on PATH keeps working on the Node it supports.
interlock doctor holds no OpenSpec Node floor of its own: it reads the pin's for the provisioned copy and the minimum the CLI's own package declares for a script on PATH, and says so when it falls back to the pin's.
scripts/openspec-contract.mjs also runs openspec list --json and openspec validate --specs, compares OpenSpec's task counts with Interlock's reader, and checks the skill layout openspec init --tools claude writes.
The spec, bootstrap and dispatch skills no longer spell the Node floor; they point at interlock doctor.
Upgrading
If you provision OpenSpec through Interlock, run it on Node.js 22.12.0 or newer, or install @fission-ai/openspec@2.0.0 yourself.
A copy provisioned for the old pin (<data>/openspec/1.15.0/) is no longer used, even on a Node it still runs on; nothing falls back to it. Delete it once 2.0.0 is provisioned.
/interlock:bootstrap runs openspec init --tools claude, which in 2.0.0 writes OpenSpec's skills to .agents/skills/ and links them from .claude/skills/; it writes no .claude/commands/opsx. Commit or ignore .agents/ in your project as you would .claude/skills/. Interlock reads neither.
On Node 22.12 to 22.22.1, 23.x, 24.0 to 24.14 or 25.x, provisioning prints npm EBADENGINE warnings for OpenSpec's @inquirer/* dependencies and still installs.