docs: clarify version checks vs install provenance

Author: Copilot

docs/install/pipx.md

@@ -21,12 +21,16 @@ pipx install git+https://github.com/github/spec-kit.git
 specify version
 ```
 
+`specify version` reports the installed Spec Kit CLI version and runtime details. It is a useful version/runtime check, but it does not prove whether the executable came from a Git source, a PyPI package, or another location. If you need to confirm installation provenance, inspect the package manager's stored install metadata (for example, `pipx list` for `pipx`-managed installs).
+
 ## Upgrade
 
 ```bash
 pipx install --force git+https://github.com/github/spec-kit.git@vX.Y.Z
 ```
 
+If you want to move to the latest release instead of a pinned tag, omit the `@vX.Y.Z` suffix from the install command above.
+
 ## Uninstall
 
 ```bash

docs/installation.md

@@ -81,13 +81,13 @@ specify init <project_name> --integration claude --ignore-agent-tools
 
 ## Verification
 
-After installation, run the following command to confirm the correct version is installed:
+After installation, run the following command to check the installed CLI version and runtime:
 
 ```bash
 specify version
 ```
 
-This helps verify you are running the official Spec Kit build from GitHub, not an unrelated package with the same name.
+This is a version/runtime check. It helps confirm the installed Spec Kit CLI version and environment, but it does not prove the executable came from the official GitHub release source or another install source. If you need to confirm install provenance, inspect the package manager's stored install metadata (for example, `uv tool list` or `pipx list`, depending on how you installed Spec Kit).
 
 **Stay current:** Run `specify self check` periodically to learn whether a newer release is available — it is read-only and never modifies your installation. When you are ready to upgrade, follow the [Upgrade Guide](./upgrade.md).