[Bug]: SSH command failures hide stdout diagnostics #2919

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Trigger a desktop SSH environment operation that runs a remote command through runSshCommand.
2. Have the remote command exit non-zero.
3. Have the remote command print its useful failure message to stdout while leaving stderr empty.
4. Observe the desktop logs and surfaced SshCommandError.

Expected behavior

The SSH failure log and SshCommandError should include enough command output to diagnose the failed remote command. If stderr is empty but stdout contains text, stdout should be available and should be used as the fallback error message.

Actual behavior

runSshCommand collects stdout and stderr, but on non-zero exit it only logs stderr and only derives the error message from stderr.

When stderr is empty, the surfaced error becomes generic:

SshCommandError: SSH command failed for <host> (exit 1).

This hides useful diagnostics printed to stdout by remote commands, including SSH pairing/setup failures.

Impact

Major degradation or frequent failure

Version or commit

main

Environment

Desktop SSH environment flows on Linux AppImage; likely affects any platform using packages/ssh.

Logs or stack traces

ssh.command.failed ... exitCode: 1, stderr: ''
SshCommandError: SSH command failed for mwolson@remote-game (exit 1).

Workaround

Manually rerun the generated remote command over SSH and capture stdout/stderr separately.