[Bug]: Windows SSH environment error due to missing 'sh'

Before submitting

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

Area

apps/web

Steps to reproduce

1. Start the App
2. Click Settings
3. Click Environments
4. Pick SSH
5. Fill out the details for the environment (Windows environment with SSH enabled)
6. Click Add Environment

Expected behavior

Adds the environment via the ssh connection.

Actual behavior

Gives the following error: "The term 'sh' is not recognized as a name of a cmdlet, function, script file, or executable program." due to the target environment not having 'sh' (Windows environment)

Impact

Blocks work completely

Version or commit

No response

Environment

No response

Logs or stack traces

Screenshots, recordings, or supporting files

08de79f2d1c3373e64501e478668ff5c3e71417a48871cec4afdd08a835e3a19.png

Workaround

No response

Reproduce the failure through apps/web by opening Settings, choosing Environments, and adding a Windows SSH environment. Locate the SSH environment handling entry point and update the behavior so Windows targets do not require sh; done means the environment is added successfully.