should r_version entry be added to uvr.toml when uvr r pin used? (along with the generate .rversion file)

[B-Nilson]

Not sure if this would make sense, jsut a thought.

Currently when pinning a file called .rversion is created. When "using" an r version (uvr r use <version>), an entry is added to uvr.toml. When we pin, should this toml entry be added as well?

[nbafrank]

Going to keep these two commands independent, per uv's convention:

• uvr r pin <ver> — writes .r-version only. Exact pin, project-local override.
• uvr r use <ver> — writes the constraint into uvr.toml's [project] r_version. Cross-project, in source control.

This mirrors uv python pin (writes .python-version) vs the requires-python field in pyproject.toml. The two are independent levers: the constraint says "any version satisfying this is acceptable for this project," the pin says "right now, use exactly this one."

Workflow when you want both:

uvr r use ">=4.5.0"   # writes uvr.toml constraint, commit this
uvr r pin 4.6.0       # writes .r-version, often gitignored

If we coupled r pin to also rewrite uvr.toml, users who want a pure local override (e.g. testing an R 4.6 build without forcing the whole team onto it) would have to manually undo the toml edit. The current split lets each command stay simple.

Closing as working-as-intended unless this breaks a workflow I'm not seeing — happy to revisit if so.