v2026.5.9 — Workspace Deploy + Command Surface Parity

Tag: `v2026.5.9` · Released: 2026-05-18 · npm: `npm install -g [email protected]`

This patch release fixes the workspace-aware `aiwg use all` deployment path introduced in the 2026.5 line and restores command-surface compatibility for operator workflows after the skills-first pivot.

What's fixed and improved

`aiwg use all` now computes the workspace-aware framework/addon/extension plan once, then deploys each selected source directory directly. This prevents the full framework post-deploy flow from running repeatedly for every selected framework, which previously produced repeated capability-index builds, repeated session-reload messages, and duplicate hook backup lines.

The legacy full deployment remains available:

aiwg use all --no-workspace-signals

Operator workflow skills are now mirrored into provider command surfaces where providers support commands, and into the closest reasonable provider location where they do not. This keeps workflows such as `aiwg-setup-project`, `aiwg-update-claude`, and `aiwg-update-agents-md` locatable through command/slash-command patterns while skills remain the canonical source artifact.

Also included

• `aiwg use --workspace-signals --dry-run` now reports the workspace-aware subset as the behavior that `aiwg use all` will deploy by default.
• Full deployment coverage tests now exercise the legacy path explicitly with `--no-workspace-signals`.
• Doctor/listing guidance now points users toward workspace-aware deployment when deployed skill counts exceed provider listing budgets.
• OpenCode and Warp provider definitions now declare command directories for mirrored operator workflows.
• Deployment completeness coverage now asserts command mirrors for Codex, OpenCode, Copilot, Warp, and Windsurf.

User impact

• `aiwg use all` no longer appears to run the same deployment repeatedly in workspace-aware mode.
• `aiwg-setup-project` remains discoverable as a skill and is also copied to command surfaces for providers that expose commands.
• Providers continue receiving all relevant assets; when a provider does not explicitly support an artifact class, AIWG places the asset in the closest reasonable location.

Verification

Release-readiness checks for this line:

npm run check:versions
npm run typecheck
npm run build:cli
npx vitest run --config config/vitest.config.js test/integration/deployment-completeness.test.ts
npx vitest run --config config/vitest.config.js test/integration/use-all-deployment.test.ts
npm test