@memnexus-ai/sdk 1.59.4 → 1.59.6

package/dist/index.cjs

@@ -1353,7 +1353,12 @@ var Memories = class {
    *
    * Same as POST /api/memories/digest but uses Server-Sent Events (SSE) to stream
    * the response. Sends `: heartbeat` comments every 10 seconds during processing
-   * to prevent gateway read-timeout (default 60s) from killing long-running digests.
+   * to keep long-running digests alive across gateway and client idle timeouts. The
+   * effective dev gateway budget is the ingress proxy-read-timeout (600s in dev per
+   * api-gateway/k8s/deploy/values-dev.yaml, which overrides the platform-infra 60s
+   * default). kong.yaml declares a 60s read_timeout but it was empirically
+   * non-binding in dev as of 2026-07-06 (a 104.8s digest returned 200). Heartbeats
+   * remain useful for client-side/UX idle-timeout behavior regardless.
    * 
    * **Event sequence:**
    * - `: heartbeat` — keep-alive comment, sent every 10s during processing

package/dist/index.d.cts

@@ -2773,7 +2773,12 @@ declare class Memories {
      *
      * Same as POST /api/memories/digest but uses Server-Sent Events (SSE) to stream
      * the response. Sends `: heartbeat` comments every 10 seconds during processing
-     * to prevent gateway read-timeout (default 60s) from killing long-running digests.
+     * to keep long-running digests alive across gateway and client idle timeouts. The
+     * effective dev gateway budget is the ingress proxy-read-timeout (600s in dev per
+     * api-gateway/k8s/deploy/values-dev.yaml, which overrides the platform-infra 60s
+     * default). kong.yaml declares a 60s read_timeout but it was empirically
+     * non-binding in dev as of 2026-07-06 (a 104.8s digest returned 200). Heartbeats
+     * remain useful for client-side/UX idle-timeout behavior regardless.
      *
      * **Event sequence:**
      * - `: heartbeat` — keep-alive comment, sent every 10s during processing

package/dist/index.d.ts

@@ -2773,7 +2773,12 @@ declare class Memories {
      *
      * Same as POST /api/memories/digest but uses Server-Sent Events (SSE) to stream
      * the response. Sends `: heartbeat` comments every 10 seconds during processing
-     * to prevent gateway read-timeout (default 60s) from killing long-running digests.
+     * to keep long-running digests alive across gateway and client idle timeouts. The
+     * effective dev gateway budget is the ingress proxy-read-timeout (600s in dev per
+     * api-gateway/k8s/deploy/values-dev.yaml, which overrides the platform-infra 60s
+     * default). kong.yaml declares a 60s read_timeout but it was empirically
+     * non-binding in dev as of 2026-07-06 (a 104.8s digest returned 200). Heartbeats
+     * remain useful for client-side/UX idle-timeout behavior regardless.
      *
      * **Event sequence:**
      * - `: heartbeat` — keep-alive comment, sent every 10s during processing

package/dist/index.js

@@ -1326,7 +1326,12 @@ var Memories = class {
    *
    * Same as POST /api/memories/digest but uses Server-Sent Events (SSE) to stream
    * the response. Sends `: heartbeat` comments every 10 seconds during processing
-   * to prevent gateway read-timeout (default 60s) from killing long-running digests.
+   * to keep long-running digests alive across gateway and client idle timeouts. The
+   * effective dev gateway budget is the ingress proxy-read-timeout (600s in dev per
+   * api-gateway/k8s/deploy/values-dev.yaml, which overrides the platform-infra 60s
+   * default). kong.yaml declares a 60s read_timeout but it was empirically
+   * non-binding in dev as of 2026-07-06 (a 104.8s digest returned 200). Heartbeats
+   * remain useful for client-side/UX idle-timeout behavior regardless.
    * 
    * **Event sequence:**
    * - `: heartbeat` — keep-alive comment, sent every 10s during processing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memnexus-ai/sdk",
-  "version": "1.59.4",
+  "version": "1.59.6",
   "description": "Official Node.js SDK for the MemNexus API",
   "license": "Proprietary",
   "type": "module",