docs(node): document install tool options

[risu729]

Sorry for the noise. They're not supported as tool opts.

Summary

• document Node install settings that can be set as tool options
• show precedence of Node tool options over node.* settings for a single tool request

Verification

• mise x prettier -- prettier --check docs/lang/node.md
• git diff --check

Companion docs for #9991.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 21013439-e107-45c5-aeca-1437a7aa23e9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This documentation-only PR adds a new "Node install options" section to docs/lang/node.md, listing 10 node settings (compile, mirror_url, flavor, cflags, configure_opts, make, make_opts, make_install_opts, ninja, concurrency) that are claimed to be usable as inline tool options in [tools].

• A reference table maps each tool option to its equivalent node.* global setting, and a TOML snippet shows the expected usage (node = { version = \"22\", compile = true, ... }).
• The section notes that tool options take precedence over node.* settings for a single tool request, but the backing implementation lives in companion PR fix(node): include source build options in lock identity #9991 which has not yet been merged into main.

Confidence Score: 3/5

The docs PR is safe as standalone text, but if merged before #9991 it advertises a feature that has no backing code in node.rs — users following the example will see their options silently ignored.

The node plugin's install_version_() only consults Settings::get() (global config) and BuildOpts::new() has no path that reads per-tool overrides from the tool version's options map. All ten documented options would be no-ops if a user follows the example in this PR today, making the documentation actively misleading until #9991 lands.

docs/lang/node.md — the new section should only be merged after src/plugins/core/node.rs gains the per-tool override wiring from #9991.

Important Files Changed

Filename	Overview
docs/lang/node.md	Adds a "Node install options" table documenting 10 settings that can be used as per-tool inline options, plus a TOML usage example. The documented feature is not yet implemented in node.rs — it depends on companion PR #9991.

_{Reviews (1): Last reviewed commit: "docs(node): document install tool option..." | Re-trigger Greptile}

[greptile-apps]

Documented feature not yet implemented in codebase

The node plugin's install_version_() in src/plugins/core/node.rs only calls Settings::get() (global settings) and BuildOpts::new() has no code that reads per-tool overrides from tv. None of the ten options listed here (compile, mirror_url, flavor, etc.) will be applied if set as inline tool options — they are silently ignored. This PR is marked as a companion to #9991, which is the implementation that would wire these overrides in. Merging this documentation before #9991 lands means the advertised node = { version = "22", compile = true, ... } syntax will have no effect.