wontopos 2.2.26 → 2.2.27

package/dist/wontopos.d.ts

@@ -418,7 +418,14 @@ export declare class Client {
     addBulk(content: string, userId?: string, category?: string, timestamp?: string, opts?: WriteOptions): Promise<StatusResult>;
     /** Supersede an old memory with new content. Payload first, userId last — same shape as add/search. */
     update(oldMemoryId: string, newContent: string, userId?: string, opts?: WriteOptions): Promise<UpdateResult>;
-    /** Semantic search over a store's memories. Returns memories, most relevant first. */
+    /** Semantic search over a store's memories. Returns memories, most relevant first.
+     *
+     *  `limit` bounds the MAIN lane, not the returned array. On a self-lane model
+     *  (Scroll 1.2+) the service answers in two disjoint lanes — the assistant's own
+     *  words come back separately — and both are returned here, so the array can hold
+     *  more than `limit`. They were retrieved and billed either way; dropping them would
+     *  only hide what you already paid for. Size a prompt window on the array you get
+     *  back, not on `limit`. `searchSelf()` hands the lanes back apart. */
     search(query: string, userId?: string, limit?: number, opts?: SearchOptions): Promise<Memory[]>;
     /** Search a self-memory model (Scroll 1.2+): both lanes from ONE call. Returns
      * `{ memories, self_memories }` — `memories` is the main lane (what others said /

package/dist/wontopos.js

@@ -37,7 +37,7 @@
  * runtime's (never disabled by this SDK; Node 18+ floors TLS at 1.2). Prefer
  * `Client.fromEnv()` over keys in source code.
  */
-const VERSION = "2.2.26";
+const VERSION = "2.2.27";
 /** Runtime info helps support debug a report ("node 18 on Windows...") —
  * platform only, never anything identifying. Browsers have no `process` (and
  * silently drop the UA header anyway). */
@@ -91,6 +91,17 @@ const IDEMPOTENCY_KEY_RE = /^[A-Za-z0-9._:\-]{1,128}$/;
 function normalizeStoreId(id) {
     return id.toLowerCase().replace(/[^a-z0-9_]/g, "_");
 }
+/** Ids already warned about, so each is reported once.
+ *
+ *  Bounded on purpose. The warning fires on ids that fold, and the shape it exists
+ *  to catch is an email — which this SDK's own documented pattern ("one store per
+ *  end user") turns into one entry PER USER, held for the life of the process and
+ *  never released, even when the client is. A server passing 50,000 user ids grew
+ *  this to 50,000 entries, a leak in exactly the case being warned about. A `Set`
+ *  keeps insertion order, so the oldest entry is the one evicted; dropping the
+ *  oldest rather than refusing new ones means a collision that first shows up late
+ *  still gets its one warning. */
+const WARNED_STORE_IDS_MAX = 1024;
 const warnedStoreIds = new Set();
 function warnIfStoreIdCollapses(id) {
     if (!id || warnedStoreIds.has(id))
@@ -99,6 +110,12 @@ function warnIfStoreIdCollapses(id) {
     if (normalized === id)
         return;
     warnedStoreIds.add(id);
+    while (warnedStoreIds.size > WARNED_STORE_IDS_MAX) {
+        const oldest = warnedStoreIds.values().next().value;
+        if (oldest === undefined)
+            break;
+        warnedStoreIds.delete(oldest);
+    }
     console.warn(`wontopos: store id ${JSON.stringify(id)} is stored as ${JSON.stringify(normalized)} ` +
         `(lowercased, and anything outside [a-z0-9_] becomes "_"). Ids that differ only by case or ` +
         `punctuation share ONE store and therefore one set of memories — if these ids come from your ` +
@@ -473,7 +490,14 @@ export class Client {
         return this.post("/api/v1/memory/supersede", { user_id: this.uid(userId), old_memory_id: oldMemoryId, new_content: newContent }, opts.idempotencyKey);
     }
     // ----- read -----
-    /** Semantic search over a store's memories. Returns memories, most relevant first. */
+    /** Semantic search over a store's memories. Returns memories, most relevant first.
+     *
+     *  `limit` bounds the MAIN lane, not the returned array. On a self-lane model
+     *  (Scroll 1.2+) the service answers in two disjoint lanes — the assistant's own
+     *  words come back separately — and both are returned here, so the array can hold
+     *  more than `limit`. They were retrieved and billed either way; dropping them would
+     *  only hide what you already paid for. Size a prompt window on the array you get
+     *  back, not on `limit`. `searchSelf()` hands the lanes back apart. */
     async search(query, userId, limit = 10, opts = {}) {
         // Reserved fields win over ...opts: an app that forwards untrusted input as
         // opts must not be able to override the store (user_id), query, or limit.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wontopos",
-  "version": "2.2.26",
+  "version": "2.2.27",
   "description": "Wontopos — long-term memory for AI agents. Pure semantic retrieval, identical recall in every language, ~100× lower LLM bill.",
   "keywords": [
     "memory",