fix(desktop): use PATH for WSL probe - #44512

Thanks for updating your PR! It now meets our contributing guidelines. 👍

AI code review — automated review for reference, author can ignore or act on any point.

Overall: correct and worthwhile — hardcoding /bin/true breaks on distros without a traditional /bin (notably NixOS and other exotic layouts), while relying on PATH matches how everything else in this file invokes commands inside the distro. Two small notes:

1. packages/desktop/src/main/wsl/runtime.ts:280 — this now depends on the non-login WSL exec environment having a sane PATH. That's true for essentially all mainstream distros today, but it does couple the probe to the distro's default env rather than an absolute location. If a future report ever shows canExecute: false on a healthy distro, this is the first place to look; a one-line comment noting why bare true is preferred over /bin/true would preserve that context for reviewers of the inevitable blame.

2. If you want belt-and-suspenders portability without PATH assumptions at all, ["/bin/sh", "-c", "exit 0"] covers both worlds (POSIX shells are more universally present than coreutils true) — though arguably true is clearer as an intent statement, and the current choice is fine.

The mocked-spawn test asserting the exact argv (["-d", "Alpine", "--", "true"]) plus the pty guard throwing on interactive use is a tidy regression net for a one-word change. Good to merge.

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.