Context: End users can only install the companion spec-kit extension with specify extension add companion once it's published to a spec-kit catalog. Today it's local --dev only (speckit-extension/docs/install.md still marks the catalog path "future"). Publishing is what makes a real, resolvable install command exist — which the VS Code launch prep then wraps in one-click UI.
Goal: the spec-kit extension is published to the catalog so a fresh user can install it with a single documented command.
Gating — do NOT publish until the extension is feature-ready. Hold until the in-flight spec-kit-side work has landed (e.g. step-05 complexity fast-path, #233 capture hardening) so we don't publish a half-baked surface. This ticket is the deliberate "now it's ready → publish" gate, not an immediate action.
Acceptance criteria:
- The spec-kit extension is published to the catalog and
specify extension add companion resolves for a fresh user (no local --dev path required).
- The install doc's "catalog" path becomes the current, supported install instruction.
- Re-running the install on an already-installed setup does not clobber user assets (non-destructive update path verified).
Technical details
- Release flow:
/publish-speckit-ext → speckit-ext-v* tag → GitHub release → spec-kit catalog (speckit-extension/docs/publishing.md). Prefixed tag is mandatory — a bare v* triggers the VS Code Marketplace release instead.
- Confirm the catalog-form add resolves the
companion-standard carrier preset from the published bundle, not a local-only path (the known reconciler/catalog seam — catalog add must actually install the preset, not no-op).
- Bump
speckit-extension/extension.yml version + its CHANGELOG as part of the publish (its own versioning, separate from the VS Code v*).
- Unblocks the one-click install buttons in the VS Code launch-prep ticket.
Context: End users can only install the companion spec-kit extension with
specify extension add companiononce it's published to a spec-kit catalog. Today it's local--devonly (speckit-extension/docs/install.mdstill marks the catalog path "future"). Publishing is what makes a real, resolvable install command exist — which the VS Code launch prep then wraps in one-click UI.Goal: the spec-kit extension is published to the catalog so a fresh user can install it with a single documented command.
Gating — do NOT publish until the extension is feature-ready. Hold until the in-flight spec-kit-side work has landed (e.g. step-05 complexity fast-path, #233 capture hardening) so we don't publish a half-baked surface. This ticket is the deliberate "now it's ready → publish" gate, not an immediate action.
Acceptance criteria:
specify extension add companionresolves for a fresh user (no local--devpath required).Technical details
/publish-speckit-ext→speckit-ext-v*tag → GitHub release → spec-kit catalog (speckit-extension/docs/publishing.md). Prefixed tag is mandatory — a barev*triggers the VS Code Marketplace release instead.companion-standardcarrier preset from the published bundle, not a local-only path (the known reconciler/catalog seam — catalog add must actually install the preset, not no-op).speckit-extension/extension.ymlversion+ its CHANGELOG as part of the publish (its own versioning, separate from the VS Codev*).