chore(release): version packages

[openspec-release-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@fission-ai/openspec@1.14.1

Patch Changes

• #2047 7358306 Thanks @clay-good! - ### Bug Fixes

  • Apply no longer calls a change ready to archive too early — When every tracked task is checked, openspec instructions apply now says the tracked tasks are complete and asks you to review or verify the change before archiving. The task guidance keeps steps that can only happen after archive in an optional ## Workflow follow-up section of plain bullets, so they no longer block task completion.
  • Accurate archive cleanup errors — When a change is archived but cleaning up a capability retirement fails, the error now says the change was archived and cleanup did not complete, instead of claiming every backup was kept. --json reports the new code archive_retirement_cleanup_failed instead of the generic archive_error.

• #2025 bfa670e Thanks @TabishB! - The CLI starts faster: each command now loads its implementation only when it runs. openspec --version and --help load 24 modules instead of 485, and commands such as config list, store list and doctor load only what they use, which matters most where Node loads modules slowly, such as Windows. Output, help text, shell completions, exit codes and telemetry are unchanged.

• #2020 760584b Thanks @clay-good! - A requirement description over 500 characters is now a warning instead of an informational hint, so openspec validate --strict fails on it and CI can enforce the limit. The check also covers ADDED requirements in a change, so openspec validate <change> --strict catches a new overlong requirement before archive. Normal validation and archive are unchanged: they still pass when this is the only finding. The specs instruction now explains how to split an existing long requirement without losing its scenarios.

• #2037 852a073 Thanks @vyhuholl! - The specs instruction now tells the agent to write each capability's spec file as soon as it has drafted it, announcing each one first, instead of planning all of them before writing any. A change with many capabilities no longer sits silent until every file is planned, and an interrupted run keeps the files it already wrote. Because specs reads done once any spec file exists, /opsx:continue now checks for capabilities in the proposal that still have no spec file and writes those before moving on.

• #2028 43d23cc Thanks @drakeo338! - The verify workflow now finds a change's spec and design artifacts by their output path (specs/ and design.md) instead of the hardcoded artifact ids specs and design, so it works with custom schemas whose artifacts use other ids.

• #2031 2500d6d Thanks @TabishB! - openspec view no longer lists or counts archived changes. In projects with many archived changes, the list pushed active work off the screen. The dashboard shows current work again, and openspec list --archived still shows archived changes on request.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: Fission-AI/OpenSpec/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: a84c6b4e-84dd-4036-918f-d2487f51ddd9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openspec-cloud]

No PR-relevant drift confirmed.

AI-generated · A citation proves the line exists, not that it makes the case — verify before acting.
Checked the 0 requirements selected for this PR at 1dc4e93 (255 total).
This is not a full-repository clean result; see the check for coverage and any broader findings.
View results · Click Refresh, then Scan again in the check. Or comment /openspec-cloud.