Web frontend bundled with [email protected] is 1.18.14 (version mismatch: app-version.v1 = 1.18.14) #41280

Description

The [email protected] npm package ships a binary whose embedded web frontend is 1.18.14, not 1.18.15. The server binary reports "1.18.15" but serves the older frontend chunk (index-DkiM3pJJ.js, which writes app-version.v1 = "1.18.14").

Steps to reproduce

1. Install [email protected] (npm).
2. Run opencode web --port 4096 --hostname 0.0.0.0.
3. Open the web UI and check localStorage["app-version.v1"] → shows {"version":"1.18.14"}.
4. Inspect the served HTML → references index-DkiM3pJJ.js (old chunk).

Evidence

• Binary strings (opencode-linux-x64/bin/opencode) contain two frontend bundles:
  • index-DkiM3pJJ.js + index-DkiM3pJJ-fyjg9exh.js → app-version = "1.18.14"
  • index-LbjPUYWZ.js + index-LbjPUYWZ-f2dwhw18.js → "1.18.15"
• The served HTML references only the old chunk: index-DkiM3pJJ.js.
• curl http://127.0.0.1:4096/ returns HTML whose <script src="/web-api/iframe-proxy?url=https://github.com/_next/static/chunks/index-DkiM3pJJ.js"> corresponds to the 1.18.14 bundle.
• API surface of both bundles is identical (verified by string-diff of all "/..." paths), so API calls work, but the UI runs the older code path.

Impact

• Users on 1.18.15 effectively run the 1.18.14 web UI: any frontend fix shipped between 1.18.14 and 1.18.15 (e.g. session-list / bookmark seeding fixes) is missing.
• Confusing when debugging UI bugs against the reported server version.

Environment

• OS: Ubuntu 22.04 x86_64
• opencode: 1.18.15 (npm opencode-ai)
• Start command: opencode web --port 4096 --hostname 0.0.0.0