aft-opencode plugin fails to load on opencode v2 (SchemaError: Expected object, got async initializer)

[ftzi]

Environment

• opencode v2 (opencode2, v0.0.0-next-17395 — the current V2 line)
• plugin: @cortexkit/aft-opencode@0.49.4 declared in the user-level config ("plugin": ["@cortexkit/aft-opencode@latest"] in ~/.config/opencode/opencode.jsonc)
• On V1 (opencode 1.18.15) the same entry loads fine

Error (server log, every session start):

failed to load plugin target=@cortexkit/aft-opencode@latest
cause=Cause([Fail(SchemaError(Expected object, got async (input) => initializePluginForDirectory(input)
  at ["default"]))])

Analysis
The plugin's dist exports the V1-style async initializePlugin function as the default export. The V2 plugin loader requires the module's default export to be a plain object (the V2 plugin contract). The plugin therefore never loads on V2 — it is npm-installed on demand, rejected with the SchemaError, and retried on every server start.

Request
Ship a V2-compatible build (default export object per the V2 plugin API), or document the V1-only status and the exact incompatibility. Happy to test a fix.

[ualtinok]

Confirmed, and it's expected-but-unannounced — thanks for the precise error capture. What you're seeing: V2 changed the plugin contract from V1's async initializer export to a {id, setup} object export, so the current @cortexkit/aft-opencode dist (V1-shaped) fails V2's export schema check at load. Nothing is broken on your V1 setups; the same entry keeps working there.

State on our side: the V2 migration is an active track — we've built a 6-gate migration plan against upstream/v2 with the OpenCode team, and the non-filesystem tool surface migrates first. Two upstream host gaps currently fence the filesystem tools (permission-ask and abort-signal seams in V2's Tool.Context, tracked upstream), so the first V2-compatible release will ship the broader tool surface with the hoisted read/write/edit trio following once those seams land.

Until that release, the plugin should be treated as V1-only. If you're running both lines side by side, keep the plugin entry in the V1 config only — a V2-side entry will fail load on every session start (noisy but harmless; OpenCode continues without the plugin). I'll update this issue when the V2-compatible version ships.