Description
While looking through the code on the journey towards a contribution here I noticed there is a focus on using source .venv/bin/activate and similar to activate the environment. I also noticed that some development workflows (for ex. .github/workflows/pyink.yml) do not leverage the uv environment to perform their work and rely instead on pip, creating the potential for confusion or misalignment of implementations.
I suggest moving to uv run syntax (e.g. uv run python, uv run pyink, etc) where possible to help simplify how the development environment may be leveraged. This avoids sometimes confusing patterns when it comes to questions about "which environment am I in?". Further - I recommend consolidating development workflows to leverage the same environment management practices where possible.