The default build does not run extension-side process commands for Ruby LSP
startup. It uses configured lsp.<server>.binary.path values first, then falls
back to worktree.which. If use_bundler is enabled, it launches through
bundle exec <server> without probing Bundler.
cargo testTo enable the command API path for project gem detection and extension-managed language server/debug gem installation, build with:
cargo test --features command_apiThis is not a replacement for fixing Zed's command spawning behavior:
zed-industries/zed#57170. The command-free profile
expects bundle or the language server executable to be available from the
project environment. Debugging expects rdbg to be available from that same
environment.