createOpencode function failure on Windows due to spawn usage

[webuilder]

Description

When I use opencode sdk on windows. I called createOpencode function, then got a fail

node:internal/child_process:286
      const err = new ErrnoException(exitCode, syscall);
                  ^

Error: spawn opencode ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:89:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn opencode',
  path: 'opencode',
  spawnargs: [ 'serve', '--hostname=127.0.0.1', '--port=0' ]
}

Plugins

No response

OpenCode version

1.2.27

Steps to reproduce

Run following on windows 11, then got error.

const { createOpencode } = await import('@opencode-ai/sdk');

const opencode = createOpencode({
    port: 4000,
});

Screenshot and/or share link

Operating System

Windows 11

Terminal

Power shell

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• fix(sdk): spawn fails on Windows - ENOENT for opencode command #8160: Same spawn opencode ENOENT error on Windows in the SDK, with the same root cause (Windows .cmd wrapper scripts requiring shell: true)
• Windows spawn ENOENT error in OpenCode SDK #2812: Same Windows spawn ENOENT error in the OpenCode SDK affecting createOpencodeServer/createOpencodeTui

Please review those issues and consider whether your report adds new information. If so, a maintainer may consolidate.