chore(deps): bump vendor/spec-kit from a4e25ce to 4a7341a

[dependabot]

Bumps vendor/spec-kit from a4e25ce to 4a7341a.

Commits

• e2d4cfa fix: add JSON error handling to auth config loader (#3836)
• e1617ce fix: use missing_ok=True in extension ZIP cleanup (#3870)
• 0a70e5b feat(presets): let a preset declare a required extension (#4250)
• d4ba753 fix(bundler): reject unsupported catalog payload versions (#4090)
• b5f7708 fix(extensions): install bundled extension updates from the local package (#4...
• d40c48c docs: clarify autonomous PR handling (#4392)
• 3eec154 fix(workflows): reject malformed step config on add (#4087)
• See full diff 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)

[forkrul]

Superseded by #18 — this one cannot be made green.

4a7341a is an untagged mid-stream commit on spec-kit's default branch, and shellcheck + repo integrity enforces the repo's pinning rule directly:

##[error]vendor/spec-kit is at 4a7341a, which is not an upstream tag

So this is red by design rather than by accident, and rebasing won't change it. #18 bumps to v1.0.6 (96c9bd6) instead — the next actual upstream tag after the current v1.0.5 pin — and moves the README vendored-submodules table with it, which the same CI step also checks.

This PR should be closed rather than merged.

---

Generated by Claude Code

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.