Shell provider returns "Endpoint is unavailable" when executing local commands

Bug description

OpenCode's Shell tool is failing to execute local PowerShell commands.

When attempting to run a local Android ADB command:

$adb = "$env:LOCALAPPDATA\Android\sdk\platform-tools\adb.exe"
& $adb devices | Out-String

OpenCode returns:

Error from provider (Console): Upstream request failed: Endpoint is unavailable.

The command does not appear to execute, so no stdout/stderr from adb is returned.

Environment
OS: Windows
Shell: PowerShell
OpenCode: [version]
Android SDK / ADB: Installed and available locally
ADB path:
%LOCALAPPDATA%\Android\sdk\platform-tools\adb.exe
Expected behavior

OpenCode should execute the local shell command and return the command's stdout/stderr.

For example:

List of devices attached
XXXXXXXX    device
YYYYYYYY    device
Actual behavior

OpenCode fails before returning the command result:

Error from provider (Console): Upstream request failed: Endpoint is unavailable.
Reproduction
Open a project in OpenCode on Windows.
Open Shell.
Run a local PowerShell command, for example:
$adb = "$env:LOCALAPPDATA\Android\sdk\platform-tools\adb.exe"
& $adb devices | Out-String
Shell execution fails with:
Upstream request failed: Endpoint is unavailable.
Impact

This prevents OpenCode from executing local development/diagnostic commands through the Shell tool.

In my case, it prevents automated Android device validation using ADB, even though the Android devices are connected to the same Windows laptop.

This appears to be a Shell/provider execution issue rather than an ADB or application error.

Additional note

The same local environment has Android SDK/platform-tools installed and the project can otherwise build successfully.

No application code changes were made to work around this issue.