backeer-codex 0.13.0 → 0.13.2

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.13.0",
3
+ "version": "0.13.2",
4
4
  "description": "Backeer approvals, lifecycle notifications and chat-scoped OpenCode connections.",
5
5
  "author": {
6
6
  "name": "Backeer"
package/README.md CHANGED
@@ -13,6 +13,65 @@ It provides:
13
13
  - Safe fallback to the normal Codex permission prompt when Backeer is unavailable or not configured.
14
14
  - Saved OpenCode connections and an independent exact-session binding for each chat, automatically tracking its subagent tree over live SSE.
15
15
 
16
+ ## Smaller tool responses (0.13.2)
17
+
18
+ Bound connection diagnosis returns coverage and counts by default. Use
19
+ `includeTree: true` or `session_status` for the complete returned tree under
20
+ `tree`. Status callers that expect `session.tree` can request
21
+ `treeFormat: "legacy"`.
22
+
23
+ Activity and detail-list tools may return a smaller, lossless `referenceTable`
24
+ in place of the reference array. Each row follows `columns`. A number indexes
25
+ the column's dictionary from zero, a string is literal, and null marks an absent
26
+ field. Pass `referenceFormat: "expanded"` for the original object array. Event
27
+ IDs, pagination, exact text reads, and critical alerts keep their existing scope.
28
+
29
+ ## Durable lifecycle notifications (0.13.1)
30
+
31
+ Completion and optional failed-tool notifications are saved to a private disk
32
+ outbox before sending. The hook waits for durable local storage and worker
33
+ handoff, not a gateway response. A detached, bounded worker continues after the
34
+ hook exits. Permission creation, mobile approval decisions, acknowledgements and
35
+ the interactive test notification retain their existing direct delivery path.
36
+
37
+ The queue is under `data/notification-outbox` in the configured Codex directory
38
+ (or under `PLUGIN_DATA`). Records use owner-only permissions and retain their
39
+ original event IDs across retries. Source credentials are not stored in records
40
+ or process arguments. Endpoint/credential changes select a separate queue; an
41
+ old source's records are never sent using a replacement credential. Queue files
42
+ contain notification payloads and should be treated like local conversation data.
43
+
44
+ Each worker makes at most three passes of 64 records, with a three-second pause
45
+ between passes and a ten-second deadline per request. Network errors, 429 and
46
+ 5xx retain pending records; subsequent configured hooks resume any backlog after
47
+ the bounded worker exits or the host restarts. Concurrent workers atomically
48
+ claim records, and records from exited workers are recovered on the next pass.
49
+ Delivery is at-least-once: retries preserve `externalId` for gateway deduplication.
50
+ Permanent HTTP failures and invalid records remain as `failed-*.json` for review
51
+ and are not automatically retried. `backeer-codex status` reports pending and
52
+ failed counts for the current source. No queue-count eviction discards records.
53
+
54
+ A queued result means saved locally, not delivered. Storage failures propagate
55
+ to the caller; the hook retains its normal empty-output fallback. Failure to
56
+ start a worker leaves the saved record available for a later hook.
57
+
58
+ ## Compact follow and protected context (0.13.1)
59
+
60
+ The bundled client now filters superseded/old ordinary compact references while
61
+ keeping raw/detail access unchanged. `watch_activity` defaults to changes-only
62
+ replies. Merge changed fields, apply agent updates/removals and any explicit
63
+ `agentOrder`, and remove the gap when `delta.gap` is null. A verification-only
64
+ update can carry `lastVerifiedAt` without a new card. Critical alerts and
65
+ delivery updates can accompany an unchanged card. Follow waits up to 45 seconds
66
+ by default and batches routine changes for one second. Critical alerts wake the
67
+ wait immediately. `context_memory` protects local decisions,
68
+ confirmed question answers, observed pending requests and unresolved errors.
69
+ Records survive raw-buffer expiry in a protected per-binding disk ledger with a
70
+ 256-entry RAM index cache; normal disconnect removes them. Bindings never share
71
+ these local decisions. This is not automatic cross-chat memory or removal of old
72
+ host conversation messages. Explicit native settlement or evidenced error
73
+ resolution is required; age and an unrelated success are insufficient.
74
+
16
75
  ## Stability update (0.13.0)
17
76
 
18
77
  The terminal companion releases completed tool payloads on item/turn/thread