fix: allow uv install outside venv

[agustif]

Summary

• add --install-target {prime, project, system} to prime env install and prime eval (default: prime)
• manage a Prime venv at ~/.prime/venvs/default, or a project .venv, or use uv pip install --system
• ensure install, environment checks, and uv run all use the same uv context

Rationale

uv pip install requires a target environment. Defaulting to a managed venv prevents accidental system installs while keeping quick‑start smooth; users can opt into project or system installs explicitly.

Fixes PrimeIntellect-ai/prime-environments#455

Notes

• --project lets users point to a specific project root for the .venv target

[cursor]

Uninstall command ignores install-target and project options

The uninstall command adds install_target and project parameters (lines 1775-1787), but these are never used in the function body. The uninstall logic (lines 1809-1830) always runs uv pip uninstall in the current environment without considering the target. This means packages installed with --install-target prime or --install-target project cannot be properly uninstalled because the uninstall command will attempt to remove from the wrong environment.

Additional Locations (1)

• packages/prime/src/prime_cli/commands/env.py#L1808-L1830

 

[cursor]

Missing exception handling for install context resolution in run_eval

The run_eval function calls _resolve_uv_install_context without a try/except block, unlike the install command which catches ValueError and displays a friendly error message. When install_target is "project" but no pyproject.toml or uv.toml is found in the directory tree, _resolve_uv_install_context raises a ValueError that would propagate as an uncaught exception with an ugly stack trace, rather than the clean CLI error shown in install.