[Bug]: v0.6.1 specify init --here --ai claude fails on Windows - still looks for release assets (spec-kit-template-claude-ps)

[litlmike]

Description

specify init --here --ai claude (and specify init . --ai claude) fails on Windows (PowerShell) with v0.6.1 stable. The CLI still attempts to download a release asset matching the pattern spec-kit-template-claude-ps but no template assets exist on v0.6.0 or v0.6.1 releases.

Steps to Reproduce

1. Install v0.6.1 stable:

   uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git@v0.6.1
   

2. Navigate to an existing project directory
3. Run:

   specify init --here --ai claude
   

Expected Behavior

Project initializes with Claude agent configuration using bundled templates (as described in #2092 — "Templates are no longer separately downloadable").

Actual Behavior

Selected AI assistant: claude
Selected script type: ps
No matching release asset found for claude (expected pattern: spec-kit-template-claude-ps)
────────── Available Assets ──────────
(no assets)
────────── Failure ──────────
Initialization failed: 1

Environment

• specify-cli version: 0.6.1 (from git+https://github.com/github/spec-kit.git@v0.6.1)
• OS: Windows 10 (x64)
• Python: 3.x via uv
• Platform: PowerShell (script type detected as ps)
• Installation method: uv tool install (persistent)

Notes

• Previously on 0.6.2.dev0 (from main), same error. Downgraded to v0.6.1 stable per readme, same result.
• Issue v0.5.0 and v0.4.5 releases missing template assets #2092 (v0.5.0) was closed with the explanation that templates are now bundled, but the init code path for --ai still hits the release asset download logic.
• v0.6.0 and v0.6.1 releases both have "assets": [] — zero release assets attached.
• This appears to be a regression or incomplete migration from release-asset-based templates to bundled templates.

[litlmike]

Update: Found the workaround. The uvx method works, while the persistent uv tool install method does not.

Fails (persistent install):

uv tool install specify-cli --force --from git+https://github.com/github/spec-kit.git@v0.6.1
specify init --here --ai claude
# → "No matching release asset found for claude (expected pattern: spec-kit-template-claude-ps)"

Works (uvx direct run):

uvx --from git+https://github.com/github/spec-kit.git@v0.6.1 specify init --here
# → "Project ready." — full initialization succeeds with Claude auto-detected

Both use the same v0.6.1 tag. The issue appears to be that the persistent uv tool install path doesn't properly bundle/resolve the template assets, while uvx running directly from the git source does.

This matches the workaround reported in #2092 by @damnhandy — the uvx method was the one that worked there too.

The README's "recommended" installation method (uv tool install) is currently broken on Windows for all AI agent templates. Only the uvx method works.