fix(opencode): make V2 plugin tools directly callable and routing independent of a stray MCP

[qoole]

What / Why / How

Follow-up to mksglu#1171 (targets its branch, so it can be folded into that PR rather than compete with it). I ran mksglu#1171 against a live OpenCode 2.0.7 server and it loads and hooks correctly. But three things kept context-mode from being automatic there. Each is one commit with a test that fails without the fix:

1. The ctx_* tools were not directly callable. In OpenCode 2, ToolEditor.add() defaults to codemode: true, which leaves a tool out of the model's direct tool list: it can only be reached by writing code against the execute tool's catalog. The routing layer, meanwhile, tells the model to call context-mode_ctx_execute, context-mode_ctx_fetch_and_index and context-mode_ctx_search directly, while the V2 registration used the bare ctx_* names. So the redirect named tools that did not exist. The tools are now registered with codemode: false. (4b91426)

2. Names now follow the router, through OpenCode 2's own namespace. OpenCode 2 builds the name the model sees as <namespace>_<name>. v2ToolIdentity() splits createToolNamer(platform)(tool) into { name, namespace }, so the visible name is exactly what the routing block and the execute.before redirects use, without hardcoding a prefix. If the OpenCode naming later changes (e.g. fix(tool-naming): use native ctx_* names for OpenCode/KiloCode plugin tools mksglu/context-mode#1161's bare ctx_*), registration follows automatically. (468b7eb)

3. Routing redirects depended on an unrelated process. routing.mjs only redirects curl/wget and large-output commands when isMCPReady() finds a live readiness sentinel, and only the stdio MCP server's main() writes one. With native V2 tools there is no MCP server. So on a machine where some other client happened to have a context-mode MCP server running, curl was redirected; on a machine without one, it ran straight through. The V2 setup() now writes the same sentinel for its own process: PID contents, refreshed every 30s against the reader's 90s window, on an unref'd timer, removed on dispose. (86c15ef)

Verified on OpenCode 2.0.7, as a local plugin on a live server with no context-mode MCP running:

• all context-mode_ctx_* tools appear as direct tools, and context-mode_ctx_execute runs;
• curl -s https://example.com | head -c 80 through the shell tool comes back as context-mode: curl/wget redirected. Call context-mode_ctx_execute(...), and the tools it names exist;
• the routing block is injected into the system prompt by the context hook (4,239 chars, alongside another plugin's context hook);
• ctx_execute still honours permissions.deny (sudo -n true → Command blocked by security policy).

Two notes, not changed here:

• The V1 native-tool path appears to have the same sentinel dependency (point 3). I left it alone because I could not test it against a live OpenCode 1.x host.
• OpenCode 2.0.7 loads a local plugin directory only through <dir>/index.js. It ignores package.json main/exports for local paths, and rejects a file path with configured plugin path must be a directory. That doesn't affect npm installs, but "Option B — manual install" from a clone would silently load nothing on V2 unless the package root has an index.js.

Affected platforms

• OpenCode

Test plan

• tests/opencode-plugin.test.ts: runs the real V2 setup() against a minimal fake OpenCode 2 context and asserts:
  • every tool is registered with codemode: false;
  • for every tool, the name OpenCode 2 would show (<namespace>_<name>) equals createToolNamer("opencode")(name);
  • a readiness sentinel exists for the process after setup(), isMCPReady() is true, and the sentinel is removed on dispose.
• Unit cases for v2ToolIdentity: the prefixed form maps to a namespace; bare names and mcp__… shapes are used as-is.
• Each new test fails before its fix and passes after.

Checklist

• Tests added/updated (TDD: red → green)
• npm test passes: 4,707 pass. The one failure, tests/scripts/asymmetric-drift-assert.test.ts (npm pack dry-run), fails identically on fix(opencode): support OpenCode 2 plugin API (V1/V2 dual export) mksglu/context-mode#1171's head and on this machine without these changes, so it looks environmental.
• npm run typecheck passes
• Docs updated if needed: see the note on local-directory installs above
• No Windows path regressions: only node:path joins, plus the existing sentinelDir()
• Targets next branch: this targets fix(opencode): support OpenCode 2 plugin API (V1/V2 dual export) mksglu/context-mode#1171's branch (which targets main)

[Scratchydisk]

Thanks for this — all three commits are now on main, cherry-picked with authorship preserved:

• 192312d — fix(opencode): register V2 ctx_* tools as direct tools under the routed names (was 4b91426)
• 2a5f7f3 — refactor(opencode): register V2 tools through OpenCode 2's namespace option (was 468b7eb)
• 95ea78f — fix(opencode): mark the V2 plugin as a ready tool provider for routing (was 86c15ef)

Verified: tests/opencode-plugin.test.ts 63 passed, npm run typecheck clean, and all three claims re-checked against opencode v2.0.9 (codemode default, <namespace>_<tool> flattening, directory-only plugin loading).

Notes for the record:

• src/adapters/opencode/plugin.ts on main is now identical to this PR's head.
• The one remaining test diff (ctx_search vs context-mode_ctx_search) is base divergence from 1378797 bare naming on main, not PR content — this PR never touched that line.
• Closing as superseded rather than merging, since the target branch fix/opencode-v2-plugin-compat is ~988 lines behind main; merging would drag the stale base back in.