backeer-opencode 0.3.2 → 0.4.0

package/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 All notable changes to `backeer-opencode` are documented here.
 
+## 0.4.0 - 2026-10-11
+
+- Add a V2 default definition with a stable ID, setup, event subscription,
+  command transform, prompt hook, and abortable cleanup; retain the V1 server
+  entrypoint for OpenCode 1.18.29 and newer.
+- Adapt native V2 permission replies, question forms, and execution lifecycle
+  events, with location isolation and reconnect handling.
+- Use the V2 plugin installation command for explicitly requested updates.
+- Keep automatic delivery feedback in server logs on V2 rather than injecting
+  it into model context. Native V2 no longer provides ignored conversation
+  entries or todo.updated events; todo notifications remain available on V1.
+- Rebuild the dependency-free installer bundle and add V2 regression tests.
+- Verification: `npm run check` passes all 49 tests; `npm audit --omit=dev`
+  reports no vulnerabilities. The packed installer loads as active on an isolated
+  OpenCode 2.0.26 service, `/backeer token` executes without an agent turn, and
+  native question answer/cancel calls pass through authenticated discovery.
+
 ## 0.3.2 - 2026-09-02
 
 - Synchronize the plugin's reported runtime version with the published package

package/README.md

@@ -13,7 +13,7 @@ inbound firewall rule.
 
 ## Requirements
 
-- OpenCode with server plugin support
+- OpenCode V2 (tested against 2.0.26), or V1 1.18.29 and newer
 - Node.js 18 or newer for the local installer and tests
 - Outbound HTTPS access to `external-gateway.backeer.com:443`
 - A Backeer source ingest token
@@ -24,7 +24,7 @@ uses that token and weakens host-level auditing and revocation.
 
 ## Local installation
 
-The local installer copies a single dependency-free plugin file into OpenCode's
+The local installer copies a single self-contained plugin file into OpenCode's
 global plugin directory. OpenCode discovers it automatically.
 
 ```sh
@@ -54,7 +54,7 @@ Restart OpenCode after installation or update.
 Install the package in OpenCode's global configuration:
 
 ```sh
-opencode plugin backeer-opencode -g
+opencode plugin add backeer-opencode
 npx backeer-opencode@latest configure
 ```
 
@@ -67,7 +67,7 @@ Alternatively, add it to `~/.config/opencode/opencode.json` manually:
 ```json
 {
   "$schema": "https://opencode.ai/config.json",
-  "plugin": ["backeer-opencode"]
+  "plugins": ["backeer-opencode"]
 }
 ```
 
@@ -121,14 +121,14 @@ environment variables are supported:
 | `BACKEER_LOG_LEVEL` | `info` (default), `error`, `debug`, or `silent` |
 
 For npm installations, non-secret options can also be supplied through the
-OpenCode plugin tuple syntax:
+OpenCode V2 plugin options syntax:
 
 ```json
 {
-  "plugin": [
-    [
-      "backeer-opencode",
-      {
+  "plugins": [
+    {
+      "package": "backeer-opencode",
+      "options": {
         "permissions": true,
         "questions": true,
         "todos": true,
@@ -142,7 +142,7 @@ OpenCode plugin tuple syntax:
           "retryAttemptThreshold": 3
         }
       }
-    ]
+    }
   ]
 }
 ```
@@ -153,7 +153,7 @@ entire lifecycle group. The token itself is deliberately not a plugin option.
 
 ## Conversation feedback
 
-User-facing status messages appear as compact Backeer entries in the OpenCode
+On OpenCode V1, user-facing status messages appear as compact Backeer entries in the OpenCode
 conversation:
 
 ```text
@@ -170,8 +170,13 @@ an agent is active, a permission prompt is open, or a question is awaiting an
 answer remains queued until the interaction closes and the session becomes idle.
 It never writes to the user's input field or replaces interactive OpenCode UI.
 
-Technical diagnostics use OpenCode's structured application log API instead of
-stdout. Normal `info` logging omits HTTP details; set
+On V2, automatic delivery feedback stays in server logs: the V1 ignored/noReply
+conversation API no longer exists. `/backeer` command results use a synthetic
+entry with `resume: false`, so they do not start an agent turn, but they can be
+included in later model context. No credentials are displayed.
+
+Technical diagnostics use V1's structured application log API or V2's captured
+server stderr, never stdout. Normal `info` logging omits HTTP details; set
 `BACKEER_LOG_LEVEL=debug` when technical details are needed. Set it to `error`
 for failures only or `silent` to disable structured logs.
 
@@ -228,7 +233,22 @@ package caches.
 
 ## Events and decisions
 
-The plugin publishes:
+On V2, native `form.created` question forms are adapted to Backeer question
+cards, replies use `session.form.reply/cancel`, and
+`session.execution.started/succeeded/failed/interrupted` drive lifecycle
+notifications. Only forms marked `metadata.kind: "question"` are forwarded;
+authentication and other forms are never exported. Events from other locations
+are ignored. V2 has no native `todo.updated` event, so todo notifications are
+disabled there regardless of the `todos` option.
+
+V2 remote question replies require the managed shared service. OpenCode 2.0.26
+does not expose forms on the plugin context, so the plugin uses the official
+client's authenticated service discovery and verifies session location before
+answering. It never starts another service. Notifications work in standalone
+mode, but remote question replies fail explicitly there rather than contacting
+a different session.
+
+The V1 event mappings are:
 
 | OpenCode event | Backeer behavior |
 |---|---|