@specverse/engines 4.1.22 → 4.1.23

package/dist/inference/ui-contracts/rules/delete-reflects-in-list.js

@@ -0,0 +1,50 @@
+/**
+ * Rule: delete-reflects-in-list
+ *
+ * Mirror of create-reflects-in-list, for the delete path. Seeds an
+ * entity via backend POST, asserts it appears in the list, then
+ * deletes it via backend DELETE and asserts it disappears. The
+ * disappear-after-delete check exercises the full state-sync chain:
+ * backend publishes a Deleted event → WebSocket pushes to frontend
+ * → useEntitySync invalidates the ['entities', modelName] query key
+ * → React Query refetches → the list view re-renders without the
+ * deleted row.
+ *
+ * If any link in that chain is broken (e.g. the mutation hook
+ * forgets to invalidate, or the WebSocket bridge drops the event),
+ * this test is the one that catches it.
+ *
+ * One TestCase per seedable model.
+ */
+import { pickDisplayAttribute, buildSeedData } from './_shared.js';
+export const RULE_ID = 'delete-reflects-in-list';
+export const deleteReflectsInList = (spec) => {
+    const cases = [];
+    for (const model of spec.models) {
+        const display = pickDisplayAttribute(model);
+        if (!display)
+            continue;
+        const marker = `ct-delete-${model.name}`;
+        const seedData = buildSeedData(model, marker);
+        if (!seedData)
+            continue;
+        const displayValue = seedData[display.name];
+        if (typeof displayValue !== 'string')
+            continue;
+        cases.push({
+            ruleId: RULE_ID,
+            specElement: model.name,
+            name: `[${RULE_ID}] deleting a ${model.name} removes it from its list view`,
+            steps: [
+                { action: 'bootRuntime' },
+                { action: 'navigateToModel', modelName: model.name },
+                { action: 'createEntity', modelName: model.name, data: seedData, bindAs: 'id' },
+                { action: 'expectEntityInList', modelName: model.name, displayValue },
+                { action: 'deleteEntity', modelName: model.name, idExpr: 'id' },
+                { action: 'expectEntityAbsent', modelName: model.name, displayValue },
+            ],
+        });
+    }
+    return cases;
+};
+//# sourceMappingURL=delete-reflects-in-list.js.map

package/dist/inference/ui-contracts/rules/delete-reflects-in-list.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"delete-reflects-in-list.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/delete-reflects-in-list.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAGH,OAAO,EAAE,oBAAoB,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AAEnE,MAAM,CAAC,MAAM,OAAO,GAAG,yBAAyB,CAAC;AAEjD,MAAM,CAAC,MAAM,oBAAoB,GAAmB,CAAC,IAAoB,EAAc,EAAE;IACvF,MAAM,KAAK,GAAe,EAAE,CAAC;IAC7B,KAAK,MAAM,KAAK,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;QAChC,MAAM,OAAO,GAAG,oBAAoB,CAAC,KAAK,CAAC,CAAC;QAC5C,IAAI,CAAC,OAAO;YAAE,SAAS;QACvB,MAAM,MAAM,GAAG,aAAa,KAAK,CAAC,IAAI,EAAE,CAAC;QACzC,MAAM,QAAQ,GAAG,aAAa,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC;QAC9C,IAAI,CAAC,QAAQ;YAAE,SAAS;QACxB,MAAM,YAAY,GAAG,QAAQ,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;QAC5C,IAAI,OAAO,YAAY,KAAK,QAAQ;YAAE,SAAS;QAE/C,KAAK,CAAC,IAAI,CAAC;YACT,MAAM,EAAE,OAAO;YACf,WAAW,EAAE,KAAK,CAAC,IAAI;YACvB,IAAI,EAAE,IAAI,OAAO,gBAAgB,KAAK,CAAC,IAAI,gCAAgC;YAC3E,KAAK,EAAE;gBACL,EAAE,MAAM,EAAE,aAAa,EAAE;gBACzB,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;gBACpD,EAAE,MAAM,EAAE,cAAc,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,IAAI,EAAE;gBAC/E,EAAE,MAAM,EAAE,oBAAoB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,YAAY,EAAE;gBACrE,EAAE,MAAM,EAAE,cAAc,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE;gBAC/D,EAAE,MAAM,EAAE,oBAAoB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,YAAY,EAAE;aACtE;SACF,CAAC,CAAC;IACL,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC,CAAC"}

package/dist/inference/ui-contracts/rules/detail-view-renders.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Rule: detail-view-renders
+ *
+ * For every model, boot the runtime, navigate to the model, and verify
+ * no error boundary is shown even when the model has zero instances
+ * (the empty state is still a render that can crash).
+ *
+ * Distinct from list-view-renders because v1's navigateToModel lands
+ * on the list by default, not the detail. In practice both rules
+ * currently exercise the same nav-click + no-error assertion; when
+ * detail views get their own dedicated entry point in the DevShell,
+ * this rule will diverge to target that path specifically.
+ *
+ * Kept as its own rule for two reasons:
+ *   1. Failure attribution is clearer — a broken detail template
+ *      fails this rule but not `list-view-renders`.
+ *   2. The rule stays stable across harness evolution — when we add
+ *      a `navigateToDetail` helper, only this rule's step changes,
+ *      not the entire test surface.
+ */
+import type { UiContractRule } from '../test-case-types.js';
+export declare const RULE_ID = "detail-view-renders";
+export declare const detailViewRenders: UiContractRule;
+//# sourceMappingURL=detail-view-renders.d.ts.map

package/dist/inference/ui-contracts/rules/detail-view-renders.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"detail-view-renders.d.ts","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/detail-view-renders.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,OAAO,KAAK,EAAE,cAAc,EAA4B,MAAM,uBAAuB,CAAC;AAEtF,eAAO,MAAM,OAAO,wBAAwB,CAAC;AAE7C,eAAO,MAAM,iBAAiB,EAAE,cAW/B,CAAC"}

package/dist/inference/ui-contracts/rules/detail-view-renders.js

@@ -0,0 +1,34 @@
+/**
+ * Rule: detail-view-renders
+ *
+ * For every model, boot the runtime, navigate to the model, and verify
+ * no error boundary is shown even when the model has zero instances
+ * (the empty state is still a render that can crash).
+ *
+ * Distinct from list-view-renders because v1's navigateToModel lands
+ * on the list by default, not the detail. In practice both rules
+ * currently exercise the same nav-click + no-error assertion; when
+ * detail views get their own dedicated entry point in the DevShell,
+ * this rule will diverge to target that path specifically.
+ *
+ * Kept as its own rule for two reasons:
+ *   1. Failure attribution is clearer — a broken detail template
+ *      fails this rule but not `list-view-renders`.
+ *   2. The rule stays stable across harness evolution — when we add
+ *      a `navigateToDetail` helper, only this rule's step changes,
+ *      not the entire test surface.
+ */
+export const RULE_ID = 'detail-view-renders';
+export const detailViewRenders = (spec) => {
+    return spec.models.map(model => ({
+        ruleId: RULE_ID,
+        specElement: model.name,
+        name: `[${RULE_ID}] ${model.name} detail view renders without errors (empty state ok)`,
+        steps: [
+            { action: 'bootRuntime' },
+            { action: 'navigateToModel', modelName: model.name },
+            { action: 'expectViewRenders' },
+        ],
+    }));
+};
+//# sourceMappingURL=detail-view-renders.js.map

package/dist/inference/ui-contracts/rules/detail-view-renders.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"detail-view-renders.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/detail-view-renders.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAIH,MAAM,CAAC,MAAM,OAAO,GAAG,qBAAqB,CAAC;AAE7C,MAAM,CAAC,MAAM,iBAAiB,GAAmB,CAAC,IAAoB,EAAc,EAAE;IACpF,OAAO,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;QAC/B,MAAM,EAAE,OAAO;QACf,WAAW,EAAE,KAAK,CAAC,IAAI;QACvB,IAAI,EAAE,IAAI,OAAO,KAAK,KAAK,CAAC,IAAI,sDAAsD;QACtF,KAAK,EAAE;YACL,EAAE,MAAM,EAAE,aAAa,EAAE;YACzB,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;YACpD,EAAE,MAAM,EAAE,mBAAmB,EAAE;SAChC;KACF,CAAC,CAAC,CAAC;AACN,CAAC,CAAC"}

package/dist/inference/ui-contracts/rules/evolve-reflects-in-list.d.ts

@@ -0,0 +1,21 @@
+/**
+ * Rule: evolve-reflects-in-list
+ *
+ * For every model with a lifecycle, seed an entity in the initial
+ * state, transition it to the next state via backend PATCH, and
+ * assert the list view reflects the new state. This exercises the
+ * lifecycle mutation path through the same state-sync contract as
+ * create/delete.
+ *
+ * Uses the first → second state transition from the lifecycle flow.
+ * If the lifecycle has fewer than two states, the rule produces no
+ * test case for that model.
+ *
+ * One TestCase per (seedable, lifecycled) model. For poll-app: Poll
+ * has a lifecycle with states draft → open → closed, so a single
+ * test covers the draft → open transition.
+ */
+import type { UiContractRule } from '../test-case-types.js';
+export declare const RULE_ID = "evolve-reflects-in-list";
+export declare const evolveReflectsInList: UiContractRule;
+//# sourceMappingURL=evolve-reflects-in-list.d.ts.map

package/dist/inference/ui-contracts/rules/evolve-reflects-in-list.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"evolve-reflects-in-list.d.ts","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/evolve-reflects-in-list.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,OAAO,KAAK,EAAE,cAAc,EAA4B,MAAM,uBAAuB,CAAC;AAGtF,eAAO,MAAM,OAAO,4BAA4B,CAAC;AAEjD,eAAO,MAAM,oBAAoB,EAAE,cA8BlC,CAAC"}

package/dist/inference/ui-contracts/rules/evolve-reflects-in-list.js

@@ -0,0 +1,53 @@
+/**
+ * Rule: evolve-reflects-in-list
+ *
+ * For every model with a lifecycle, seed an entity in the initial
+ * state, transition it to the next state via backend PATCH, and
+ * assert the list view reflects the new state. This exercises the
+ * lifecycle mutation path through the same state-sync contract as
+ * create/delete.
+ *
+ * Uses the first → second state transition from the lifecycle flow.
+ * If the lifecycle has fewer than two states, the rule produces no
+ * test case for that model.
+ *
+ * One TestCase per (seedable, lifecycled) model. For poll-app: Poll
+ * has a lifecycle with states draft → open → closed, so a single
+ * test covers the draft → open transition.
+ */
+import { pickDisplayAttribute, buildSeedData, getLifecycleStates } from './_shared.js';
+export const RULE_ID = 'evolve-reflects-in-list';
+export const evolveReflectsInList = (spec) => {
+    const cases = [];
+    for (const model of spec.models) {
+        const states = getLifecycleStates(model);
+        if (!states || states.length < 2)
+            continue;
+        const display = pickDisplayAttribute(model);
+        if (!display)
+            continue;
+        const marker = `ct-evolve-${model.name}`;
+        const seedData = buildSeedData(model, marker);
+        if (!seedData)
+            continue;
+        const displayValue = seedData[display.name];
+        if (typeof displayValue !== 'string')
+            continue;
+        const [fromState, toState] = states;
+        cases.push({
+            ruleId: RULE_ID,
+            specElement: `${model.name} ${fromState}→${toState}`,
+            name: `[${RULE_ID}] evolving a ${model.name} from '${fromState}' to '${toState}' updates the list view`,
+            steps: [
+                { action: 'bootRuntime' },
+                { action: 'navigateToModel', modelName: model.name },
+                { action: 'createEntity', modelName: model.name, data: seedData, bindAs: 'id' },
+                { action: 'expectEntityInList', modelName: model.name, displayValue },
+                { action: 'evolveEntity', modelName: model.name, idExpr: 'id', targetState: toState },
+                { action: 'expectLifecycleState', modelName: model.name, stateName: toState },
+            ],
+        });
+    }
+    return cases;
+};
+//# sourceMappingURL=evolve-reflects-in-list.js.map

package/dist/inference/ui-contracts/rules/evolve-reflects-in-list.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"evolve-reflects-in-list.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/evolve-reflects-in-list.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAGH,OAAO,EAAE,oBAAoB,EAAE,aAAa,EAAE,kBAAkB,EAAE,MAAM,cAAc,CAAC;AAEvF,MAAM,CAAC,MAAM,OAAO,GAAG,yBAAyB,CAAC;AAEjD,MAAM,CAAC,MAAM,oBAAoB,GAAmB,CAAC,IAAoB,EAAc,EAAE;IACvF,MAAM,KAAK,GAAe,EAAE,CAAC;IAC7B,KAAK,MAAM,KAAK,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;QAChC,MAAM,MAAM,GAAG,kBAAkB,CAAC,KAAK,CAAC,CAAC;QACzC,IAAI,CAAC,MAAM,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC;YAAE,SAAS;QAC3C,MAAM,OAAO,GAAG,oBAAoB,CAAC,KAAK,CAAC,CAAC;QAC5C,IAAI,CAAC,OAAO;YAAE,SAAS;QACvB,MAAM,MAAM,GAAG,aAAa,KAAK,CAAC,IAAI,EAAE,CAAC;QACzC,MAAM,QAAQ,GAAG,aAAa,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC;QAC9C,IAAI,CAAC,QAAQ;YAAE,SAAS;QACxB,MAAM,YAAY,GAAG,QAAQ,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;QAC5C,IAAI,OAAO,YAAY,KAAK,QAAQ;YAAE,SAAS;QAE/C,MAAM,CAAC,SAAS,EAAE,OAAO,CAAC,GAAG,MAAM,CAAC;QAEpC,KAAK,CAAC,IAAI,CAAC;YACT,MAAM,EAAE,OAAO;YACf,WAAW,EAAE,GAAG,KAAK,CAAC,IAAI,IAAI,SAAS,IAAI,OAAO,EAAE;YACpD,IAAI,EAAE,IAAI,OAAO,gBAAgB,KAAK,CAAC,IAAI,UAAU,SAAS,SAAS,OAAO,yBAAyB;YACvG,KAAK,EAAE;gBACL,EAAE,MAAM,EAAE,aAAa,EAAE;gBACzB,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;gBACpD,EAAE,MAAM,EAAE,cAAc,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,IAAI,EAAE,QAAQ,EAAE,MAAM,EAAE,IAAI,EAAE;gBAC/E,EAAE,MAAM,EAAE,oBAAoB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,YAAY,EAAE;gBACrE,EAAE,MAAM,EAAE,cAAc,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE;gBACrF,EAAE,MAAM,EAAE,sBAAsB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,SAAS,EAAE,OAAO,EAAE;aAC9E;SACF,CAAC,CAAC;IACL,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC,CAAC"}

package/dist/inference/ui-contracts/rules/form-shows-required-indicators.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Rule: form-shows-required-indicators
+ *
+ * For every attribute marked `required`, the model's form view
+ * should expose a visible input or field label. v1 uses a loose
+ * text-presence check; the harness helper can be tightened later
+ * to verify a specific required marker (asterisk, aria-required,
+ * "required" text, etc.).
+ *
+ * One TestCase per (model, required-attribute) pair.
+ */
+import type { UiContractRule } from '../test-case-types.js';
+export declare const RULE_ID = "form-shows-required-indicators";
+export declare const formShowsRequiredIndicators: UiContractRule;
+//# sourceMappingURL=form-shows-required-indicators.d.ts.map

package/dist/inference/ui-contracts/rules/form-shows-required-indicators.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"form-shows-required-indicators.d.ts","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/form-shows-required-indicators.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,KAAK,EAAE,cAAc,EAA4B,MAAM,uBAAuB,CAAC;AAEtF,eAAO,MAAM,OAAO,mCAAmC,CAAC;AAExD,eAAO,MAAM,2BAA2B,EAAE,cAsBzC,CAAC"}

package/dist/inference/ui-contracts/rules/form-shows-required-indicators.js

@@ -0,0 +1,38 @@
+/**
+ * Rule: form-shows-required-indicators
+ *
+ * For every attribute marked `required`, the model's form view
+ * should expose a visible input or field label. v1 uses a loose
+ * text-presence check; the harness helper can be tightened later
+ * to verify a specific required marker (asterisk, aria-required,
+ * "required" text, etc.).
+ *
+ * One TestCase per (model, required-attribute) pair.
+ */
+export const RULE_ID = 'form-shows-required-indicators';
+export const formShowsRequiredIndicators = (spec) => {
+    const cases = [];
+    for (const model of spec.models) {
+        const attrs = model.attributes || [];
+        for (const attr of attrs) {
+            if (!attr.required)
+                continue;
+            // Skip metadata attributes — they're system-managed (id, createdAt)
+            // and shouldn't appear in a user-facing form.
+            if (attr.category === 'metadata')
+                continue;
+            cases.push({
+                ruleId: RULE_ID,
+                specElement: `${model.name}.${attr.name}`,
+                name: `[${RULE_ID}] ${model.name}.${attr.name} is shown as a required input`,
+                steps: [
+                    { action: 'bootRuntime' },
+                    { action: 'navigateToModel', modelName: model.name },
+                    { action: 'expectFormInput', modelName: model.name, attributeName: attr.name, required: true },
+                ],
+            });
+        }
+    }
+    return cases;
+};
+//# sourceMappingURL=form-shows-required-indicators.js.map

package/dist/inference/ui-contracts/rules/form-shows-required-indicators.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"form-shows-required-indicators.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/form-shows-required-indicators.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAIH,MAAM,CAAC,MAAM,OAAO,GAAG,gCAAgC,CAAC;AAExD,MAAM,CAAC,MAAM,2BAA2B,GAAmB,CAAC,IAAoB,EAAc,EAAE;IAC9F,MAAM,KAAK,GAAe,EAAE,CAAC;IAC7B,KAAK,MAAM,KAAK,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;QAChC,MAAM,KAAK,GAAG,KAAK,CAAC,UAAU,IAAI,EAAE,CAAC;QACrC,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;YACzB,IAAI,CAAC,IAAI,CAAC,QAAQ;gBAAE,SAAS;YAC7B,oEAAoE;YACpE,8CAA8C;YAC9C,IAAI,IAAI,CAAC,QAAQ,KAAK,UAAU;gBAAE,SAAS;YAC3C,KAAK,CAAC,IAAI,CAAC;gBACT,MAAM,EAAE,OAAO;gBACf,WAAW,EAAE,GAAG,KAAK,CAAC,IAAI,IAAI,IAAI,CAAC,IAAI,EAAE;gBACzC,IAAI,EAAE,IAAI,OAAO,KAAK,KAAK,CAAC,IAAI,IAAI,IAAI,CAAC,IAAI,+BAA+B;gBAC5E,KAAK,EAAE;oBACL,EAAE,MAAM,EAAE,aAAa,EAAE;oBACzB,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;oBACpD,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,aAAa,EAAE,IAAI,CAAC,IAAI,EAAE,QAAQ,EAAE,IAAI,EAAE;iBAC/F;aACF,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC,CAAC"}

package/dist/inference/ui-contracts/rules/hasmany-shows-children-in-detail.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Rule: hasMany-shows-children-in-detail
+ *
+ * For every `hasMany` relationship on a model, the parent model's
+ * detail view should surface the child collection (section,
+ * collapsible, link, card — any visible reference will do for v1).
+ *
+ * Relationship shape can be either an explicit object or a shorthand
+ * string: `posts: hasMany Post cascade`. The parser normalizes to
+ * `{ name: 'posts', type: 'hasMany', target: 'Post' }`.
+ *
+ * One TestCase per (parent-model, hasMany-relationship) pair.
+ */
+import type { UiContractRule } from '../test-case-types.js';
+export declare const RULE_ID = "hasMany-shows-children-in-detail";
+export declare const hasManyShowsChildrenInDetail: UiContractRule;
+//# sourceMappingURL=hasmany-shows-children-in-detail.d.ts.map

package/dist/inference/ui-contracts/rules/hasmany-shows-children-in-detail.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hasmany-shows-children-in-detail.d.ts","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/hasmany-shows-children-in-detail.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,KAAK,EAAE,cAAc,EAA4B,MAAM,uBAAuB,CAAC;AAEtF,eAAO,MAAM,OAAO,qCAAqC,CAAC;AAE1D,eAAO,MAAM,4BAA4B,EAAE,cAsB1C,CAAC"}

package/dist/inference/ui-contracts/rules/hasmany-shows-children-in-detail.js

@@ -0,0 +1,39 @@
+/**
+ * Rule: hasMany-shows-children-in-detail
+ *
+ * For every `hasMany` relationship on a model, the parent model's
+ * detail view should surface the child collection (section,
+ * collapsible, link, card — any visible reference will do for v1).
+ *
+ * Relationship shape can be either an explicit object or a shorthand
+ * string: `posts: hasMany Post cascade`. The parser normalizes to
+ * `{ name: 'posts', type: 'hasMany', target: 'Post' }`.
+ *
+ * One TestCase per (parent-model, hasMany-relationship) pair.
+ */
+export const RULE_ID = 'hasMany-shows-children-in-detail';
+export const hasManyShowsChildrenInDetail = (spec) => {
+    const cases = [];
+    for (const model of spec.models) {
+        const rels = model.relationships || [];
+        for (const rel of rels) {
+            // Type may contain modifiers (e.g. 'hasMany cascade'); look
+            // for the substring.
+            const typeStr = String(rel.type || '');
+            if (!/hasMany/i.test(typeStr))
+                continue;
+            cases.push({
+                ruleId: RULE_ID,
+                specElement: `${model.name}.${rel.name}`,
+                name: `[${RULE_ID}] ${model.name}.${rel.name} relationship is visible in the detail view`,
+                steps: [
+                    { action: 'bootRuntime' },
+                    { action: 'navigateToModel', modelName: model.name },
+                    { action: 'expectRelationshipSection', modelName: model.name, relationshipName: rel.name },
+                ],
+            });
+        }
+    }
+    return cases;
+};
+//# sourceMappingURL=hasmany-shows-children-in-detail.js.map

package/dist/inference/ui-contracts/rules/hasmany-shows-children-in-detail.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"hasmany-shows-children-in-detail.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/hasmany-shows-children-in-detail.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAIH,MAAM,CAAC,MAAM,OAAO,GAAG,kCAAkC,CAAC;AAE1D,MAAM,CAAC,MAAM,4BAA4B,GAAmB,CAAC,IAAoB,EAAc,EAAE;IAC/F,MAAM,KAAK,GAAe,EAAE,CAAC;IAC7B,KAAK,MAAM,KAAK,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;QAChC,MAAM,IAAI,GAAG,KAAK,CAAC,aAAa,IAAI,EAAE,CAAC;QACvC,KAAK,MAAM,GAAG,IAAI,IAAI,EAAE,CAAC;YACvB,4DAA4D;YAC5D,qBAAqB;YACrB,MAAM,OAAO,GAAG,MAAM,CAAC,GAAG,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC;YACvC,IAAI,CAAC,UAAU,CAAC,IAAI,CAAC,OAAO,CAAC;gBAAE,SAAS;YACxC,KAAK,CAAC,IAAI,CAAC;gBACT,MAAM,EAAE,OAAO;gBACf,WAAW,EAAE,GAAG,KAAK,CAAC,IAAI,IAAI,GAAG,CAAC,IAAI,EAAE;gBACxC,IAAI,EAAE,IAAI,OAAO,KAAK,KAAK,CAAC,IAAI,IAAI,GAAG,CAAC,IAAI,6CAA6C;gBACzF,KAAK,EAAE;oBACL,EAAE,MAAM,EAAE,aAAa,EAAE;oBACzB,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;oBACpD,EAAE,MAAM,EAAE,2BAA2B,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,gBAAgB,EAAE,GAAG,CAAC,IAAI,EAAE;iBAC3F;aACF,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC,CAAC"}

package/dist/inference/ui-contracts/rules/lifecycle-state-visible-in-detail.d.ts

@@ -0,0 +1,25 @@
+/**
+ * Rule: lifecycle-state-visible-in-detail
+ *
+ * For every model with a lifecycle, the detail view should surface
+ * the lifecycle's state names. v1 checks the *first* (initial)
+ * state — typically what a fresh instance shows — because that's
+ * the one guaranteed to exist without creating data.
+ *
+ * Lifecycle shape in the spec:
+ *   lifecycles:
+ *     status:
+ *       flow: draft -> open -> closed
+ *
+ * We parse the `flow` string to extract states. If the model uses a
+ * different shape (e.g. an explicit `states: [...]`), the parser
+ * should normalize both into the same structure.
+ *
+ * One TestCase per (model, lifecycle) pair — not per state, since
+ * testing every state requires creating instances and evolving them,
+ * which belongs to the state-sync rules.
+ */
+import type { UiContractRule } from '../test-case-types.js';
+export declare const RULE_ID = "lifecycle-state-visible-in-detail";
+export declare const lifecycleStateVisibleInDetail: UiContractRule;
+//# sourceMappingURL=lifecycle-state-visible-in-detail.d.ts.map

package/dist/inference/ui-contracts/rules/lifecycle-state-visible-in-detail.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"lifecycle-state-visible-in-detail.d.ts","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/lifecycle-state-visible-in-detail.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAEH,OAAO,KAAK,EAAE,cAAc,EAA4B,MAAM,uBAAuB,CAAC;AAEtF,eAAO,MAAM,OAAO,sCAAsC,CAAC;AAuB3D,eAAO,MAAM,6BAA6B,EAAE,cAqB3C,CAAC"}

package/dist/inference/ui-contracts/rules/lifecycle-state-visible-in-detail.js

@@ -0,0 +1,66 @@
+/**
+ * Rule: lifecycle-state-visible-in-detail
+ *
+ * For every model with a lifecycle, the detail view should surface
+ * the lifecycle's state names. v1 checks the *first* (initial)
+ * state — typically what a fresh instance shows — because that's
+ * the one guaranteed to exist without creating data.
+ *
+ * Lifecycle shape in the spec:
+ *   lifecycles:
+ *     status:
+ *       flow: draft -> open -> closed
+ *
+ * We parse the `flow` string to extract states. If the model uses a
+ * different shape (e.g. an explicit `states: [...]`), the parser
+ * should normalize both into the same structure.
+ *
+ * One TestCase per (model, lifecycle) pair — not per state, since
+ * testing every state requires creating instances and evolving them,
+ * which belongs to the state-sync rules.
+ */
+export const RULE_ID = 'lifecycle-state-visible-in-detail';
+function extractInitialState(lifecycleDef) {
+    if (!lifecycleDef)
+        return null;
+    // Form 1: { flow: 'draft -> open -> closed' }
+    if (typeof lifecycleDef.flow === 'string') {
+        const first = lifecycleDef.flow.split('->')[0]?.trim();
+        if (first)
+            return first;
+    }
+    // Form 2: { states: ['draft', 'open', 'closed'] }
+    if (Array.isArray(lifecycleDef.states) && lifecycleDef.states.length > 0) {
+        const first = lifecycleDef.states[0];
+        return typeof first === 'string' ? first : first?.name || null;
+    }
+    // Form 3: { initial: 'draft', states: {...} }
+    if (typeof lifecycleDef.initial === 'string')
+        return lifecycleDef.initial;
+    return null;
+}
+export const lifecycleStateVisibleInDetail = (spec) => {
+    const cases = [];
+    for (const model of spec.models) {
+        const lifecycles = model.lifecycles;
+        if (!lifecycles)
+            continue;
+        for (const [lcName, lcDef] of Object.entries(lifecycles)) {
+            const initial = extractInitialState(lcDef);
+            if (!initial)
+                continue;
+            cases.push({
+                ruleId: RULE_ID,
+                specElement: `${model.name}.${lcName}`,
+                name: `[${RULE_ID}] ${model.name}.${lcName} initial state '${initial}' visible`,
+                steps: [
+                    { action: 'bootRuntime' },
+                    { action: 'navigateToModel', modelName: model.name },
+                    { action: 'expectLifecycleState', modelName: model.name, stateName: initial },
+                ],
+            });
+        }
+    }
+    return cases;
+};
+//# sourceMappingURL=lifecycle-state-visible-in-detail.js.map

package/dist/inference/ui-contracts/rules/lifecycle-state-visible-in-detail.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"lifecycle-state-visible-in-detail.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/lifecycle-state-visible-in-detail.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAIH,MAAM,CAAC,MAAM,OAAO,GAAG,mCAAmC,CAAC;AAE3D,SAAS,mBAAmB,CAAC,YAAiB;IAC5C,IAAI,CAAC,YAAY;QAAE,OAAO,IAAI,CAAC;IAE/B,8CAA8C;IAC9C,IAAI,OAAO,YAAY,CAAC,IAAI,KAAK,QAAQ,EAAE,CAAC;QAC1C,MAAM,KAAK,GAAG,YAAY,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,CAAC;QACvD,IAAI,KAAK;YAAE,OAAO,KAAK,CAAC;IAC1B,CAAC;IAED,kDAAkD;IAClD,IAAI,KAAK,CAAC,OAAO,CAAC,YAAY,CAAC,MAAM,CAAC,IAAI,YAAY,CAAC,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACzE,MAAM,KAAK,GAAG,YAAY,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;QACrC,OAAO,OAAO,KAAK,KAAK,QAAQ,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,KAAK,EAAE,IAAI,IAAI,IAAI,CAAC;IACjE,CAAC;IAED,8CAA8C;IAC9C,IAAI,OAAO,YAAY,CAAC,OAAO,KAAK,QAAQ;QAAE,OAAO,YAAY,CAAC,OAAO,CAAC;IAE1E,OAAO,IAAI,CAAC;AACd,CAAC;AAED,MAAM,CAAC,MAAM,6BAA6B,GAAmB,CAAC,IAAoB,EAAc,EAAE;IAChG,MAAM,KAAK,GAAe,EAAE,CAAC;IAC7B,KAAK,MAAM,KAAK,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;QAChC,MAAM,UAAU,GAAG,KAAK,CAAC,UAA6C,CAAC;QACvE,IAAI,CAAC,UAAU;YAAE,SAAS;QAC1B,KAAK,MAAM,CAAC,MAAM,EAAE,KAAK,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,UAAU,CAAC,EAAE,CAAC;YACzD,MAAM,OAAO,GAAG,mBAAmB,CAAC,KAAK,CAAC,CAAC;YAC3C,IAAI,CAAC,OAAO;gBAAE,SAAS;YACvB,KAAK,CAAC,IAAI,CAAC;gBACT,MAAM,EAAE,OAAO;gBACf,WAAW,EAAE,GAAG,KAAK,CAAC,IAAI,IAAI,MAAM,EAAE;gBACtC,IAAI,EAAE,IAAI,OAAO,KAAK,KAAK,CAAC,IAAI,IAAI,MAAM,mBAAmB,OAAO,WAAW;gBAC/E,KAAK,EAAE;oBACL,EAAE,MAAM,EAAE,aAAa,EAAE;oBACzB,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;oBACpD,EAAE,MAAM,EAAE,sBAAsB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,SAAS,EAAE,OAAO,EAAE;iBAC9E;aACF,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC,CAAC"}

package/dist/inference/ui-contracts/rules/list-shows-business-columns.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Rule: list-shows-business-columns
+ *
+ * For each attribute marked `category: business` on a model, the
+ * model's list view should expose a column for it. Metadata and
+ * relationship attributes are excluded — metadata is system-managed
+ * and relationship FKs are handled by the relationship rule.
+ *
+ * One TestCase per (model, business-attribute) pair. A 3-attribute
+ * business model with 5 other metadata attributes produces 3 cases,
+ * not 8. That's the point of spec inference: test cases track the
+ * shape that matters.
+ */
+import type { UiContractRule } from '../test-case-types.js';
+export declare const RULE_ID = "list-shows-business-columns";
+export declare const listShowsBusinessColumns: UiContractRule;
+//# sourceMappingURL=list-shows-business-columns.d.ts.map

package/dist/inference/ui-contracts/rules/list-shows-business-columns.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"list-shows-business-columns.d.ts","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/list-shows-business-columns.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,KAAK,EAAE,cAAc,EAA4B,MAAM,uBAAuB,CAAC;AAEtF,eAAO,MAAM,OAAO,gCAAgC,CAAC;AAErD,eAAO,MAAM,wBAAwB,EAAE,cAsBtC,CAAC"}

package/dist/inference/ui-contracts/rules/list-shows-business-columns.js

@@ -0,0 +1,39 @@
+/**
+ * Rule: list-shows-business-columns
+ *
+ * For each attribute marked `category: business` on a model, the
+ * model's list view should expose a column for it. Metadata and
+ * relationship attributes are excluded — metadata is system-managed
+ * and relationship FKs are handled by the relationship rule.
+ *
+ * One TestCase per (model, business-attribute) pair. A 3-attribute
+ * business model with 5 other metadata attributes produces 3 cases,
+ * not 8. That's the point of spec inference: test cases track the
+ * shape that matters.
+ */
+export const RULE_ID = 'list-shows-business-columns';
+export const listShowsBusinessColumns = (spec) => {
+    const cases = [];
+    for (const model of spec.models) {
+        const attrs = model.attributes || [];
+        for (const attr of attrs) {
+            // v1: treat missing category as 'business' so older specs that
+            // don't tag categories still produce useful rules. Skip
+            // metadata + relationship explicitly.
+            if (attr.category === 'metadata' || attr.category === 'relationship')
+                continue;
+            cases.push({
+                ruleId: RULE_ID,
+                specElement: `${model.name}.${attr.name}`,
+                name: `[${RULE_ID}] ${model.name}.${attr.name} column is visible in the list view`,
+                steps: [
+                    { action: 'bootRuntime' },
+                    { action: 'navigateToModel', modelName: model.name },
+                    { action: 'expectListColumn', modelName: model.name, attributeName: attr.name },
+                ],
+            });
+        }
+    }
+    return cases;
+};
+//# sourceMappingURL=list-shows-business-columns.js.map

package/dist/inference/ui-contracts/rules/list-shows-business-columns.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"list-shows-business-columns.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/list-shows-business-columns.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAIH,MAAM,CAAC,MAAM,OAAO,GAAG,6BAA6B,CAAC;AAErD,MAAM,CAAC,MAAM,wBAAwB,GAAmB,CAAC,IAAoB,EAAc,EAAE;IAC3F,MAAM,KAAK,GAAe,EAAE,CAAC;IAC7B,KAAK,MAAM,KAAK,IAAI,IAAI,CAAC,MAAM,EAAE,CAAC;QAChC,MAAM,KAAK,GAAG,KAAK,CAAC,UAAU,IAAI,EAAE,CAAC;QACrC,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;YACzB,+DAA+D;YAC/D,wDAAwD;YACxD,sCAAsC;YACtC,IAAI,IAAI,CAAC,QAAQ,KAAK,UAAU,IAAI,IAAI,CAAC,QAAQ,KAAK,cAAc;gBAAE,SAAS;YAC/E,KAAK,CAAC,IAAI,CAAC;gBACT,MAAM,EAAE,OAAO;gBACf,WAAW,EAAE,GAAG,KAAK,CAAC,IAAI,IAAI,IAAI,CAAC,IAAI,EAAE;gBACzC,IAAI,EAAE,IAAI,OAAO,KAAK,KAAK,CAAC,IAAI,IAAI,IAAI,CAAC,IAAI,qCAAqC;gBAClF,KAAK,EAAE;oBACL,EAAE,MAAM,EAAE,aAAa,EAAE;oBACzB,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;oBACpD,EAAE,MAAM,EAAE,kBAAkB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,aAAa,EAAE,IAAI,CAAC,IAAI,EAAE;iBAChF;aACF,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC,CAAC"}

package/dist/inference/ui-contracts/rules/list-view-renders.d.ts

@@ -0,0 +1,19 @@
+/**
+ * Rule: list-view-renders
+ *
+ * For every model in the spec, boot the runtime, click through to the
+ * model's primary view (typically the list), and assert nothing threw
+ * an error boundary or bailed with an empty DOM.
+ *
+ * Catches: generator regressions that produce broken list components,
+ * runtime component crashes on specific field types, missing column
+ * renderers, etc. The dual guard (error-boundary + non-empty content)
+ * catches both obvious explosions and silent "return null" bugs.
+ *
+ * Deliberately doesn't check for specific content — column-level
+ * assertions come from `list-shows-business-columns` (Phase 3).
+ */
+import type { UiContractRule } from '../test-case-types.js';
+export declare const RULE_ID = "list-view-renders";
+export declare const listViewRenders: UiContractRule;
+//# sourceMappingURL=list-view-renders.d.ts.map

package/dist/inference/ui-contracts/rules/list-view-renders.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"list-view-renders.d.ts","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/list-view-renders.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,KAAK,EAAE,cAAc,EAA4B,MAAM,uBAAuB,CAAC;AAEtF,eAAO,MAAM,OAAO,sBAAsB,CAAC;AAE3C,eAAO,MAAM,eAAe,EAAE,cAW7B,CAAC"}

package/dist/inference/ui-contracts/rules/list-view-renders.js

@@ -0,0 +1,29 @@
+/**
+ * Rule: list-view-renders
+ *
+ * For every model in the spec, boot the runtime, click through to the
+ * model's primary view (typically the list), and assert nothing threw
+ * an error boundary or bailed with an empty DOM.
+ *
+ * Catches: generator regressions that produce broken list components,
+ * runtime component crashes on specific field types, missing column
+ * renderers, etc. The dual guard (error-boundary + non-empty content)
+ * catches both obvious explosions and silent "return null" bugs.
+ *
+ * Deliberately doesn't check for specific content — column-level
+ * assertions come from `list-shows-business-columns` (Phase 3).
+ */
+export const RULE_ID = 'list-view-renders';
+export const listViewRenders = (spec) => {
+    return spec.models.map(model => ({
+        ruleId: RULE_ID,
+        specElement: model.name,
+        name: `[${RULE_ID}] ${model.name} list view renders without errors`,
+        steps: [
+            { action: 'bootRuntime' },
+            { action: 'navigateToModel', modelName: model.name },
+            { action: 'expectViewRenders' },
+        ],
+    }));
+};
+//# sourceMappingURL=list-view-renders.js.map

package/dist/inference/ui-contracts/rules/list-view-renders.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"list-view-renders.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/list-view-renders.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAIH,MAAM,CAAC,MAAM,OAAO,GAAG,mBAAmB,CAAC;AAE3C,MAAM,CAAC,MAAM,eAAe,GAAmB,CAAC,IAAoB,EAAc,EAAE;IAClF,OAAO,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;QAC/B,MAAM,EAAE,OAAO;QACf,WAAW,EAAE,KAAK,CAAC,IAAI;QACvB,IAAI,EAAE,IAAI,OAAO,KAAK,KAAK,CAAC,IAAI,mCAAmC;QACnE,KAAK,EAAE;YACL,EAAE,MAAM,EAAE,aAAa,EAAE;YACzB,EAAE,MAAM,EAAE,iBAAiB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;YACpD,EAAE,MAAM,EAAE,mBAAmB,EAAE;SAChC;KACF,CAAC,CAAC,CAAC;AACN,CAAC,CAAC"}

package/dist/inference/ui-contracts/rules/nav-has-model-entries.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Rule: nav-has-model-entries
+ *
+ * For every model declared in the spec, assert that the runtime UI
+ * exposes a visible reference to the model (nav entry, sidebar link,
+ * dashboard card — any of them count). v1 uses a loose "text appears
+ * on the page" assertion; a stricter ARIA-role variant can come
+ * later once the runtime standardizes its nav component's semantics.
+ *
+ * One TestCase per model.
+ *
+ * This is the most important rule: if the runtime can't even show
+ * the model name after initial render, everything else downstream is
+ * certainly broken. It's also the cheapest — one navigation, one
+ * text query per model.
+ */
+import type { UiContractRule } from '../test-case-types.js';
+export declare const RULE_ID = "nav-has-model-entries";
+export declare const navHasModelEntries: UiContractRule;
+//# sourceMappingURL=nav-has-model-entries.d.ts.map

package/dist/inference/ui-contracts/rules/nav-has-model-entries.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"nav-has-model-entries.d.ts","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/nav-has-model-entries.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAEH,OAAO,KAAK,EAAE,cAAc,EAA4B,MAAM,uBAAuB,CAAC;AAEtF,eAAO,MAAM,OAAO,0BAA0B,CAAC;AAE/C,eAAO,MAAM,kBAAkB,EAAE,cAUhC,CAAC"}

package/dist/inference/ui-contracts/rules/nav-has-model-entries.js

@@ -0,0 +1,29 @@
+/**
+ * Rule: nav-has-model-entries
+ *
+ * For every model declared in the spec, assert that the runtime UI
+ * exposes a visible reference to the model (nav entry, sidebar link,
+ * dashboard card — any of them count). v1 uses a loose "text appears
+ * on the page" assertion; a stricter ARIA-role variant can come
+ * later once the runtime standardizes its nav component's semantics.
+ *
+ * One TestCase per model.
+ *
+ * This is the most important rule: if the runtime can't even show
+ * the model name after initial render, everything else downstream is
+ * certainly broken. It's also the cheapest — one navigation, one
+ * text query per model.
+ */
+export const RULE_ID = 'nav-has-model-entries';
+export const navHasModelEntries = (spec) => {
+    return spec.models.map(model => ({
+        ruleId: RULE_ID,
+        specElement: model.name,
+        name: `[${RULE_ID}] ${model.name} is visible in the nav`,
+        steps: [
+            { action: 'bootRuntime' },
+            { action: 'expectNavHasModel', modelName: model.name },
+        ],
+    }));
+};
+//# sourceMappingURL=nav-has-model-entries.js.map

package/dist/inference/ui-contracts/rules/nav-has-model-entries.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"nav-has-model-entries.js","sourceRoot":"","sources":["../../../../src/inference/ui-contracts/rules/nav-has-model-entries.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAIH,MAAM,CAAC,MAAM,OAAO,GAAG,uBAAuB,CAAC;AAE/C,MAAM,CAAC,MAAM,kBAAkB,GAAmB,CAAC,IAAoB,EAAc,EAAE;IACrF,OAAO,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;QAC/B,MAAM,EAAE,OAAO;QACf,WAAW,EAAE,KAAK,CAAC,IAAI;QACvB,IAAI,EAAE,IAAI,OAAO,KAAK,KAAK,CAAC,IAAI,wBAAwB;QACxD,KAAK,EAAE;YACL,EAAE,MAAM,EAAE,aAAa,EAAE;YACzB,EAAE,MAAM,EAAE,mBAAmB,EAAE,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE;SACvD;KACF,CAAC,CAAC,CAAC;AACN,CAAC,CAAC"}