backeer-codex 0.11.0 → 0.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "backeer-codex",
3
- "version": "0.11.0",
3
+ "version": "0.12.0",
4
4
  "description": "Backeer approvals, lifecycle notifications and chat-scoped OpenCode connections.",
5
5
  "author": {
6
6
  "name": "Backeer"
package/README.md CHANGED
@@ -74,7 +74,7 @@ backeer-codex opencode sessions dev
74
74
  Then tell Codex in a new chat: **“Connect this chat to dev, session ses_….”**
75
75
  The tools validate the project and session, then return a unique binding for
76
76
  that chat. Other chats can select different sessions without changing it. Each
77
- binding has its own stream/cursor, including when multiple chats follow the same
77
+ binding has its own projection/cursors, including when multiple chats follow the same
78
78
  session. Commands require that binding; no global default or automatic fallback
79
79
  exists. Prompt delivery keeps the existing request-ID deduplication rules.
80
80
 
@@ -103,7 +103,7 @@ The same binding/cursor is retained; new instructions and answers still require
103
103
  fresh project/session verification. Missing replay history is reported as a gap,
104
104
  never invented or treated as complete. A gap must not be acknowledged until
105
105
  `session_status` succeeds for the same target. Disconnecting one chat does not
106
- close another chat's stream, and active bindings do not consume the quota for
106
+ close another chat's subscription, and active bindings do not consume the quota for
107
107
  read-only session listings or diagnosis.
108
108
 
109
109
  The plugin does not create SSH tunnels or change SSH permissions. Keep the saved
@@ -297,3 +297,45 @@ project, including worktrees, instead of proxying one owner's stream. Reload
297
297
  old owner processes after updating the shared gateway protocol. Update both
298
298
  plugins; updating only the local adapter cannot fix remote child event delivery.
299
299
  Opaque agents inside a separate Codex process still need its own event source.
300
+
301
+ ## Slow API recovery (0.11.1)
302
+
303
+ The bundled adapter coordinates with remote Backeer OpenCode 0.14.2: native reads
304
+ allow 10 seconds, aggregated snapshots allow 30 seconds, and local HTTP/handshakes
305
+ allow 45 seconds. Reconnects still wait 3 seconds between attempts. Discovery
306
+ uses the read budget rather than failing healthy inventories after 3 seconds.
307
+ `verify_connection` defaults to 30 seconds per check; explicit caller deadlines
308
+ remain authoritative. Actual native deadlines are reported distinctly as
309
+ `native_session_api_timeout` (504), with no automatic command replay.
310
+ Update both ends and load the new remote owner code; a local upgrade alone
311
+ cannot override the remote gateway's old 1.5-second limit.
312
+
313
+ ## 0.12.0: durable delivery and economical live control
314
+
315
+ Requires Backeer OpenCode 0.15.0 for all new bridge features. The self-contained
316
+ adapter exposes 25 tools, including connection_report, instruction_status,
317
+ tail_output, read_errors and tool_result. Existing bindings follow verified
318
+ subagents automatically. Ordinary child questions can be read/answered from
319
+ the same chat with an explicit targetSessionId and fresh native ancestry/form
320
+ checks. Instructions continue to target the selected root.
321
+
322
+ Activity uses SSE projection and bounded periodic reconciliation. Pass
323
+ changesOnly:true to receive deltas after the first full card. Critical alerts
324
+ still arrive immediately. Compatible bindings share one project SSE transport
325
+ within one MCP process, retaining independent scopes/cursors and gap recovery.
326
+ Separate MCP processes do not share a transport.
327
+
328
+ Accepted, queued, delivered and completed are distinct. Inspect the persisted
329
+ exact request receipt before retrying uncertain delivery. Protected journals
330
+ store signatures/receipts, never prompt or answer text. Interrupted reservations
331
+ are not replayed automatically. Guarantees begin with requests recorded by the
332
+ new bridge. Native V1 delivery can remain unknown. Session completion is never
333
+ claimed as proof of per-instruction completion.
334
+
335
+ Use `backeer-codex opencode report <name>` or connection_report for a safe,
336
+ layered diagnostic report. Loaded runtime versions are separate from unverified
337
+ installation state. Unsupported protocol majors block commands. Tail/error/tool
338
+ reads return source references and explicit clipping/retention gaps without
339
+ consuming transcript/detail cursors. Metrics measure bytes and latency, not
340
+ billed tokens. Install stages a complete replacement and restores local files
341
+ and marketplace on activation failure; it never edits an active plugin cache.