skapi-js 1.8.1 → 1.8.2

package/dist/skapi.d.mts

@@ -176,6 +176,17 @@ type RecordData = {
     };
     ip: string;
     readonly: boolean;
+    /**
+     * Present ONLY on an element of a postRecords() result that the backend refused.
+     * Such an element is an empty record (record_id is ""), and this carries the reason
+     * the backend gave, e.g. { code: 'NOT_EXISTS', message: 'Reference "..." does not exists.' }.
+     * A saved record never has it, so `record_id` stays the test for "did this save".
+     */
+    error?: {
+        code?: string;
+        message?: string;
+        [key: string]: any;
+    };
 };
 type Connection = {
     /** User's locale */
@@ -653,6 +664,17 @@ declare class Skapi {
     owner: string;
     session: Record<string, any> | null;
     connection: Connection | null;
+    /**
+     * unique_id -> record_id, bucketed by a "<service>/<owner>" scope key.
+     *
+     * The scope is mandatory. One Skapi instance routinely serves MANY services: the
+     * MCP server keeps a single instance per user and names the target project on every
+     * call, and the dashboard switches projects without reconstructing. A flat map let
+     * the same unique_id from two projects collide on one key, so a post carrying
+     * `reference: "src::<file>"` was silently rewritten to the OTHER project's
+     * record_id and the backend rejected it as non-existent. Never key this by
+     * unique_id alone, and never scope it by `this.service` when the call names its own.
+     */
     private __my_unique_ids;
     private __uniqueIdsPersistTimer;
     private userPool;

package/dist/skapi.d.ts

@@ -176,6 +176,17 @@ type RecordData = {
     };
     ip: string;
     readonly: boolean;
+    /**
+     * Present ONLY on an element of a postRecords() result that the backend refused.
+     * Such an element is an empty record (record_id is ""), and this carries the reason
+     * the backend gave, e.g. { code: 'NOT_EXISTS', message: 'Reference "..." does not exists.' }.
+     * A saved record never has it, so `record_id` stays the test for "did this save".
+     */
+    error?: {
+        code?: string;
+        message?: string;
+        [key: string]: any;
+    };
 };
 type Connection = {
     /** User's locale */
@@ -653,6 +664,17 @@ declare class Skapi {
     owner: string;
     session: Record<string, any> | null;
     connection: Connection | null;
+    /**
+     * unique_id -> record_id, bucketed by a "<service>/<owner>" scope key.
+     *
+     * The scope is mandatory. One Skapi instance routinely serves MANY services: the
+     * MCP server keeps a single instance per user and names the target project on every
+     * call, and the dashboard switches projects without reconstructing. A flat map let
+     * the same unique_id from two projects collide on one key, so a post carrying
+     * `reference: "src::<file>"` was silently rewritten to the OTHER project's
+     * record_id and the backend rejected it as non-existent. Never key this by
+     * unique_id alone, and never scope it by `this.service` when the call names its own.
+     */
     private __my_unique_ids;
     private __uniqueIdsPersistTimer;
     private userPool;