[Bug] WebUI gets no response after sending message: GET /api/reference fails due to special characters in path; direct API calls work fine

Description

Describe the bug

When using the official Linux x64-baseline release binary, after sending messages in the Web chat interface, there is no response from the model.
Browser dev console shows an error on request GET /api/reference: the request path contains unexpected special characters.

Notably:
Direct API requests to /v1/chat/completions work perfectly when invoked manually. This issue only occurs within the WebUI.

Suspected root cause:
The pre-built release binary embeds stale frontend assets. The frontend code generates malformed request URLs with illegal characters, which causes the backend path resolution to fail.

Environment

• Binary: opencode-linux-x64-baseline.tar.gz (downloaded from GitHub Releases)
• OS: Kylin Linux V10 x86_64
• Startup command:
  ./opencode serve --hostname 0.0.0.0 --port 4096

Steps to reproduce

1. Launch opencode with the official prebuilt Linux binary
2. Visit the WebUI in browser
3. Create a new conversation and send any text message

Expected behavior

The model responds normally in the Web chat window.

Actual behavior

No reply is displayed. Browser console captures errors for GET /api/reference caused by special characters inside the requested directory path.

Additional information

1. Manual calls to OpenAI-compatible /v1/chat/completions API work without any error.
2. The musl variant binary fails to run on Kylin Linux.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response