@bettercms-ai/kit 2.0.0-next.6 → 2.0.0-next.7

package/dist/testing/coverage-extras.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Coverage extras: kit-own entries for what V2's corpus never exercises, kept OUT of the corpus (which stays V2
+ * verbatim: catalog-copy.test). coverageOf reports them as their own row, so the type count reads "28/29 from V2,
+ * json via extras" and never passes off a kit fixture as V2's. Each extra runs the same gates as a corpus entry.
+ */
+import type { CatalogItem } from "../library/catalog";
+/** V2's corpus has no `json` field: one entry holds one, with a nested value, so the adapters and the dock carry it. */
+export declare const COVERAGE_EXTRAS: CatalogItem[];

package/dist/testing/coverage-extras.js

@@ -0,0 +1,44 @@
+//#region src/testing/coverage-extras.ts
+/** V2's corpus has no `json` field: one entry holds one, with a nested value, so the adapters and the dock carry it. */
+var COVERAGE_EXTRAS = [{
+	id: "extra-json-field",
+	core: false,
+	category: "Advanced patterns",
+	tags: [],
+	hay: "json value extra",
+	ex: {
+		id: "extra-json-field",
+		label: "Raw JSON value",
+		proves: "A json field (the one type V2's corpus never uses) is carried by both lanes and edited in the dock",
+		schema: {
+			name: "jsonSettings",
+			title: "JSON settings",
+			kind: "object",
+			fields: [{
+				name: "title",
+				title: "Title",
+				type: "string"
+			}, {
+				name: "settings",
+				title: "Settings",
+				type: "json",
+				description: "Raw settings the site reads as they are."
+			}]
+		},
+		value: {
+			title: "Map widget",
+			settings: {
+				zoom: 12,
+				center: [52.37, 4.9],
+				layers: ["streets", {
+					id: "pins",
+					visible: true
+				}]
+			}
+		}
+	}
+}];
+//#endregion
+export { COVERAGE_EXTRAS };
+
+//# sourceMappingURL=coverage-extras.js.map

package/dist/testing/coverage-extras.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"coverage-extras.js","names":[],"sources":["../../src/testing/coverage-extras.ts"],"sourcesContent":["/**\n * Coverage extras: kit-own entries for what V2's corpus never exercises, kept OUT of the corpus (which stays V2\n * verbatim: catalog-copy.test). coverageOf reports them as their own row, so the type count reads \"28/29 from V2,\n * json via extras\" and never passes off a kit fixture as V2's. Each extra runs the same gates as a corpus entry.\n */\nimport type { CatalogItem } from \"../library/catalog\";\n\n/** V2's corpus has no `json` field: one entry holds one, with a nested value, so the adapters and the dock carry it. */\nexport const COVERAGE_EXTRAS: CatalogItem[] = [\n  {\n    id: \"extra-json-field\",\n    core: false,\n    category: \"Advanced patterns\",\n    tags: [],\n    hay: \"json value extra\",\n    ex: {\n      id: \"extra-json-field\",\n      label: \"Raw JSON value\",\n      proves: \"A json field (the one type V2's corpus never uses) is carried by both lanes and edited in the dock\",\n      schema: {\n        name: \"jsonSettings\",\n        title: \"JSON settings\",\n        kind: \"object\",\n        fields: [\n          { name: \"title\", title: \"Title\", type: \"string\" },\n          { name: \"settings\", title: \"Settings\", type: \"json\", description: \"Raw settings the site reads as they are.\" },\n        ],\n      },\n      value: { title: \"Map widget\", settings: { zoom: 12, center: [52.37, 4.9], layers: [\"streets\", { id: \"pins\", visible: true }] } },\n    },\n  },\n];\n"],"mappings":";;AAQA,IAAa,kBAAiC,CAC5C;CACE,IAAI;CACJ,MAAM;CACN,UAAU;CACV,MAAM,CAAC;CACP,KAAK;CACL,IAAI;EACF,IAAI;EACJ,OAAO;EACP,QAAQ;EACR,QAAQ;GACN,MAAM;GACN,OAAO;GACP,MAAM;GACN,QAAQ,CACN;IAAE,MAAM;IAAS,OAAO;IAAS,MAAM;GAAS,GAChD;IAAE,MAAM;IAAY,OAAO;IAAY,MAAM;IAAQ,aAAa;GAA2C,CAC/G;EACF;EACA,OAAO;GAAE,OAAO;GAAc,UAAU;IAAE,MAAM;IAAI,QAAQ,CAAC,OAAO,GAAG;IAAG,QAAQ,CAAC,WAAW;KAAE,IAAI;KAAQ,SAAS;IAAK,CAAC;GAAE;EAAE;CACjI;AACF,CACF"}

package/dist/testing/exclusions.d.ts

@@ -0,0 +1,30 @@
+export interface KitExclusion {
+    id: string;
+    plane: "schema" | "value";
+    /** the lossy feature it signs (adapters/lossy.ts FEATURES), or a backend rule's code */
+    feature?: string;
+    key?: string;
+    /** only this part of the feature (e.g. the Shopify subset of reference targets) */
+    pattern?: string;
+    reason: string;
+    signedBy: string;
+}
+export interface KitEquivalence {
+    id: string;
+    /** value: a stored value moved; schema: a definition key whose effect another key carries (its `feature` is not loss) */
+    plane: "schema" | "value";
+    /** schema plane: the lossy feature (adapters/lossy.ts CATALOG) the move accounts for */
+    feature?: string;
+    key: string;
+    /** where prod holds the fact instead */
+    moves: string;
+    /** what the gate's proof checks to read it back */
+    recovery: string;
+    /** schema plane: the V2 source (or the gate) that shows the key has no effect of its own, or where it is carried */
+    proof?: string;
+    /** the write that carries the fact (a planner): the gates measure it rather than exclude the feature */
+    carriedBy?: string;
+    ruledBy?: string;
+}
+export declare const EXCLUSIONS: KitExclusion[];
+export declare const EQUIVALENCES: KitEquivalence[];

package/dist/testing/exclusions.js

@@ -0,0 +1,13 @@
+import exclusions_v1_default from "../ledgers/exclusions.v1.js";
+//#region src/testing/exclusions.ts
+/**
+* The exclusions ledger (ledgers/exclusions.v1.json), for the gates that hold the V2 → prod mapping to it: a lost key
+* is an owner-signed exclusion or a proven equivalence (a representation move), never anything else. The dashboard's
+* kitCorpusDock gate reads it from here.
+*/
+var EXCLUSIONS = exclusions_v1_default.exclusions;
+var EQUIVALENCES = exclusions_v1_default.equivalences;
+//#endregion
+export { EQUIVALENCES, EXCLUSIONS };
+
+//# sourceMappingURL=exclusions.js.map

package/dist/testing/exclusions.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"exclusions.js","names":[],"sources":["../../src/testing/exclusions.ts"],"sourcesContent":["/**\n * The exclusions ledger (ledgers/exclusions.v1.json), for the gates that hold the V2 → prod mapping to it: a lost key\n * is an owner-signed exclusion or a proven equivalence (a representation move), never anything else. The dashboard's\n * kitCorpusDock gate reads it from here.\n */\nimport ledger from \"../../ledgers/exclusions.v1.json\";\n\nexport interface KitExclusion {\n  id: string;\n  plane: \"schema\" | \"value\";\n  /** the lossy feature it signs (adapters/lossy.ts FEATURES), or a backend rule's code */\n  feature?: string;\n  key?: string;\n  /** only this part of the feature (e.g. the Shopify subset of reference targets) */\n  pattern?: string;\n  reason: string;\n  signedBy: string;\n}\n\nexport interface KitEquivalence {\n  id: string;\n  /** value: a stored value moved; schema: a definition key whose effect another key carries (its `feature` is not loss) */\n  plane: \"schema\" | \"value\";\n  /** schema plane: the lossy feature (adapters/lossy.ts CATALOG) the move accounts for */\n  feature?: string;\n  key: string;\n  /** where prod holds the fact instead */\n  moves: string;\n  /** what the gate's proof checks to read it back */\n  recovery: string;\n  /** schema plane: the V2 source (or the gate) that shows the key has no effect of its own, or where it is carried */\n  proof?: string;\n  /** the write that carries the fact (a planner): the gates measure it rather than exclude the feature */\n  carriedBy?: string;\n  ruledBy?: string;\n}\n\nexport const EXCLUSIONS = ledger.exclusions as KitExclusion[];\nexport const EQUIVALENCES = ledger.equivalences as KitEquivalence[];\n"],"mappings":";;;;;;;AAqCA,IAAa,aAAa,sBAAO;AACjC,IAAa,eAAe,sBAAO"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bettercms-ai/kit",
-  "version": "2.0.0-next.6",
+  "version": "2.0.0-next.7",
   "description": "The BetterCMS V2 Block Kit: schema language, form engine, controls and design tokens.",
   "license": "MIT",
   "type": "module",
@@ -73,7 +73,7 @@
   },
   "peerDependencies": {
     "@base-ui/react": "^1.4.1",
-    "@bettercms-ai/types": "^1.56.0",
+    "@bettercms-ai/types": "^1.59.0",
     "@tabler/icons-react": "^3.48.0",
     "framer-motion": "^12.40.0",
     "react": "^19.2.0",