Kimi/Vibe 1.4.0 init generates skills that still reference /opsx commands #1155

Summary

QA for the published @fission-ai/openspec@1.4.0 release found that Kimi CLI and Mistral Vibe initialize as skills-only tools, but the generated setup guidance and skill prose still point users at /opsx:* commands.

This is confusing because no command adapter/files are generated for these tools, and the 1.4.0 docs/release notes describe skill-based invocation for them.

Reproduction

From a clean temp home/prefix:

npm install -g @fission-ai/openspec@1.4.0 --prefix "$PREFIX"
PATH="$PREFIX/bin:$PATH" HOME="$HOME_DIR" OPENSPEC_TELEMETRY=0 openspec init --tools kimi "$PROJECT"
rg -n '/opsx:|/skill:|openspec-' "$PROJECT/.kimi/skills"

Observed init output:

OpenSpec Setup Complete

Created: Kimi CLI
5 skills and 5 commands in .kimi/
Commands skipped for: kimi (no adapter)

Getting started:
  Start your first change: /opsx:propose "your idea"

Observed generated Kimi skill references:

.kimi/skills/openspec-propose/SKILL.md:19:When ready to implement, run /opsx:apply
.kimi/skills/openspec-propose/SKILL.md:94:- Prompt: "Run `/opsx:apply` or ask me to implement to start working on the tasks."
.kimi/skills/openspec-explore/SKILL.md:203:User: /opsx:explore add-auth-system
.kimi/skills/openspec-apply-change/SKILL.md:25:Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).

The same pattern reproduces with Vibe:

PATH="$PREFIX/bin:$PATH" HOME="$HOME_DIR" OPENSPEC_TELEMETRY=0 openspec init --tools vibe "$PROJECT"
rg -n '/opsx:|/skill:|openspec-' "$PROJECT/.vibe/skills"

Observed init output:

Created: Mistral Vibe
5 skills and 5 commands in .vibe/
Commands skipped for: vibe (no adapter)

Getting started:
  Start your first change: /opsx:propose "your idea"

Expected

For adapterless skills-only tools:

• init output should not say 5 commands when commands are skipped
• getting-started guidance should use the correct skill invocation for that tool
• generated skill prose should not tell users to run /opsx:* commands that were not generated

Docs in v1.4.0 say:

• Kimi CLI: skill-based invocations such as /skill:openspec-propose, /skill:openspec-apply-change
• Mistral Vibe: skills in .vibe/skills/openspec-*/SKILL.md, no generated command adapter

QA context

Other 1.4.0 release-note checks passed in the same QA run:

• published npm package installs and reports openspec --version as 1.4.0
• Kimi/Vibe skill directories are created under .kimi/skills/ and .vibe/skills/
• default core profile includes openspec-sync-specs
• case-insensitive requirement headers validate successfully
• delta validation gives the new header-only SHALL/MUST hint
• zsh completion install works for isolated standard zsh and oh-my-zsh homes
• workspace-planning mode is preserved when entering a workspace via a symlink alias