backeer-opencode 0.7.0 → 0.8.1

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 All notable changes to `backeer-opencode` are documented here.
 
+## 0.8.1 - 2026-11-03
+
+- Resolve an existing private V2 server before shared-service discovery; verify native API PID and exact session/project without starting a service or hardcoded ports/session IDs.
+- Discover Linux ephemeral listeners only from the current process's socket inodes; retain compatible owning shared-service and verified worktree handling.
+- Return allowlisted native-question diagnostics without exposing upstream text or credentials.
+
+## 0.8.0 - 2026-11-03
+
+- Add `list_questions` and `answer_question` to both MCP adapters: pending text/options, single/multiple selection and custom text answers.
+- Rehydrate pending questions from OpenCode after reconnect, scoped to the exact session and project. Reuse existing native V1/V2 question reply adapters.
+- Pin answers to a question revision and option indices, retain idempotent delivery, and exclude permission/authentication forms. Mobile approvals remain unchanged.
+
 ## 0.7.0 - 2026-11-03
 
 - Add bounded first-run discovery of known loopback endpoints and protected token files, project detection and validated profile saving through MCP.

package/README.md

@@ -69,7 +69,7 @@ Version 0.6.0 also supports saved connections and separate per-chat session
 bindings. Set `BACKEER_LIVE_PROFILES_FILE` on the local MCP adapter, or use the
 bundled connection tools in `backeer-codex` 0.3.0. Existing `BACKEER_LIVE_URL` /
 `BACKEER_LIVE_TOKEN_FILE` single-connection configuration still exposes its
-original four tools. See [per-chat connections](docs/live-control.md#per-chat-connections).
+original tools, plus ordinary question reading/answering in 0.8.0. See [per-chat connections](docs/live-control.md#per-chat-connections).
 
 ## Requirements
 
@@ -301,12 +301,15 @@ 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.
+V2 question reads/replies use the official authenticated client API. For an
+existing private stdio server, 0.8.1 first verifies its own native API and PID;
+a Linux ephemeral port is discovered only from that process's socket inodes.
+An explicit private `--port` also works without Linux socket discovery.
+Other processes retain compatible shared-service discovery. Exact session and
+project/worktree ownership are checked before reading or answering. The plugin
+never starts another service, moves a session or changes authentication. An
+unverifiable private server fails explicitly rather than selecting a different
+shared service.
 
 The V1 event mappings are: