@maximem/synap-js-sdk 0.4.5 → 0.4.7

package/dist/index.d.cts

@@ -597,6 +597,21 @@ interface CreateMemoryOptions {
     documentCreatedAt?: string | Date | null;
     mode?: IngestMode | string;
     metadata?: Json;
+    /**
+     * The level this memory belongs to, named in full, one entry per level down
+     * to it: `{ customer: "acme", team: "payments", user: "dana" }`.
+     *
+     * Only needed by an account whose scope ladder has a level between its
+     * customer and its user levels. `user_id` and `customer_id` cannot say which
+     * one a write belongs to, so on such a ladder the server refuses the write
+     * rather than guessing: a wrong guess at or above the customer level crosses
+     * a tenant boundary.
+     *
+     * Omit it and nothing changes. Sending one to an account without nested
+     * scoping is an error rather than ignored, because a caller who asks to be
+     * narrowed and is ignored gets widened instead.
+     */
+    scope?: Record<string, string> | null;
 }
 /**
  * Mirrors Python's `CreateMemoryResponse`.
@@ -672,6 +687,21 @@ interface CreateFromFileOptions {
     documentType?: string;
     mode?: IngestMode | string;
     metadata?: Json;
+    /**
+     * The level this memory belongs to, named in full, one entry per level down
+     * to it: `{ customer: "acme", team: "payments", user: "dana" }`.
+     *
+     * Only needed by an account whose scope ladder has a level between its
+     * customer and its user levels. `user_id` and `customer_id` cannot say which
+     * one a write belongs to, so on such a ladder the server refuses the write
+     * rather than guessing: a wrong guess at or above the customer level crosses
+     * a tenant boundary.
+     *
+     * Omit it and nothing changes. Sending one to an account without nested
+     * scoping is an error rather than ignored, because a caller who asks to be
+     * narrowed and is ignored gets widened instead.
+     */
+    scope?: Record<string, string> | null;
 }
 interface UpdateMemoryOptions {
     memory_id?: string;
@@ -1190,8 +1220,8 @@ interface SynapClientOptions {
      * matching Python's `st_verbatim_overlay`. `SYNAP_ST_VERBATIM_OVERLAY`
      * overrides this either way.
      */
-    st_verbatim_overlay?: boolean;
-    stVerbatimOverlay?: boolean;
+    st_verbatim_overlay?: boolean | undefined;
+    stVerbatimOverlay?: boolean | undefined;
     /**
      * Let the SDK answer `get_context_for_prompt` and `get_compacted` from its
      * own short-term store when the conversation is warm, skipping the cloud
@@ -1200,13 +1230,13 @@ interface SynapClientOptions {
      * This is the COST switch. `st_verbatim_overlay` is the correctness one and
      * is independent of it.
      */
-    sdk_st_authoritative?: boolean;
-    sdkStAuthoritative?: boolean;
+    sdk_st_authoritative?: boolean | undefined;
+    sdkStAuthoritative?: boolean | undefined;
     /**
      * Where the SDK's diagnostics go. Defaults to `console.warn` prefixed with
      * `[synap]`. Pass a no-op to silence them, or your own logger to route them.
      */
-    logger?: SynapLogger;
+    logger?: SynapLogger | undefined;
     /**
      * Bypass the process registry and build a genuinely separate client.
      *
@@ -1241,7 +1271,7 @@ interface ConfigureOptions {
     /** Accepted and ignored. Python-only. */
     log_level?: string;
     /** Replaces the diagnostic sink, same as the constructor option. */
-    logger?: SynapLogger;
+    logger?: SynapLogger | undefined;
 }
 /** Options for the cross-scope `fetch()`. Snake_case, matching Python's kwargs. */
 interface UnifiedFetchOptions {

package/dist/index.d.ts

@@ -597,6 +597,21 @@ interface CreateMemoryOptions {
     documentCreatedAt?: string | Date | null;
     mode?: IngestMode | string;
     metadata?: Json;
+    /**
+     * The level this memory belongs to, named in full, one entry per level down
+     * to it: `{ customer: "acme", team: "payments", user: "dana" }`.
+     *
+     * Only needed by an account whose scope ladder has a level between its
+     * customer and its user levels. `user_id` and `customer_id` cannot say which
+     * one a write belongs to, so on such a ladder the server refuses the write
+     * rather than guessing: a wrong guess at or above the customer level crosses
+     * a tenant boundary.
+     *
+     * Omit it and nothing changes. Sending one to an account without nested
+     * scoping is an error rather than ignored, because a caller who asks to be
+     * narrowed and is ignored gets widened instead.
+     */
+    scope?: Record<string, string> | null;
 }
 /**
  * Mirrors Python's `CreateMemoryResponse`.
@@ -672,6 +687,21 @@ interface CreateFromFileOptions {
     documentType?: string;
     mode?: IngestMode | string;
     metadata?: Json;
+    /**
+     * The level this memory belongs to, named in full, one entry per level down
+     * to it: `{ customer: "acme", team: "payments", user: "dana" }`.
+     *
+     * Only needed by an account whose scope ladder has a level between its
+     * customer and its user levels. `user_id` and `customer_id` cannot say which
+     * one a write belongs to, so on such a ladder the server refuses the write
+     * rather than guessing: a wrong guess at or above the customer level crosses
+     * a tenant boundary.
+     *
+     * Omit it and nothing changes. Sending one to an account without nested
+     * scoping is an error rather than ignored, because a caller who asks to be
+     * narrowed and is ignored gets widened instead.
+     */
+    scope?: Record<string, string> | null;
 }
 interface UpdateMemoryOptions {
     memory_id?: string;
@@ -1190,8 +1220,8 @@ interface SynapClientOptions {
      * matching Python's `st_verbatim_overlay`. `SYNAP_ST_VERBATIM_OVERLAY`
      * overrides this either way.
      */
-    st_verbatim_overlay?: boolean;
-    stVerbatimOverlay?: boolean;
+    st_verbatim_overlay?: boolean | undefined;
+    stVerbatimOverlay?: boolean | undefined;
     /**
      * Let the SDK answer `get_context_for_prompt` and `get_compacted` from its
      * own short-term store when the conversation is warm, skipping the cloud
@@ -1200,13 +1230,13 @@ interface SynapClientOptions {
      * This is the COST switch. `st_verbatim_overlay` is the correctness one and
      * is independent of it.
      */
-    sdk_st_authoritative?: boolean;
-    sdkStAuthoritative?: boolean;
+    sdk_st_authoritative?: boolean | undefined;
+    sdkStAuthoritative?: boolean | undefined;
     /**
      * Where the SDK's diagnostics go. Defaults to `console.warn` prefixed with
      * `[synap]`. Pass a no-op to silence them, or your own logger to route them.
      */
-    logger?: SynapLogger;
+    logger?: SynapLogger | undefined;
     /**
      * Bypass the process registry and build a genuinely separate client.
      *
@@ -1241,7 +1271,7 @@ interface ConfigureOptions {
     /** Accepted and ignored. Python-only. */
     log_level?: string;
     /** Replaces the diagnostic sink, same as the constructor option. */
-    logger?: SynapLogger;
+    logger?: SynapLogger | undefined;
 }
 /** Options for the cross-scope `fetch()`. Snake_case, matching Python's kwargs. */
 interface UnifiedFetchOptions {

package/dist/index.js

@@ -853,6 +853,10 @@ function buildCreateBody(options) {
     ),
     user_id: either(o2, "user_id", "userId") ?? null,
     customer_id: either(o2, "customer_id", "customerId") ?? null,
+    // null, never `{}`. An empty path is not absence: the server treats one as
+    // an error, because a caller asking to be narrowed and being ignored gets
+    // widened instead.
+    scope: options.scope ?? null,
     mode,
     metadata: options.metadata ?? {}
   };