Published npm 2.26.0 still ships a V1-only plugin export while main/README already target OpenCode v2

[InCerryGit]

Summary

opencode-mem@2.26.0 (current npm latest, published 2026-09-06) still default-exports the V1 plugin shape and fails to load on OpenCode v2. Meanwhile the main README Getting Started section already recommends the V2-style config {"plugins": ["opencode-mem"]}, and main contains V2 plugin support that is not part of any published release yet.

Environment

• OpenCode v2.0.18
• opencode-mem 2.26.0 (npm latest, published 2026-09-06T02:44:43.012Z)
• Config entry: {"plugins": ["opencode-mem"]} (as recommended by the main README Getting Started)
• OS: Linux (WSL2); terminal: unavailable (nonessential)

Reproduction

1. Use OpenCode v2 (v2.0.18 observed).
2. Add {"plugins": ["opencode-mem"]} to the OpenCode config as shown in the README Getting Started.
3. Start OpenCode.

Expected Behavior

Either the plugin loads on OpenCode v2, or the README clearly states that v2 support exists only on main and is not yet published.

Actual Behavior

The plugin fails to load with:

Plugin must export a default definition with an id and an effect or setup function.

Verified cause: the published entry https://unpkg.com/opencode-mem@2.26.0/dist/plugin.js still default-exports the V1 shape (export default { id, server: OpenCodeMemPlugin };, no setup/effect).

Additional Context

• main commit d413c2efeca1ac9f5d40f113f4485ffee7ae9b5c (2026-09-18, "feat: add OpenCode v2 plugin support") adds the V2 plugin definition, and main package.json also adds a ./v2 export plus @opencode/plugin ^2.0.8 (version still reads 2.26.0).
• Related: opencode 2.x is support or not ? #316, OpenCode V2 plugin API migration: timeline and plan? #173. This report adds the published-package verification (npm latest vs main) and the README/release mismatch.
• Request: publish a package version that includes the V2 support, or update the README to clarify that v2 support is on main only (including any temporary workaround).

[dhowe]

status?