Problem
When I run uv run specfact upgrade --yes, the CLI detects the installation method as pipx and then surfaces the pipx spaced-home warning:
Installation method detected: pipx⚠️ Found a space in the pipx home path...
That detection is misleading in this invocation path. I am launching the command via uv run, so the upgrade flow should not present pipx as the effective runner context just because the underlying installation happens to live in a pipx-managed environment.
Why this matters
The command finishes successfully, but the output makes the upgrade look unhealthy and suggests a configuration problem that is not actionable for this run mode.
Expected behavior
- Detect the actual upgrade execution context more accurately when invoked through
uv run.
- Avoid showing the pipx-specific spaced-home warning in this case unless it is genuinely relevant to the active upgrade path.
Related issue
Environment
- macOS
uv run specfact upgrade --yes
Problem
When I run
uv run specfact upgrade --yes, the CLI detects the installation method aspipxand then surfaces the pipx spaced-home warning:Installation method detected: pipx⚠️ Found a space in the pipx home path...That detection is misleading in this invocation path. I am launching the command via
uv run, so the upgrade flow should not present pipx as the effective runner context just because the underlying installation happens to live in a pipx-managed environment.Why this matters
The command finishes successfully, but the output makes the upgrade look unhealthy and suggests a configuration problem that is not actionable for this run mode.
Expected behavior
uv run.Related issue
Environment
uv run specfact upgrade --yes