env-manager-selection

Resolve runtime version mismatch build failures by checking project version cue files like .nvmrc or .python-version, then activating the declared environment manager with the correct command to switch the active runtime and fix the compilation errors.

The best way to pick the right environment manager is by mapping mandatory project files like .sdkmanrc, .tool-versions, or .ruby-version to their manager-specific activation commands, ensuring the correct runtime is selected before building or testing.

Use .tool-versions and .nvmrc files to switch your local language runtime by detecting the cues and running the corresponding manager commands, such as invoking asdf, sdkman, or fnm/nvm to align your active environment with the project's declared version.

Environment manager detection respects user constraints by avoiding file inspection if requested, and it asks a clarifying question when the appropriate runtime manager or activation workflow is uncertain.

Java or Go builds fail with unsupported class file or runtime errors when the active language runtime version does not match the project's declared version, requiring you to switch managers using cues like .sdkmanrc to align the environment.