@securecoms/agent-bridge 0.24.0 → 0.25.1

package/dist/sodium-ready.d.ts

@@ -33,11 +33,17 @@
  * second warm-up, not a shortcut.
  *
  * ⛔ 2. DO NOT IMPORT `libsodium-wrappers-sumo` DIRECTLY HERE. ⇒ THIS ONE STILL
- * BINDS ON THIS FILE, UNCHANGED. `esbuild.config.mjs:15` inlines every
- * `@agentvault/connect-*` workspace package into the bridge bundle and that
- * specifier is absent from the EXTERNAL list at `:3-8`, so esbuild would bundle
- * a SECOND libsodium instance out of this file. The await would then warm a
- * heap that nothing reads, and this fix would look correct and do nothing.
+ * BINDS ON THIS FILE. Before #895 that specifier was absent from the EXTERNAL
+ * list in `esbuild.config.mjs`, so esbuild would have bundled a SECOND
+ * libsodium instance out of this file: the await would warm a heap that
+ * nothing reads, and the fix would look correct and do nothing. #895 inlines
+ * the patched `@agentvault/crypto` and makes `libsodium-wrappers-sumo` EXTERNAL
+ * precisely so the process keeps ONE instance, shared by the inlined crypto
+ * and anything else. ⛔ That singleton is now carried by the EXTERNAL entry;
+ * removing it from that list re-creates the split heap. `scripts/pack-smoke.sh`
+ * G-5b proves it on the installed tarball: the warm-up below, which only
+ * touches the INLINED crypto, must warm the libsodium the installed tree
+ * resolves.
  * ⚠️ The same inlining is why the delegate below is not a no-op in the shipped
  * bundle: the SDK barrier is inlined into `dist/bin.js` exactly once, and this
  * delegate points at that one copy.

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const BRIDGE_VERSION = "0.24.0";
+export declare const BRIDGE_VERSION = "0.25.1";

package/dist/ws-server.d.ts

@@ -64,6 +64,9 @@
  *     behind a 2^attempts × 5 s backoff. A nack fails only its own message.
  *     Messages never handed over (mid-flush close, a failed frame write) go
  *     back without that penalty.
+ *   - #842: a delivery still un-acked after INFLIGHT_STALE_AFTER_MS is LOGGED
+ *     once (`runtime_inbox.inflight_stale`) and otherwise left alone. There
+ *     is deliberately no lease: see INFLIGHT_STALE_AFTER_MS.
  *
  * Single consumer: the daemon serves one agent per process. A new `/v1/ws`
  * connection replaces the prior one (newest wins, mirroring the SSE path); the
@@ -77,7 +80,24 @@ import type { BridgeAgent } from "./bridge-agent.js";
 export interface AgentWebSocketOptions {
     token: string;
     allowOrigins: string[];
+    /** Test seam: the stale-in-flight sweep period (default INFLIGHT_STALE_SWEEP_MS). */
+    inflightStaleSweepMs?: number;
+    /** Test seam: the age past which an un-acked delivery is logged (default INFLIGHT_STALE_AFTER_MS). */
+    inflightStaleAfterMs?: number;
+    /** Test seam: the clock the delivery ages are measured on. */
+    now?: () => number;
 }
+/**
+ * FB-P1-024 / #842 ruling §3: a stale-in-flight OBSERVATION, not a lease.
+ * The bridge cannot tell a message queued inside the consumer from one whose
+ * turn is running, so it must not requeue or cancel on age: a lease short
+ * enough to matter would re-run live turns (duplicate replies and side
+ * effects). It only logs `runtime_inbox.inflight_stale`, once per delivery,
+ * content-free, and takes NO action. The post-launch fix is protocol v2
+ * (`started` / `cancel` negotiated in `hello`), not a shorter threshold here.
+ */
+export declare const INFLIGHT_STALE_SWEEP_MS = 60000;
+export declare const INFLIGHT_STALE_AFTER_MS: number;
 export declare function attachAgentWebSocket(server: HttpServer, agent: BridgeAgent, opts: AgentWebSocketOptions): {
     close(): void;
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@securecoms/agent-bridge",
-  "version": "0.24.0",
+  "version": "0.25.1",
   "type": "module",
   "engines": {
     "node": ">=22.5.0"
@@ -37,17 +37,24 @@
     "test:watch": "vitest"
   },
   "dependencies": {
-    "@agentvault/crypto": "0.4.1",
+    "@hpke/chacha20poly1305": "^1.8.0",
+    "@hpke/core": "^1.8.0",
+    "@hpke/dhkem-x448": "^1.8.0",
+    "@hpke/hybridkem-x-wing": "^0.7.0",
+    "@hpke/ml-kem": "^0.3.0",
     "@noble/ciphers": "^1.3.0",
     "@noble/curves": "^1.9.7",
     "@noble/hashes": "^1.4.0",
+    "@noble/post-quantum": "^0.6.0",
     "ajv": "^8.18.0",
     "ajv-formats": "^3.0.1",
+    "libsodium-wrappers-sumo": "0.7.15",
     "ws": "^8.21.0",
     "zod": "^3.23.0"
   },
   "devDependencies": {
     "@agentvault/connect-core": "*",
+    "@agentvault/crypto": "0.4.1",
     "@types/node": "^22.0.0",
     "@types/ws": "^8.18.1",
     "esbuild": "0.24.0",