TUI crash: PluginProvider is missing

Summary

OpenCode TUI crashed with Error: PluginProvider is missing during use.

Environment

• opencode version: 2.0.8
• OS: Linux 7.2.5-4-omarchy (x64)
• Terminal: xterm-256color
• Shell: Unavailable: not captured in crash report
• Install/channel: latest
• Active plugins: Unavailable: crash report did not include plugin list (local reporter config has no plugins in ~/.config/opencode/opencode.jsonc)

Reproduction

1. Launch opencode TUI (v2.0.8 on Linux 7.2.5-4-omarchy x64, xterm-256color)
2. Use TUI normally (exact action unknown — reported automatically from crash screen)
3. TUI crashes with PluginProvider is missing

Expected Behavior

TUI should not crash; PluginProvider context should be available to the component tree.

Actual Behavior

TUI crashed with unexpected error:

Error: PluginProvider is missing
    at sa (/$bunfs/root/chunk-vbstx86m.js:2593:2804)
    at Uc (/$bunfs/root/chunk-x0cbprj9.js:4:248)
    at Jr (/$bunfs/root/chunk-zr6pz3ag.js:2:7348)
    at children (/$bunfs/root/chunk-vbstx86m.js:2590:118420)
    at <anonymous> (/$bunfs/root/chunk-zr6pz3ag.js:2:15047)
    at rA (/$bunfs/root/chunk-zr6pz3ag.js:2:10380)
    at Ye (/$bunfs/root/chunk-zr6pz3ag.js:2:10156)
    at c (/$bunfs/root/chunk-zr6pz3ag.js:2:4465)
    at Pe (/$bunfs/root/chunk-zr6pz3ag.js:2:8653)
    at Jr (/$bunfs/root/chunk-zr6pz3ag.js:2:7348)

Additional Context

• Reported automatically from the OpenCode crash screen.
• Frequency / specific trigger action unknown — reporter indicated "During use" but did not provide steps.
• Reporter diagnostics snapshot (from separate Mac used to file issue, not crash machine): opencode v2.0.8, Darwin 24.6.0 arm64, TERM=xterm-256color / TERM_PROGRAM=ghostty, SHELL=/opt/homebrew/bin/fish, no active plugins in config.

Start by reproducing the crash in the OpenCode TUI using v2.0.8 on Linux, since the exact triggering action is unknown. Trace the source corresponding to the minified PluginProvider is missing stack and inspect how the TUI component tree receives that context. Done means the reported workflow no longer crashes and the relevant regression is covered by a test.