@nicia-ai/typegraph 0.48.0 → 0.50.0

package/dist/{index-D7d1u2gr.d.ts → index-B0PrmE3K.d.cts}

@@ -1,5 +1,5 @@
-import { bj as KindEntity } from './types-BqFZTQmV.js';
-import { M as MaterializeIndexesResult, S as SchemaDiff } from './materialize-indexes-DJ3ykH59.js';
+import { bt as KindEntity } from './types-CWg4dTjj.cjs';
+import { M as MaterializeIndexesResult, S as SchemaDiff } from './materialize-indexes-CrSiW_lT.cjs';
 
 /**
  * TypeGraph Error Hierarchy
@@ -325,6 +325,20 @@ type UniquenessErrorDetails = Readonly<{
     existingId: string;
     newId: string;
     fields: readonly string[];
+    /**
+     * The claim row's `node_kind` — the axis this violation was found at.
+     * Optional so a third-party backend implementing the documented "throws
+     * `UniquenessError`" contract keeps working unchanged; when a throw site
+     * omits it, a caller loses only the disambiguation this field exists for,
+     * never correctness of the refusal itself.
+     *
+     * `constraintName` alone cannot tell two disjoint pairs apart — every
+     * `disjointWith` pair shares the single reserved `DISJOINT_CONSTRAINT_NAME`
+     * — so `mapClaimRefusal` (`store/claims/node-claims.ts`) matches on this
+     * field together with `constraintName` and the key, which is exactly the
+     * claim row's primary key and therefore unambiguous.
+     */
+    axis?: string;
 }>;
 /**
  * Thrown when uniqueness constraint is violated.

package/dist/{index-COs_z6nV.d.cts → index-CwcXsL5R.d.ts}

@@ -1,5 +1,5 @@
-import { bj as KindEntity } from './types-BqFZTQmV.cjs';
-import { M as MaterializeIndexesResult, S as SchemaDiff } from './materialize-indexes-DTtAnvfY.cjs';
+import { bt as KindEntity } from './types-CWg4dTjj.js';
+import { M as MaterializeIndexesResult, S as SchemaDiff } from './materialize-indexes-C9GG3O3C.js';
 
 /**
  * TypeGraph Error Hierarchy
@@ -325,6 +325,20 @@ type UniquenessErrorDetails = Readonly<{
     existingId: string;
     newId: string;
     fields: readonly string[];
+    /**
+     * The claim row's `node_kind` — the axis this violation was found at.
+     * Optional so a third-party backend implementing the documented "throws
+     * `UniquenessError`" contract keeps working unchanged; when a throw site
+     * omits it, a caller loses only the disambiguation this field exists for,
+     * never correctness of the refusal itself.
+     *
+     * `constraintName` alone cannot tell two disjoint pairs apart — every
+     * `disjointWith` pair shares the single reserved `DISJOINT_CONSTRAINT_NAME`
+     * — so `mapClaimRefusal` (`store/claims/node-claims.ts`) matches on this
+     * field together with `constraintName` and the key, which is exactly the
+     * claim row's primary key and therefore unambiguous.
+     */
+    axis?: string;
 }>;
 /**
  * Thrown when uniqueness constraint is violated.