Remote build over non-interactive ssh can't find tools that interactive shells see (environment modules, .bashrc PATH)

Symptom: an app runs a build or setup script on a remote host over ssh host 'bash build.sh'. When you test by hand in an interactive shell, the script finds a tool (via $TOOL_HOME or PATH). From the app, it silently takes the 'tool not installed' branch and skips an optional component.

Cause: non-interactive ssh shells don't run the interactive startup files or module load lines, so variables like TOOL_HOME and the PATH additions made by environment modules (Lmod/TCL modules) or .bashrc are missing. Test harnesses often hide it, because they module load the tool themselves in their ssh command.

Fixes: - Discover tools without relying on the caller's environment: check $TOOL_HOME, then PATH, then known install roots. Also look next to a sibling tool you already found: vendors often install suites side by side under one root with matching version directories, so prefer the same version. - Log what was found (path and version), and say loudly when an optional component is skipped. - Test the way the app runs it: ssh host 'env -i HOME=$HOME bash -c "bash build.sh"', or env -i locally, to reproduce the bare environment. - Don't 'fix' it by sourcing the user's .bashrc from the script. That's slow, has side effects, and differs from user to user.