Diagnose a Python dependency or virtual environment conflict systematically

Diagnose this Python environment or dependency problem. Do not propose a fix until you've stated a specific hypothesis for the root cause — "try reinstalling" is not a diagnosis.

ERROR
ImportError: cannot import name "BaseSettings" from "pydantic" — happens after upgrading a different package.

ENVIRONMENT
Windows 11, Python 3.12, venv created with python -m venv .venv

PACKAGE MANAGER IN USE
uv

DIAGNOSTIC PROCESS
1. Identify the failure category first: a version conflict between two packages' requirements, a missing system-level dependency (compiler, system library), a wrong or stale virtual environment being activated, a Python version mismatch (a package with no wheel for this Python version), or a corrupted/partial install. State which one this looks like and why, citing the specific line in the error output.
2. Ask for exactly the information you're missing to confirm the hypothesis, if anything — pip list output, the package manager's version, which python, or the lockfile — rather than guessing further.
3. Once confirmed, give the fix as ordered, copy-pasteable commands, not a paragraph description. Note which command is destructive (e.g. deleting a virtual environment) before it runs.
4. Give one prevention step specific to this failure category — pinning a version range, adding a lockfile, using a resolver like uv or pip-tools for reproducible installs — not a generic "keep dependencies updated."

CONSTRAINTS
- Don't suggest pip install --upgrade or --force-reinstall as a first move; that can mask the real problem and break other packages pinned lower in the dependency tree.
- If the fix could change behavior elsewhere in the project (a major version bump), say so and ask before assuming it's fine.

OUTPUT FORMAT
Root cause hypothesis, then confirming evidence needed if any, then exact fix commands, then one line on preventing this category next time.