fix: use user temp dir for Windows CLI startup

[niver2002]

Summary

• set TMP and TEMP to %LOCALAPPDATA%\Temp before spawning the Windows binary from packages/opencode/bin/opencode
• avoid OpenTUI DLL load failures on Windows where Bun falls back to bad temp extraction paths like B:/~BUN/root/...
• keep the fix scoped to the Windows launcher so generated npm wrappers do not need custom patching

Verification

• reproduced the local Windows failure with Failed to initialize OpenTUI render library ... error code 126
• verified that forcing a user-scoped temp directory lets the TUI boot normally
• upstreamed the same fix into the launcher source used by the published package

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[niver2002]

Reproduced locally on Windows with . Confirmed that forcing to lets the TUI boot normally, so this PR upstreams the same launcher-side fix.

[niver2002]

Summary: on Windows, set TMP and TEMP to the user's LOCALAPPDATA Temp directory before spawning the packaged binary from packages/opencode/bin/opencode. This avoids OpenTUI DLL load failures where Bun falls back to invalid temp extraction paths and the CLI hangs at startup with error code 126. Verification: I reproduced the failure locally, confirmed that switching to a user-scoped temp directory lets the TUI boot normally, and upstreamed that same launcher-side fix here.

[github-actions]

This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new pull request that follows our guidelines.