[Windows] Upgrade embedded Bun runtime from v1.3.5 — LSP broken due to spawn segfault #11648

Description

opencode v1.1.48 ships a standalone executable (opencode.exe) with Bun v1.3.5 embedded. This version has a known segmentation fault bug on Windows when spawning child processes (e.g., LSP servers).

Users cannot upgrade the embedded Bun runtime — it's baked into the binary via bun build --compile. Even upgrading system Bun to v1.3.8 has no effect.

Impact

• All LSP functionality is broken on Windows for opencode + oh-my-opencode users
• oh-my-opencode has added a safety check that blocks LSP startup entirely when Bun < 1.3.6 is detected
• Since the embedded version is always 1.3.5, LSP is permanently disabled with no user workaround

Evidence

# Binary contains hardcoded Bun v1.3.5
$ strings opencode.exe | grep "Bun v"
Bun v1.3.5
Bun v1.3.5

# opencode version
$ opencode --version
1.1.48

Request

Please upgrade the embedded Bun runtime in the standalone executable to v1.3.6 or later in the next release.

Related Issues

• Segmentation fault at address 0x0 on Windows x64 baseline in Bun v1.3.5 during opencode-ai execution oven-sh/bun#25798 — Windows spawn segfault in Bun v1.3.5
• Segmentation Fault in Bun v1.3.5 on Windows 10 x64 During Opencode Execution oven-sh/bun#26026 — Same segfault, different reporter
• [Bug][v3.0.0-beta.15]: Bun crashed when using LSP(lsp_diagnostics) on Windows code-yeongyu/oh-my-openagent#1047 — LSP crash on Windows
• [Bug] LSP permanently blocked on Windows: opencode embeds Bun v1.3.5, users cannot upgrade code-yeongyu/oh-my-openagent#1366 — LSP permanently blocked due to embedded Bun version

Environment

• opencode: v1.1.48
• Embedded Bun: v1.3.5
• OS: Windows 11 x64