[dependabot]

Bumps vendor/spec-kit from 4ca46a0 to 99e047e.

Upgrade guide

Sourced from vendor/spec-kit's upgrade guide.

Upgrade Guide

You have Spec Kit installed and want to upgrade to the latest version to get new features, bug fixes, or updated slash commands. This guide covers both upgrading the CLI tool and updating your project files.

---

Quick Reference

What to Upgrade	Command	When to Use
CLI Tool (recommended)	specify self upgrade	Latest stable release, in place. Auto-detects whether you installed via uv tool or pipx.
CLI Tool — pin a version	specify self upgrade --tag vX.Y.Z[suffix]	Upgrade to a specific release tag instead of the latest stable. Suffixes are limited to dev, alpha/beta/rc, and/or build metadata forms.
CLI Tool — manual fallback	uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git@vX.Y.Z	When specify self upgrade isn't available (older installs) or when you want explicit control.
CLI Tool — manual fallback (pipx)	pipx install --force git+https://github.com/github/spec-kit.git@vX.Y.Z	Same as above, for pipx installs.
Project Files	Run specify integration upgrade <key>, then specify extension update	Refresh installed integration files and extensions in your project
Both	Run CLI upgrade, then project update	Recommended for major version updates

---

Part 1: Upgrade the CLI Tool

The CLI tool (specify) is separate from your project files. Upgrade it to get the latest features and bug fixes.

If you installed from PyPI and want to keep that install route, follow the PyPI upgrade instructions. Repeating uv tool install specify-cli does not upgrade an existing installation.

Recommended: specify self upgrade

The CLI ships with two self-management commands that handle the common case automatically:

# Check whether a newer release is available (read-only — does not modify anything)
specify self check
Preview what would run, without actually upgrading
specify self upgrade --dry-run
Upgrade in place to the latest stable release (auto-detects uv tool vs pipx install)
specify self upgrade
Or pin a specific release tag (replace vX.Y.Z[suffix] with the tag you want)
specify self upgrade --tag vX.Y.Z[suffix]

Bare specify self upgrade executes immediately, matching the no-prompt behavior of commands like pip install -U and npm update. The CLI classifies your runtime into one of: uv tool, pipx, uvx (ephemeral), source checkout, or unsupported. Only uv tool and pipx are upgraded automatically; for uv tool installs, it runs uv tool install specify-cli --force --from <git ref> under the hood so pinned release tags work. The other paths print path-specific guidance and exit 0 without touching anything.

Pinned tags must start with vMAJOR.MINOR.PATCH. Optional suffixes are limited to dev, alpha/beta/rc, and/or build metadata forms such as v1.0.0-rc1, v0.8.0.dev0, v0.8.0+build.42, or the combination v1.0.0-rc1+build.42; branch names, hash refs, latest, and bare versions without v are rejected.

Set SPECIFY_UPGRADE_TIMEOUT_SECS to cap how long the installer subprocess may run (default: no timeout — interrupt with Ctrl+C if needed). If that internal timeout fires, specify self upgrade exits 124 and reports that it timed out while waiting for the installer subprocess, including the configured timeout and manual retry command. A real installer exit code 124 is propagated with Upgrade failed. Installer exit code: 124., so scripts should treat exit 124 as ambiguous and inspect the message when they need to distinguish the two cases.

... (truncated)

Commits

• 99e047e fix(integrations): refresh manifest hashes after preset registration on switc...
• dcb0de7 chore: release 1.2.5, begin 1.2.6.dev0 development (#5167)
• 521498d docs: publish extension development guide on docs site (#5166)
• 3f4c576 docs: publish extensions overview and navigation (#5165)
• f070a70 fix(extensions): load top-level defaults from extension.yml (#5164)
• b0edc22 fix(bundles): reject integration mappings without an id (#5161)
• 7f45114 docs: publish extension publishing guide on the docs site (#5163)
• 749a177 feat(workflows): expose installed workflow listing through MCP (#5115)
• a83d4cf fix(extensions): reject hook commands that are not strings (#5146)
• 246b9d0 fix(workflows): accept equivalent version spellings in archive updates (#5155)
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)