Fix #4345: Extension version staleness

[ranka23]

Bumps agent-context and git versions to 1.1.0. Manually tested. AI-assisted.

[KSchlobohm]

Maintainer note: We’re carrying this PR forward as a narrow version-metadata correction for future installs of the bundled agent-context and git extensions. Existing installations require the known workaround after upgrading to a Spec Kit release containing these versions.

Known workaround

specify extension add agent-context --force
specify extension add git --force

[Copilot]

Pull request overview

Bumps bundled extension versions so installed projects can detect updates.

Changes:

• Updates agent-context and git manifests to v1.1.0.
• Synchronizes catalog versions.

Show a summary per file

File	Description
extensions/git/extension.yml	Bumps git extension version.
extensions/agent-context/extension.yml	Bumps agent-context version.
extensions/catalog.json	Updates bundled catalog entries.

Review details

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

• Files reviewed: 3/3 changed files
• Comments generated: 2
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 1
• Review effort level: Balanced

[mnriem]

To make this mergeable as a complete fix for #4345, the following still needs to be addressed:

1. Update the exact agent-context pins from 1.0.0 to 1.1.0 in the four examples/bundles/*/bundle.yml manifests and the fixtures in tests/integration/test_bundler_{init_install,local_install}.py. These are examples/tests rather than a production catalog bundle, but the bundler enforces their pins against the embedded manifest.
2. Fix the bundled-extension update path. extension update currently discovers 1.1.0 from the live catalog and then calls download_extension(), which rejects bundled entries without a download_url. For a bundled extension, the available version should come from the CLI's embedded extension.yml, and the update should reinstall that embedded directory atomically with force=True, preserving the existing config and rollback behavior. This also prevents an older CLI embedding 1.0.0 from offering a live-catalog 1.1.0 update it cannot provide.
3. Add regression coverage for updating an installed older bundled extension from a newer embedded copy, and for catalog/manifest version parity. The proposed CI guard requiring a manifest version bump whenever shipped extension content changes should also be included or tracked explicitly as follow-up work.

The extension version remains independent from the CLI version; this only requires the catalog, embedded manifest, and exact example/test pins to agree on the extension release being shipped.

Posted on behalf of @mnriem by GitHub Copilot (model: GPT-5.6 Sol).