@ai-matrx/associations 0.9.33 → 0.10.0

package/dist/index.d.cts

@@ -400,6 +400,22 @@ interface DemandedRpcSignatures {
             title: string;
         }[];
     };
+    entity_row_create: {
+        Args: {
+            p_organization_id: string;
+            p_title: string;
+            p_token: string;
+        };
+        Returns: unknown;
+    };
+    entity_row_rename: {
+        Args: {
+            p_id: string;
+            p_title: string;
+            p_token: string;
+        };
+        Returns: unknown;
+    };
     cmt_list: {
         Args: {
             p_entity_id: string;
@@ -16424,27 +16440,6 @@ interface PgError {
     hint?: string | null;
 }
 
-/**
- * The minimal table surface entity-row create/rename needs (a structural
- * subset of supabase-js's query builder). Registry-convention writes go
- * DIRECT to the backing table (they are RLS-gated feature rows, not
- * association edges — there is no RPC for them by design).
- */
-interface AssociationsTableQuery {
-    insert(row: Record<string, unknown>): {
-        select(columns: string): {
-            single(): PromiseLike<{
-                data: unknown;
-                error: PgError | null;
-            }>;
-        };
-    };
-    update(patch: Record<string, unknown>): {
-        eq(column: string, value: string): PromiseLike<{
-            error: PgError | null;
-        }>;
-    };
-}
 /**
  * The data seam — a structural subset of `SupabaseClient<Database>`: any
  * client that can answer the demanded RPC families (README § The demanded
@@ -16452,22 +16447,21 @@ interface AssociationsTableQuery {
  * one. `PromiseLike` because supabase-js returns a thenable builder, not a
  * `Promise`.
  *
- * `from`/`schema` are OPTIONAL (W2, additive): only the entity-row
- * create/rename service uses them (generic registry-convention row writes).
- * A dataSource without them still satisfies every RPC operation; calling
- * entity-row create/rename against it returns a screamed `{ok:false}`
- * result naming the missing capability — never a silent no-op. A real
- * supabase-js client satisfies both structurally.
+ * 🚨 RPC AND NOTHING ELSE (DOORS-ONLY-4, 2026-09-21). This port used to carry
+ * OPTIONAL `from`/`schema` table surfaces, used by exactly one service —
+ * entity-row create/rename, which wrote the registered entity's backing table
+ * directly. The doors-only ruling (`platform` and `iam` are not client-writable;
+ * every write goes through a named SECURITY DEFINER door) made that path answer
+ * `42501` on every closed table, so it now calls `entity_row_create` /
+ * `entity_row_rename` like every other operation. With its one reader gone the
+ * two optional members were a port nobody reads — removed rather than left as a
+ * seam a future write could quietly reach for.
  */
 interface AssociationsDataSource {
     rpc(fn: DemandedRpcName, args: Record<string, unknown>): PromiseLike<{
         data: unknown;
         error: PgError | null;
     }>;
-    from?(table: string): AssociationsTableQuery;
-    schema?(name: string): {
-        from(table: string): AssociationsTableQuery;
-    };
 }
 /**
  * The identity seam — today a store-singleton read (`requireUserId`) plus the

package/dist/index.d.ts

@@ -400,6 +400,22 @@ interface DemandedRpcSignatures {
             title: string;
         }[];
     };
+    entity_row_create: {
+        Args: {
+            p_organization_id: string;
+            p_title: string;
+            p_token: string;
+        };
+        Returns: unknown;
+    };
+    entity_row_rename: {
+        Args: {
+            p_id: string;
+            p_title: string;
+            p_token: string;
+        };
+        Returns: unknown;
+    };
     cmt_list: {
         Args: {
             p_entity_id: string;
@@ -16424,27 +16440,6 @@ interface PgError {
     hint?: string | null;
 }
 
-/**
- * The minimal table surface entity-row create/rename needs (a structural
- * subset of supabase-js's query builder). Registry-convention writes go
- * DIRECT to the backing table (they are RLS-gated feature rows, not
- * association edges — there is no RPC for them by design).
- */
-interface AssociationsTableQuery {
-    insert(row: Record<string, unknown>): {
-        select(columns: string): {
-            single(): PromiseLike<{
-                data: unknown;
-                error: PgError | null;
-            }>;
-        };
-    };
-    update(patch: Record<string, unknown>): {
-        eq(column: string, value: string): PromiseLike<{
-            error: PgError | null;
-        }>;
-    };
-}
 /**
  * The data seam — a structural subset of `SupabaseClient<Database>`: any
  * client that can answer the demanded RPC families (README § The demanded
@@ -16452,22 +16447,21 @@ interface AssociationsTableQuery {
  * one. `PromiseLike` because supabase-js returns a thenable builder, not a
  * `Promise`.
  *
- * `from`/`schema` are OPTIONAL (W2, additive): only the entity-row
- * create/rename service uses them (generic registry-convention row writes).
- * A dataSource without them still satisfies every RPC operation; calling
- * entity-row create/rename against it returns a screamed `{ok:false}`
- * result naming the missing capability — never a silent no-op. A real
- * supabase-js client satisfies both structurally.
+ * 🚨 RPC AND NOTHING ELSE (DOORS-ONLY-4, 2026-09-21). This port used to carry
+ * OPTIONAL `from`/`schema` table surfaces, used by exactly one service —
+ * entity-row create/rename, which wrote the registered entity's backing table
+ * directly. The doors-only ruling (`platform` and `iam` are not client-writable;
+ * every write goes through a named SECURITY DEFINER door) made that path answer
+ * `42501` on every closed table, so it now calls `entity_row_create` /
+ * `entity_row_rename` like every other operation. With its one reader gone the
+ * two optional members were a port nobody reads — removed rather than left as a
+ * seam a future write could quietly reach for.
  */
 interface AssociationsDataSource {
     rpc(fn: DemandedRpcName, args: Record<string, unknown>): PromiseLike<{
         data: unknown;
         error: PgError | null;
     }>;
-    from?(table: string): AssociationsTableQuery;
-    schema?(name: string): {
-        from(table: string): AssociationsTableQuery;
-    };
 }
 /**
  * The identity seam — today a store-singleton read (`requireUserId`) plus the

package/dist/index.js

@@ -2122,6 +2122,8 @@ var DEMANDED_RPC_NAMES = [
   "ues_get_bulk",
   "ues_touch",
   "reference_search_candidates",
+  "entity_row_create",
+  "entity_row_rename",
   "cmt_list",
   "cmt_add",
   "cmt_edit",