chore(deps): Bump @fission-ai/openspec from 1.9.0 to 1.10.0 in the workflow-tooling group

[dependabot]

Bumps the workflow-tooling group with 1 update: @fission-ai/openspec.

Updates @fission-ai/openspec from 1.9.0 to 1.10.0

Release notes

Sourced from @​fission-ai/openspec's releases.

v1.10.0 - Zed support, quieter installs

What's New in v1.10.0

Zed joins the supported tools, init speaks your language, and installing OpenSpec no longer trips npm's alarm.

New

• Zed Agent - openspec init --tools zed installs the workflow skills into .agents/skills/, where Zed's built-in Agent finds them. Skills-only, so they're invoked as /openspec-propose. Requires Zed v1.4.2 or newer.
• Non-English artifacts - openspec init --language <language> sets the language for generated artifacts without hand-editing config.yaml. OpenSpec headings and SHALL/MUST stay in English, so your specs still validate.

Improved

• Installing - the published package now declares no install scripts at all, so npm install -g @fission-ai/openspec no longer emits the allow-scripts warning that read like a packaging fault (and whose suggested fix, npm approve-scripts, never worked for a global install anyway). The shell-completions tip now comes from the CLI itself: once, on stderr, and only when there's a human there to read it.
• Task plans - generated tasks now have to say how you'd know they're done, whether that's a test, a command, an observable result, or a delivered artifact. "Implement the thing" no longer passes for a plan.
• Prompts - the multi-select picker now shows the full key help from the prompt library, so navigation, select-all and invert are discoverable instead of folklore.

Fixed

• Feedback - openspec feedback used your entire report as the issue title and left the body with nothing but metadata. Reports now keep their text, and titles stay a readable length.
• Archive - retiring a capability could dead-end on Spec must have at least one requirement with no guidance at all, when the spec also held content the merge couldn't account for. The abort now names exactly what's in the way.
• Stores - the specs instruction read main specs from a path relative to your working directory. Under a store that missed the spec entirely, or, worse, quietly returned a different capability that happened to share the name.
• Profiles - a custom profile could select archive without sync, leaving the archive workflow calling a workflow that was never installed.
• OpenCode - /opsx-propose add-auth dropped add-auth before the workflow ever saw it.
• Schemas with no specs artifact - changes created under one failed validation immediately, demanding a delta that schema could never produce.
• Output hygiene - the first-run telemetry notice went to stdout, so openspec spec show auth > auth.md wrote the notice into the file ahead of the spec. It goes to stderr now.
• openspec update - stopped advising Claude Code, Codex and other CLI tools to restart an IDE they don't have.

New Contributors

• @​ryandemelo made their first contribution in Fission-AI/OpenSpec#1666

Full Changelog: Fission-AI/OpenSpec@v1.9.0...v1.10.0

Changelog

Sourced from @​fission-ai/openspec's changelog.

1.10.0

Minor Changes

• #1685 c747ed1 Thanks @​clay-good! - Add openspec init --language <language> to configure the language used for artifacts in new projects.

Patch Changes

• #1704 7276c6c Thanks @​clay-good! - Drop the npm postinstall script. Its only job was printing a one-line tip about opt-in shell completions, but shipping any install script made npm install -g @fission-ai/openspec emit an allow-scripts warning that reads as a packaging fault (and npm approve-scripts then fails with ENOMATCH on a global install, since it looks in the local project). The tip now prints from the CLI on its first run — to stderr, in an interactive terminal, once, and not at all if you already have completions installed — and the published package declares no preinstall/install/postinstall script, so a registry install runs no OpenSpec code. Suppress the tip with OPENSPEC_NO_COMPLETIONS=1.

• #1656 a72a74d Thanks @​clay-good! - ### Bug Fixes

  • openspec update now suggests restarting an IDE only when it updates an IDE-resident tool. CLI tools such as Claude Code, Codex, and Gemini CLI no longer show an unnecessary restart hint.

• #1703 9643888 Thanks @​clay-good! - Point the spec-driven specs instruction's main-spec read and edit at the store-aware root. It named openspec/specs/<capability-path>/spec.md, a path relative to the current directory, for both step 1 of the MODIFIED workflow ("locate the existing requirement") and the edit that fixes a leftover TBD Purpose. When the change lives in a store — whether selected with --store, a project store: pointer, or a global default store — the main spec is under the store root, so that read missed it, or silently returned a different capability when a local one happened to share the name, and the MODIFIED block was then copied from the wrong requirement. Both operations now use <planningHome.root>/openspec/specs/..., the root already returned by openspec instructions ... --json and the same convention the sync and archive workflows use. Fixes #1702.

• #1699 18688c8 Thanks @​clay-good! - archive: tell the author how to retire a capability when the emptied spec also holds content the merge cannot account for. That combination printed only "Spec must have at least one requirement" and no guidance at all; the abort now names the blocking lines and reports a retire_capabilities marker that is present but cannot be honored. Authored content quoted in those messages - the blocking lines, and the marker's own reason, which openspec validate prints too - is stripped of control characters and bounded in length before it reaches the terminal.

• #1660 7da3f34 Thanks @​clay-good! - Require generated tasks to state how their completion can be verified.

Commits

• 1ebddd1 Version Packages (#1705)
• 7da3f34 fix(tasks): include verification in generated plans (#1660)
• 7276c6c fix(packaging): print the completions tip from the CLI, not a postinstall scr...
• 9643888 fix(schema): resolve main-spec reads against the store-aware root (#1703)
• 18688c8 fix(archive): never dead-end a capability retirement (#1699)
• c747ed1 feat(init): add language option (#1685)
• 15e50d6 fix(opencode): pass command arguments to workflows (#1664)
• cf06d45 fix(profiles): include sync with archive workflows (#1663)
• f3aa167 feat(tools): add Zed Agent support (#1659)
• a72a74d fix(update): only suggest IDE restarts when needed (#1656)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions