[Bug]: Provider update fails when binary not found, even if direct binary path is set

Before submitting

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

Area

apps/server

Steps to reproduce

1. Hide the opencode binary from shell exposed to t3 in any way. In my case at the end of zshrc I call

fish
exit

2. Set direct path to selected provider in config

3. Try to update provider when outdated via app, and receive the error

From what I seen, the binary path isn't carried to update command:

I would consider two possible soulutions:

1. Carry the binary path to update commands, but it looks like workaround around core issue for me
2. Fix the problem that binaries are not found even tho setup like this (with fish) finds them correctly in regular shell

I did encounter this error with OpenCode, Codex and Claude,

Tested on nightly: 0.0.34-nightly.20260811.1064, encountered on both stable and other nightly releases

Expected behavior

When I click "update providers" button providers get updated correctly

Actual behavior

Error occurs because binary could not be found.

Impact

Minor bug or occasional failure

Version or commit

0.0.34-nightly.20260811.1064

Environment

macOS and Linux Server

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

I just run update commands manually, but I think carrying the binary path into the update system could be considered workaround.

Start in the apps/server provider-update flow and reproduce the failure by hiding the binary from the shell while configuring its direct path. Verify that clicking the update providers button succeeds for OpenCode, Codex, and Claude when the binary is unavailable through the shell but available through the configured path.