@memnexus-ai/typescript-sdk 1.59.18 → 1.59.19

package/dist/index.d.cts

@@ -10625,9 +10625,12 @@ declare class MemoriesService extends BaseService {
      * Atomically append a block to a named memory
      * Atomically appends a text block to a named memory, eliminating the
   read-modify-write clobber that concurrent full-content updates cause on
-  shared named memories. The server reads the current head, concatenates
-  `existing + separator + block`, and writes a new version under the
-  NameLock with an internal compare-and-swap + bounded retry — so
+  shared named memories. Each append runs inside a single transaction that
+  holds the per-name NameLock end to end: it acquires the lock, reads the
+  current head UNDER the lock, concatenates `existing + separator + block`,
+  and writes the new version — all before releasing the lock. Concurrent
+  appends therefore QUEUE on the lock and serialize (the same mechanism the
+  full-content PUT path uses); there is no compare-and-swap retry loop, so
   simultaneous appends all survive and the client needs no retry logic.
   Content is decrypted, assembled, size-checked, and re-encrypted
   server-side; plaintext is never returned to other callers.

package/dist/index.d.ts

@@ -10625,9 +10625,12 @@ declare class MemoriesService extends BaseService {
      * Atomically append a block to a named memory
      * Atomically appends a text block to a named memory, eliminating the
   read-modify-write clobber that concurrent full-content updates cause on
-  shared named memories. The server reads the current head, concatenates
-  `existing + separator + block`, and writes a new version under the
-  NameLock with an internal compare-and-swap + bounded retry — so
+  shared named memories. Each append runs inside a single transaction that
+  holds the per-name NameLock end to end: it acquires the lock, reads the
+  current head UNDER the lock, concatenates `existing + separator + block`,
+  and writes the new version — all before releasing the lock. Concurrent
+  appends therefore QUEUE on the lock and serialize (the same mechanism the
+  full-content PUT path uses); there is no compare-and-swap retry loop, so
   simultaneous appends all survive and the client needs no retry logic.
   Content is decrypted, assembled, size-checked, and re-encrypted
   server-side; plaintext is never returned to other callers.

package/dist/index.js

@@ -3356,9 +3356,12 @@ var MemoriesService = class extends BaseService {
      * Atomically append a block to a named memory
      * Atomically appends a text block to a named memory, eliminating the
   read-modify-write clobber that concurrent full-content updates cause on
-  shared named memories. The server reads the current head, concatenates
-  `existing + separator + block`, and writes a new version under the
-  NameLock with an internal compare-and-swap + bounded retry — so
+  shared named memories. Each append runs inside a single transaction that
+  holds the per-name NameLock end to end: it acquires the lock, reads the
+  current head UNDER the lock, concatenates `existing + separator + block`,
+  and writes the new version — all before releasing the lock. Concurrent
+  appends therefore QUEUE on the lock and serialize (the same mechanism the
+  full-content PUT path uses); there is no compare-and-swap retry loop, so
   simultaneous appends all survive and the client needs no retry logic.
   Content is decrypted, assembled, size-checked, and re-encrypted
   server-side; plaintext is never returned to other callers.