tui: crash with UnsupportedContentType (event stream)

Summary

The OpenCode TUI crashed with ClientError: UnsupportedContentType originating from the event-stream client. It happened once; the log shows a single event-stream disconnect with the same error followed by a successful reconnect ~80ms later.

Environment

• opencode version: 2.0.7
• OS: Darwin 25.6.0 (arm64)
• Terminal: Orca 1.4.205 (TERM=xterm-256color, TERM_PROGRAM=Orca, COLORTERM=truecolor)
• Shell: /bin/zsh
• Install/channel: release (opencode v2.0.7 via npm global @opencode/cli)
• Active plugins: local project plugin .opencode/plugins/agentmemory-capture.ts (note: this plugin is currently failing to load on the server with Cannot find package '@opencode/plugin' — separate issue, possibly unrelated)

Reproduction

1. Have the TUI open (project workspace, exact view unknown).
2. Crash occurred once without a clear triggering action from the user.

Minimal steps are unavailable — the triggering action is unknown and it has only happened once.

Expected Behavior

The TUI should stay alive; at most the event stream should reconnect silently (as the log shows it can).

Actual Behavior

The TUI crashed to the crash screen with:

ClientError: UnsupportedContentType
    at S (/$bunfs/root/chunk-0vaztdxa.js:13:25549)
    at async <anonymous> (/$bunfs/root/chunk-0vaztdxa.js:2:912)
    at processTicksAndRejections (native:7:39)

Additional Context

• Server log shows exactly one matching entry: 2026-09-18T09:09:23.698Z ... "event stream disconnected" component=client attempt=1 error=UnsupportedContentType role=cli, followed by event stream connecting (attempt 1) and event stream connected 84ms later. The client recovered at the log level, but the TUI still crashed.
• Frequency: once. No other UnsupportedContentType entries in the log.
• No workaround tried (single occurrence, client reconnected on its own per the log).

No source file or test is identified; start by tracing the TUI event-stream client handling of UnsupportedContentType and the reconnect path described in the logs. Investigate how this one-time disconnect reaches the crash screen, using the bundled stack and server log as entry points. Done means the TUI stays alive while the event stream reconnects after this error.