backeer-codex 0.13.0 → 0.13.1

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.1",
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,47 @@ 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
+ ## Durable lifecycle notifications (0.13.1)
17
+
18
+ Completion and optional failed-tool notifications are saved to a private disk
19
+ outbox before sending. The hook waits for durable local storage and worker
20
+ handoff, not a gateway response. A detached, bounded worker continues after the
21
+ hook exits. Permission creation, mobile approval decisions, acknowledgements and
22
+ the interactive test notification retain their existing direct delivery path.
23
+
24
+ The queue is under `data/notification-outbox` in the configured Codex directory
25
+ (or under `PLUGIN_DATA`). Records use owner-only permissions and retain their
26
+ original event IDs across retries. Source credentials are not stored in records
27
+ or process arguments. Endpoint/credential changes select a separate queue; an
28
+ old source's records are never sent using a replacement credential. Queue files
29
+ contain notification payloads and should be treated like local conversation data.
30
+
31
+ Each worker makes at most three passes of 64 records, with a three-second pause
32
+ between passes and a ten-second deadline per request. Network errors, 429 and
33
+ 5xx retain pending records; subsequent configured hooks resume any backlog after
34
+ the bounded worker exits or the host restarts. Concurrent workers atomically
35
+ claim records, and records from exited workers are recovered on the next pass.
36
+ Delivery is at-least-once: retries preserve `externalId` for gateway deduplication.
37
+ Permanent HTTP failures and invalid records remain as `failed-*.json` for review
38
+ and are not automatically retried. `backeer-codex status` reports pending and
39
+ failed counts for the current source. No queue-count eviction discards records.
40
+
41
+ A queued result means saved locally, not delivered. Storage failures propagate
42
+ to the caller; the hook retains its normal empty-output fallback. Failure to
43
+ start a worker leaves the saved record available for a later hook.
44
+
45
+ ## Prepared context filter (unreleased)
46
+
47
+ The bundled client now filters superseded/old ordinary compact references while
48
+ keeping raw/detail access unchanged. `watch_activity` defaults to changes-only
49
+ replies. `context_memory` is the 26th managed tool: it protects local decisions,
50
+ confirmed question answers, observed pending requests and unresolved errors.
51
+ Records survive raw-buffer expiry in a protected per-binding disk ledger with a
52
+ 256-entry RAM index cache; normal disconnect removes them. Bindings never share
53
+ these local decisions. This is not automatic cross-chat memory or removal of old
54
+ host conversation messages. Explicit native settlement or evidenced error
55
+ resolution is required; age and an unrelated success are insufficient.
56
+
16
57
  ## Stability update (0.13.0)
17
58
 
18
59
  The terminal companion releases completed tool payloads on item/turn/thread