fix: use specify-cli@latest consistently

Use @latest to force a fresh PyPI resolve (bypasses uv's cached tool
version), matching the issue acceptance criteria. Source install remains
as fallback when PyPI lags.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

.github/workflows/release.yml

@@ -68,7 +68,7 @@ jobs:
           From [PyPI](https://pypi.org/project/specify-cli/):
 
           \`\`\`bash
-          uv tool install 'specify-cli==${VERSION_NO_V}'
+          uv tool install specify-cli@latest
           specify init my-project
           \`\`\`
 

README.md

@@ -47,7 +47,7 @@ Spec-Driven Development **flips the script** on traditional software development
 Requires **[uv](https://docs.astral.sh/uv/)** ([install uv](https://github.com/github/spec-kit/blob/main/docs/install/uv.md)):
 
 ```bash
-uv tool install specify-cli
+uv tool install specify-cli@latest
 ```
 
 Or install from source using a specific [release](https://github.com/github/spec-kit/releases) tag (useful if the PyPI version is not yet available for a new release):

docs/installation.md

@@ -21,7 +21,7 @@ Install once and use everywhere:
 > The command below requires **[uv](https://docs.astral.sh/uv/)**. If you see `command not found: uv`, [install uv first](./install/uv.md).
 
 ```bash
-uv tool install specify-cli
+uv tool install specify-cli@latest
 ```
 
 Or install from source using a specific [release](https://github.com/github/spec-kit/releases) tag: