opencode2: plugin list crashes and plugins from config not loaded

[mrofisr]

Summary

opencode2 (next) does not load or list plugins configured in ~/.config/opencode/opencode.json. The opencode2 plugin list command crashes with a chdir bug (ENOENT: no such file or directory, chdir '/home/ubuntu' -> 'plugin').

Environment

• opencode version: 0.0.0-next-15747 (next channel)
• OS: Linux 6.17.0-1018-oracle aarch64 (Ubuntu 24.04)
• Terminal: TERM_PROGRAM=tmux, TERM=tmux-256color
• Shell: /bin/bash
• Install/channel: next (via volta)
• Active plugins: superpowers, oh-my-openagent (configured but not loaded)

Reproduction

1. Configure plugins in ~/.config/opencode/opencode.json:

   {
     "plugins": [
       "superpowers@git+https://github.com/obra/superpowers.git",
       "oh-my-openagent@latest"
     ]
   }

2. Run: opencode2 plugin list

Expected Behavior

Configured plugins should be listed with their status.

Actual Behavior

Error: ENOENT: no such file or directory, chdir '/home/ubuntu' -> 'plugin'

Additional Context

• Same chdir bug as opencode2 models 9router (opencode2: Model unavailable error for OpenAI-compatible provider despite working API #37531).
• Related to the broader pattern where opencode2 ignores config sections (providers, mcp, permissions, agents, plugins).

[github-actions]

This issue might be related to existing issues about plugins not loading in v2. Please check:

• v2: external TUI plugins declared in tui.json are never loaded #36525: v2 external TUI plugins declared in tui.json are never loaded — similar theme of plugins configured but not loaded in opencode2
• tui: external TUI plugins from tui.json are parsed but not loaded #36505: tui external TUI plugins from tui.json are parsed but not loaded — another related report

These are slightly different contexts (tui.json vs opencode.json, TUI plugins vs server plugins), but they may share the same underlying cause in how opencode2 handles plugin configuration.

[rekram1-node]

v1 plugins are not compatible sso they will not work w/ v2.