docs: add repo-specific tool_versions to preview environments

[roomote]

Documents the tool_versions field on repository configuration for preview environments.

Changes

• Replaced the simple "Repository Format" heading with a full Repository Configuration Fields table covering repository, branch, tool_versions, and commands
• Expanded the Automatic Tool Installation section into two options:
  • Option 1: tool_versions in the environment config (generates .tool-versions at runtime, excluded from git, takes priority over repo file)
  • Option 2: existing .tool-versions file in the repository (existing behavior)
• Added a tip callout explaining when to use each approach
• Updated the Complete Example to demonstrate tool_versions and branch on repository entries

---

View task on Roo Code Cloud

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
roo-code-docs	Ready	Preview, Comment	Feb 13, 2026 5:03am

[roomote]

Rooviewer   See task

All previously flagged issues have been resolved. No new issues found.

• Inconsistent tool naming: Option 1 examples use node while Option 2 .tool-versions example uses nodejs -- could confuse readers about which name to use

Previous reviews

• ee6acc9: Review #1
• ee6acc9: Review #2

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote]

Rooviewer   See task

One minor documentation issue found (already flagged by the previous review).

• Inconsistent tool naming: Option 1 examples use node while Option 2 .tool-versions example uses nodejs -- could confuse readers about which name to use

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}