Web terminal fails under CSP when Ghostty WASM loads via data URL

[xomaxie]

When running the web UI behind a strict CSP (connect-src 'self'), the terminal fails to load. Console shows "Fetch API cannot load data:application/wasm;base64,..." and "Failed to load ghostty-vt.wasm". This happens in Safari/Firefox and in Cloudflare Access setups with default CSP.

Repro:

1. Run opencode web
2. Serve UI with CSP connect-src 'self'
3. Open terminal -> blank

Expected: terminal loads.
Actual: Ghostty WASM load blocked because it uses a data: URL.

Proposed fix: load ghostty-vt.wasm via asset URL instead of data: (Vite ?url).

[github-actions]

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

• Web UI does not load when running opencode web #6557: Web UI does not load when running opencode web - Related MIME type and module loading failures
• opencode web mode broken: empty page - multiple versions and multiple os #5237: opencode web mode broken: empty page - Multiple versions/OS with asset loading errors
• Web UI fails to load - JS module blocked due to incorrect MIME type #6122: Web UI fails to load - JS module blocked due to incorrect MIME type
• Black screen when running opencode web in v1.0.17 (blocked insecure content / CORS errors) #3853: Black screen when running opencode web - Security policy violations (CORS, insecure content)
• Opencode Web: Terminal not working #7578: Opencode Web: Terminal not working - Terminal component not functional in web UI
• web terminal can not input chinese , and latest version terminal can't use, asset load error! #8833: web terminal can not input chinese - Web terminal malfunction with asset load error

These issues describe similar problems with web content loading failures, security policy violations (CSP, CORS), and MIME type enforcement that may be related to your WASM loading issue.

Feel free to ignore if none of these address your specific case.