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.11.0

Minor Changes

• #1301 a7353ae Thanks @m-tanner! - Add openspec status --all, which reports every active change in one process instead of one CLI spawn per change. --all --json emits a single { "changes": [ <status>, ... ], "root" } envelope sorted by change name; a change that fails to load contributes { "changeName", "status": [diagnostic] } in place rather than aborting the sweep. A partial failure exits 1 in both text and JSON modes while preserving the complete JSON envelope. Mutually exclusive with --change.

• #980 dd7cea3 Thanks @bsmedberg-xometry! - show: add --diff, which renders each delta requirement against the requirement it replaces in the main spec instead of reprinting the whole block. A MODIFIED requirement has to carry every scenario it keeps, so reviewers could not see what a change actually altered without diffing files by hand. openspec show <change> --diff now prints a colorized unified diff per requirement (additions green, removals red), the full text of ADDED requirements, the authored Reason/Migration text of REMOVED ones, and FROM/TO for RENAMED ones; a requirement that is renamed and modified in the same delta is diffed against its old name. --json --diff keeps the existing payload shape and adds each applicable diff and warning field to MODIFIED deltas only. Main specs resolve against the same root as the change, so --store <id> diffs against that store. Without --diff, openspec show <change> prints exactly what it printed before.

Patch Changes

• #830 109f81f Thanks @alfred-openspec! - Write Antigravity skills and workflows to .agents/, arbitrate its shared skill tree with other tools, and safely migrate an existing .agent/ install.

• #1712 04b37ac Thanks @Marzx13! - archive: preserve a requirement's original position when renaming it instead of moving the renamed block to the end of the spec.

• #1716 7010e26 Thanks @aymanxdev! - explore: require explicit, scope-bound confirmation before the skill uses any command or tool that can create, edit, move, or delete a file. The explore skill's guardrails let "if the user asks" cover answers to its own clarifying questions, so an agent could treat a design discussion as a go-ahead and start creating schemas or editing openspec/config.yaml uninvited. The skill and the /opsx:explore command now instruct the agent to name the proposed artifacts or files, ask a direct yes/no question, and wait for confirmation in a separate message before writing. Read-only commands and tools remain available without confirmation, and expanding the confirmed scope requires another confirmation.

• #1199 ab81a4b Thanks @leo-ar! - Improve Fish completions so command, subcommand, flag, and indexed positional completions no longer fall back to filesystem suggestions unless the target is a real path.

• #1010 e5e350d Thanks @Dansyuqri! - Draw explore-mode diagrams with plain ASCII. The worked examples in the explore skill and /opsx:explore command used Unicode box-drawing, arrow, and marker glyphs, whose display width varies across terminals, fonts, and locales. Agents copied the style, causing padded boxes and aligned tables to drift.

• 2fa679f Thanks @ryandemelo! - Make schema init --default validate and stage config changes before installing a schema, and roll back both files if either install fails. The staging and backup directories it creates are excluded from schema discovery, so they are never offered as real schemas.

• #1671 126c5d6 Thanks @kitimark! - openspec validate now reports a ## Purpose that is still the placeholder archive writes for a new capability, instead of passing it. The placeholder is longer than the 50-character brevity floor, so until now the one check meant to catch a Purpose nobody wrote was satisfied by the exact text saying nobody wrote one — a spec whose Purpose read Does stuff. failed --strict while a spec whose Purpose said nothing at all passed. A capability could carry the placeholder indefinitely while every command reported success.

  It is a warning, so a project that already has placeholders on disk keeps validating by default and only --strict fails. The message says to edit the main spec directly, since a ## Purpose in a delta is read only when the capability is created and cannot replace an existing one.

  Detection is narrow. The placeholder archive generates is recognised through the same definition that writes it, wherever it appears in the Purpose. Otherwise only a TBD or TODO opening the Purpose counts, so The retry budget is TBD pending benchmarks is still a valid Purpose and a word like TBDs is not a marker. Fenced code inside the Purpose is quoted material rather than the Purpose speaking, so a spec that documents the placeholder keeps passing. An empty Purpose is unchanged, and a Purpose reported as a placeholder is no longer also reported as too brief, so a bare TBD yields one finding rather than two.

  openspec archive is unaffected: it validates rebuilt specs without --strict, so a spec archive writes still passes the validation it would have passed before, and the text archive writes is unchanged.

[openspec-cloud]

Nothing to compare — no requirement applies to this change.

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 7fd49fc (255 total).
View results · Click Refresh, then Scan again in the check. Or comment /openspec-cloud.