@antelopejs/dms-ai 0.6.1 → 0.8.0

package/skills/dms-ai/cases.json

@@ -0,0 +1,47 @@
+{
+  "version": 1,
+  "cases": [
+    {
+      "id": "ai-install-codex",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "Install dms-ai and make it use Codex instead of Claude Code.",
+      "expect": {
+        "skills": ["dms-ai"],
+        "acceptable": ["dms", "dms-project"]
+      }
+    },
+    {
+      "id": "ai-offline-casual",
+      "area": "dms-ai",
+      "style": "casual",
+      "prompt": "the ai assistant says offline",
+      "expect": {
+        "skills": ["dms-ai"],
+        "acceptable": ["dms", "dms-project"]
+      }
+    },
+    {
+      "id": "dms-ai-disable-sidecar",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "How do I start the DMS backend without the dms-ai sidecar process, for example in a CI job?",
+      "expect": {
+        "skills": ["dms-ai"],
+        "acceptable": ["dms", "dms-project"],
+        "mustMention": ["DMS_AI"]
+      }
+    },
+    {
+      "id": "dms-ai-not-builder-editor",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "The Edit this page editor never opens and Ctrl+B does nothing. How do I set the projectRoot of the builder module?",
+      "expect": {
+        "skills": ["dms-builder"],
+        "acceptable": ["dms"],
+        "avoid": ["dms-ai"]
+      }
+    }
+  ]
+}

package/skills/dms-ai-code-mode/cases.json

@@ -0,0 +1,38 @@
+{
+  "version": 1,
+  "cases": [
+    {
+      "id": "dms-ai-code-mode-edit-loop",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "The assistant is in Code mode and I want it to change the orders page and the two other pages that reuse the same custom block. How should it work so I can watch each page update in the dashboard?",
+      "expect": {
+        "skills": ["dms-ai-code-mode"],
+        "acceptable": ["dms-ai", "dms-pages", "dms-best-practices"],
+        "mustMention": ["FindPagesUsing", "NavigateToPage", "Typecheck"]
+      }
+    },
+    {
+      "id": "dms-ai-code-mode-page-404-casual",
+      "area": "dms-ai",
+      "style": "casual",
+      "prompt": "ai edited my page in code mode and now it 404s, how do i see why",
+      "expect": {
+        "skills": ["dms-ai-code-mode"],
+        "acceptable": ["dms-ai", "dms-pages", "dms"],
+        "mustMention": ["QueryLogs"]
+      }
+    },
+    {
+      "id": "dms-ai-code-mode-not-safe-builder",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "We are in safe mode. Create a Reports page under the pages.reports category with BuilderCreatePage, then add a TableView on the orders resource.",
+      "expect": {
+        "skills": ["dms-builder-safe"],
+        "acceptable": ["dms-pages", "dms-best-practices"],
+        "avoid": ["dms-ai-code-mode"]
+      }
+    }
+  ]
+}

package/skills/dms-builder-safe/cases.json

@@ -0,0 +1,67 @@
+{
+  "version": 1,
+  "cases": [
+    {
+      "id": "ai-builder-add-chart",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "Using the Builder tools, add a revenue chart to the sales page.",
+      "expect": {
+        "skills": ["dms-builder-safe"],
+        "acceptable": [
+          "dms-pages",
+          "dms-best-practices",
+          "dms-builder-page",
+          "dms-builder"
+        ]
+      }
+    },
+    {
+      "id": "dms-builder-safe-table-casual",
+      "area": "dms-ai",
+      "style": "casual",
+      "prompt": "add a table of the books to the catalog page, safe mode",
+      "expect": {
+        "skills": ["dms-builder-safe"],
+        "acceptable": ["dms-pages", "dms-builder", "dms-best-practices"]
+      }
+    },
+    {
+      "id": "dms-builder-safe-kpi-query",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "In safe mode, add a KpiCard to the /sales/overview page that shows the total number of orders. Which Builder tools do I call, in what order?",
+      "expect": {
+        "skills": ["dms-builder-safe"],
+        "acceptable": ["dms-pages", "dms-best-practices", "dms-builder"],
+        "mustMention": [
+          "BuilderQueryTemplates",
+          "BuilderAddQuery",
+          "BuilderAddBlock"
+        ]
+      }
+    },
+    {
+      "id": "dms-builder-safe-opaque-target",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "In safe mode the Builder answered opaque_target when I tried to configure the nested chart of a ChartCard. How should the agent proceed?",
+      "expect": {
+        "skills": ["dms-builder-safe"],
+        "acceptable": ["dms-ai-code-mode", "dms-best-practices", "dms-pages"],
+        "mustMention": ["AskUser"]
+      }
+    },
+    {
+      "id": "dms-builder-safe-not-code-mode",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "dms-ai is in Code mode. I changed a custom block by hand and want to show the three pages that render it, then check the Typecheck output.",
+      "expect": {
+        "skills": ["dms-ai-code-mode"],
+        "acceptable": ["dms-ai", "dms-pages"],
+        "avoid": ["dms-builder-safe"]
+      }
+    }
+  ]
+}

package/skills/dms-external-database/REFERENCE.md

@@ -11,7 +11,7 @@ integrator gave you:
       "source": { "type": "package", "package": "@antelopejs/postgres", "version": "<version>" },
       "config": { "mode": "external", "statementTimeoutMs": 30000 },
       "env": { "url": "ERP_DATABASE_URL" } } },
-  { "op": "CreateLocalModule", "id": "erp-tables", "path": "modules/erp-tables", "entry": {
+  { "op": "CreateLocalModule", "id": "erp-tables", "path": "modules/erp-tables", "connection": "erp", "entry": {
       "importOverrides": [{ "interface": "@antelopejs/interface-database", "source": "postgres-erp" }] } },
   { "op": "ConfigureModule", "id": "mongodb", "entry": {
       "exportPriority": { "@antelopejs/interface-database": 1 } } },
@@ -22,13 +22,36 @@ integrator gave you:
 ] }
 ```
 
-- **Step 1** is the client's database as an external postgres instance. Its URL comes from the
-  variable.
-- **Step 2** is the module the tables are generated into. It is bound to that instance.
+- **Step 1** is the client's database as an external instance of its engine's module. Its URL
+  comes from the variable.
+- **Step 2** is the module the tables are generated into. It is bound to that instance, and
+  `connection` records that it holds the tables of `erp`.
 - **Step 3** keeps the DMS and its modules on the project's own database. Leave it out if the
   project already pins them.
 - **Steps 4 and 5** give the Builder and you the connection `erp`, the same id for both.
 
+For MongoDB and RethinkDB, step 1 changes, and the other steps name its id in place of
+`postgres-erp`. The `disabledExports` entry keeps the external instance from ever serving the raw
+client other modules ask for:
+
+```json
+{ "op": "AddModule", "id": "mongodb-erp", "entry": {
+    "source": { "type": "package", "package": "@antelopejs/mongodb", "version": "<version>" },
+    "config": { "mode": "external", "statementTimeoutMs": 30000 },
+    "env": { "url": "ERP_DATABASE_URL", "database": "ERP_DATABASE_NAME" },
+    "disabledExports": ["@antelopejs/interface-mongodb"] } }
+```
+
+```json
+{ "op": "AddModule", "id": "rethinkdb-erp", "entry": {
+    "source": { "type": "package", "package": "@antelopejs/rethinkdb", "version": "<version>" },
+    "config": { "mode": "external", "statementTimeoutMs": 30000 },
+    "env": { "url": "ERP_DATABASE_URL" },
+    "disabledExports": ["@antelopejs/interface-rethinkdb"] } }
+```
+
+The RethinkDB URL holds the database as its path: `rethinkdb://user:password@host:28015/erp`.
+
 ## The proposal
 
 `BuilderAnalyseDatabase` answers it once the job is done:
@@ -53,7 +76,8 @@ integrator gave you:
   "open": [
     { "id": "purpose:legacy.t_cst", "kind": "purpose", "relation": "legacy.t_cst",
       "question": "What does legacy.t_cst hold?", "options": ["…"], "proposed": null,
-      "resource": { "relation": "legacy.t_cst", "…": "…" } } ] }
+      "resource": { "relation": "legacy.t_cst", "…": "…" },
+      "open": [ { "id": "reference:legacy.t_cst.c05", "kind": "reference", "…": "…" } ] } ] }
 ```
 
 The rules, in the order they apply to a relation:
@@ -64,15 +88,15 @@ The rules, in the order they apply to a relation:
 | R4 | a framework's or a migration tool's table | excluded |
 | R3 | no rows | excluded |
 | R2 | no key | stats only |
-| R5 | keyed by its two foreign keys | stats only: a link table |
+| R5 | keyed by its two references | stats only: a link table |
 | R6 | keyed, with a label candidate | TableView |
 | R7 | keyed, no label, referenced | TableView labelled by its key, and a `label` item |
 | R8 | keyed, no label, not referenced, with a time axis | stats only: events or a log |
 | R9 | anything else | a `purpose` item |
 
 For columns: F1 and F2 leave out a column no type reads and one named like a secret, F3 proposes
-the first accepted declaration, F4 makes a declared foreign key a relation column, F5 one found
-whole by `CheckReference`. L1 chooses labels, L2 titles, FL the four flags, W1 read-only.
+the first accepted declaration, F4 makes a reference the database declares a relation column
+(PostgreSQL only), F5 one found whole by `CheckReference`. L1 chooses labels, L2 titles, FL the four flags, W1 read-only.
 
 ## Plan
 
@@ -119,7 +143,8 @@ The proposal's values, without their rules, plus what you changed:
 ```
 
 - `declared` defaults to the column's `accepts[0]`. Set it only to take another accepted
-  declaration.
+  declaration, and always for a column a `field-type` item asked about: give the answer as its
+  `declared`.
 - Key columns are added for you.
 - A relation column's target must be in the same call, with a `label`, or mapped in the module
   before.

package/skills/dms-external-database/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dms-external-database
-description: Connects a DMS project to a client's existing database, runs the Builder's analysis of it, settles what the analysis could not decide from the catalog and aggregates, generates TableViews through the Builder, and adds stats pages over them. Use when the user wants pages over a database the project does not own ("plug in our client's Postgres", "generate the admin for this database", "finish the mapping the Builder proposed").
+description: Connects a DMS project to a client's existing database, runs the Builder's analysis of it, settles what the analysis could not decide from the catalog and aggregates, generates TableViews through the Builder, and adds stats pages over them. Use when the user wants pages over a database the project does not own, PostgreSQL, MongoDB or RethinkDB ("plug in our client's Postgres", "map their Mongo database", "generate the admin for this database", "finish the mapping the Builder proposed").
 icon: i-ph-database
 category: Builder
 tags: [Database, Builder, Pages, DMS]
@@ -28,16 +28,21 @@ Call `DatabaseConnections`.
 - **A connection is listed** with an `engine`: use its id and go to 2.
 - **An entry answers `error`**: say what it says (an owned instance, the catalog not enabled, a
   role that cannot read) and stop.
-- **Nothing is listed**: the project is not connected yet. Propose one
-  `BuilderConfigureProject` call with the steps in REFERENCE.md *Connecting*. Pick the names with
-  the integrator, for example connection `erp`, provider module `postgres-erp`, generated module
-  `erp-tables`, variable `ERP_DATABASE_URL`. Ask the integrator for the version of
-  `@antelopejs/postgres` to install: you cannot look it up. The user approves the diff.
-  - Then tell the integrator to put the URL in `.env` (`ERP_DATABASE_URL=postgres://…`), or in
-    the Builder's *Database* workspace, which writes it there, and to restart the project. Every
-    deployed environment needs the same variable, set where that environment keeps its secrets,
+- **Nothing is listed**: the project is not connected yet. Ask the integrator which engine the
+  database runs: PostgreSQL, MongoDB or RethinkDB. Propose one `BuilderConfigureProject` call
+  with that engine's steps in REFERENCE.md *Connecting*. Pick the names with the integrator, for
+  example connection `erp`, provider module `postgres-erp` (`mongodb-erp`, `rethinkdb-erp`),
+  generated module `erp-tables`, variable `ERP_DATABASE_URL`, and for MongoDB
+  `ERP_DATABASE_NAME`. Ask the integrator for the version of the engine's module to install
+  (`@antelopejs/postgres`, `@antelopejs/mongodb`, `@antelopejs/rethinkdb`): you cannot look it
+  up. The user approves the diff.
+  - Then tell the integrator to put the URL in `.env` (`ERP_DATABASE_URL=postgres://…`,
+    `mongodb://…`, or `rethinkdb://…/<database>`; for MongoDB also `ERP_DATABASE_NAME`), or in the
+    Builder's *Database* workspace, which writes it there, and to restart the project. Every
+    deployed environment needs the same variables, set where that environment keeps its secrets,
     never in git.
-  - Recommend a role with SELECT only for the analysis.
+  - Recommend an account that can only read for the analysis: a PostgreSQL role with SELECT, a
+    MongoDB user with the built-in `read` role, a RethinkDB user with `read` permission.
   - Stop here: the connection exists only after the restart.
 
 The Builder and you each have a connection to the database, under the same id: the Builder for
@@ -66,16 +71,24 @@ profile of the whole database again: the Builder did it.
 - **Open items**, one by one:
   - `purpose`: what a relation holds. Decide from its name, comment, columns and profile:
     entities to list (a TableView), facts to count (stats only), or nothing to show (excluded).
-    The item carries the relation as it would be mapped.
+    The item carries the relation as it would be mapped, and in its own `open` the questions
+    that mapping leaves. Answer those only when you map the relation.
   - `label`: which column names a row. Prefer a name or title, then a code or number people
     recognise.
   - `reference`: a column found almost whole in another relation's key. Check it with
     `CheckReference` on the column; make it a relation column only at containment 1.
+  - `field-type`: a field of a document database whose sampled values have several types, none
+    covering enough of them (`int 60% | string 40%`). Pick the declaration that reads what
+    the field means, from its name and its shares, or leave it out. Unanswered, it stays out.
   - Where nothing tells you, say so and leave the item open: the integrator answers it in the
     Builder. Do not guess.
 - **Defaults worth revisiting.** For example a table rule R8 calls a log whose name and comment
   say it holds entities, a label rule L1 chose that a comment contradicts, or a title taken from a
   cryptic name.
+- **Document databases** (MongoDB, RethinkDB) declare no field types and no references: the
+  catalog reads types from a sample, and every reference comes from a name and a `CheckReference`,
+  never from the database. An embedded document is one field: its subfields are not mappable, and
+  neither is an array of ids as a relation.
 - **Editable.** Every TableView is proposed read-only. Make one editable only where the integrator
   wants it; show `writes` beside it, so a read-only role in this environment is visible.
 - **Stats pages,** which the analysis does not make, one per area:

package/skills/dms-external-database/cases.json

@@ -0,0 +1,47 @@
+{
+  "version": 1,
+  "cases": [
+    {
+      "id": "dms-external-database-connect-erp",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "Our client already runs a PostgreSQL ERP database. I want admin pages over it in this DMS project without recreating the tables, and nothing is connected yet. How do we begin?",
+      "expect": {
+        "skills": ["dms-external-database"],
+        "acceptable": ["dms", "dms-builder", "dms-builder-safe"],
+        "mustMention": ["BuilderConfigureProject"]
+      }
+    },
+    {
+      "id": "dms-external-database-finish-mapping",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "The Builder analysed the client's database and proposed a mapping with a few open items. Settle them, apply the mapping and add a page with monthly revenue.",
+      "expect": {
+        "skills": ["dms-external-database"],
+        "acceptable": ["dms-builder", "dms-builder-safe"]
+      }
+    },
+    {
+      "id": "dms-external-database-casual",
+      "area": "dms-ai",
+      "style": "casual",
+      "prompt": "need admin screens for the clients old postgres db, dont wanna recreate the tables",
+      "expect": {
+        "skills": ["dms-external-database"],
+        "acceptable": ["dms", "dms-builder", "dms-builder-safe", "dms-database"]
+      }
+    },
+    {
+      "id": "dms-external-database-not-console",
+      "area": "dms-ai",
+      "style": "clean",
+      "prompt": "Show me the schemas that my project's own modules registered as a diagram in the dashboard console.",
+      "expect": {
+        "skills": ["dms-database"],
+        "acceptable": ["dms"],
+        "avoid": ["dms-external-database"]
+      }
+    }
+  ]
+}

package/frontend-vue/tests/i18n-panel.test.ts

@@ -1,118 +0,0 @@
-import { readdirSync, readFileSync, statSync } from "node:fs";
-import { join, resolve } from "node:path";
-import { describe, expect, it } from "vitest";
-import { TOOL_VERB_KEYS } from "../app/chat/utils/tool-lexicon";
-import en from "../i18n/locales/dms-ai-panel-en-GB.json";
-import fr from "../i18n/locales/dms-ai-panel-fr-FR.json";
-
-type Tree = Record<string, unknown>;
-
-const ROOT = resolve(__dirname, "..");
-const SOURCES = [
-	"app/chat",
-	"app/runtime",
-	"app/plugins",
-	"app/components/ChatPanel.vue",
-];
-const LITERAL_KEY =
-	/["'`](dms_ai\.(?:panel|tools|common)\.[A-Za-z0-9_.]+[A-Za-z0-9_])["'`]/g;
-const OWNED_NAMESPACES = ["panel", "tools", "common"];
-
-/** Keys built at run time from a value, each with every value it can take. */
-const DYNAMIC_FAMILIES: Record<string, readonly string[]> = {
-	"dms_ai.panel.tool.state": [
-		"done",
-		"running",
-		"waiting",
-		"denied",
-		"blocked",
-		"failed",
-		"stopped",
-	],
-	"dms_ai.panel.change.status": ["added", "modified", "deleted"],
-	"dms_ai.panel.change.typecheck": ["passed", "failed", "skipped"],
-	"dms_ai.common.scope": ["safe", "vibe"],
-	"dms_ai.common.agent": ["claude", "codex"],
-	"dms_ai.panel.composer.scope_desc": ["safe", "vibe"],
-	"dms_ai.panel.full_auto": [
-		"duration_turn",
-		"duration_30m",
-		"duration_chat",
-		"banner_turn",
-		"banner_30m",
-		"banner_chat",
-	],
-	"dms_ai.panel.drawer": [
-		"group_active",
-		"group_today",
-		"group_week",
-		"group_older",
-	],
-	"dms_ai.panel.empty": ["text_safe", "text_vibe"],
-	"dms_ai.panel.approvals": [
-		"why_deletes_data",
-		"why_removes_code",
-		"effect_adds_dependency",
-		"effect_removes_dependency",
-	],
-	"dms_ai.panel.rules": [
-		"kind_file",
-		"kind_directory",
-		"kind_command",
-		"kind_domain",
-	],
-};
-
-function files(path: string): string[] {
-	const full = join(ROOT, path);
-	if (!statSync(full).isDirectory()) return [full];
-	return readdirSync(full).flatMap((entry) => files(join(path, entry)));
-}
-
-function flatten(tree: Tree, prefix = ""): string[] {
-	return Object.entries(tree).flatMap(([key, value]) =>
-		value !== null && typeof value === "object"
-			? flatten(value as Tree, `${prefix}${key}.`)
-			: [`${prefix}${key}`],
-	);
-}
-
-function usedKeys(): string[] {
-	const source = SOURCES.flatMap(files)
-		.map((file) => readFileSync(file, "utf8"))
-		.join("\n");
-	return [
-		...new Set([...source.matchAll(LITERAL_KEY)].map((match) => match[1])),
-	];
-}
-
-const dynamicKeys = Object.entries(DYNAMIC_FAMILIES).flatMap(
-	([prefix, values]) => values.map((value) => `${prefix}.${value}`),
-);
-
-describe("the panel's strings", () => {
-	const english = new Set(flatten(en));
-	const french = new Set(flatten(fr));
-
-	it("exist in English and French alike", () => {
-		expect([...english].sort()).toEqual([...french].sort());
-	});
-
-	it("cover every key the panel uses", () => {
-		const keys = [
-			...usedKeys(),
-			...dynamicKeys,
-			...TOOL_VERB_KEYS.map((verb) => `dms_ai.tools.${verb}`),
-		];
-		expect(keys.filter((key) => !english.has(key))).toEqual([]);
-	});
-
-	it("stay in the panel's own namespaces", () => {
-		expect(Object.keys(en.dms_ai).sort()).toEqual([...OWNED_NAMESPACES].sort());
-	});
-
-	it("hold no character vue-i18n would read as syntax", () => {
-		const texts = [JSON.stringify(en), JSON.stringify(fr)];
-		for (const text of texts) expect(text).not.toMatch(/[@$]/);
-	});
-});

package/frontend-vue/tests/i18n-views.test.ts

@@ -1,63 +0,0 @@
-import { readdirSync, readFileSync, statSync } from "node:fs";
-import { join, resolve } from "node:path";
-import { describe, expect, it } from "vitest";
-import en from "../i18n/locales/dms-ai-views-en-GB.json";
-import fr from "../i18n/locales/dms-ai-views-fr-FR.json";
-
-type Tree = Record<string, unknown>;
-
-const ROOT = resolve(__dirname, "..");
-// The page components (the skill drawer and cards among them) and the view
-// helpers they share; the chat panel has its own test.
-const SOURCES = ["app/components", "app/views"];
-const EXCLUDED = ["ChatPanel.vue"];
-const LITERAL_KEY = /["'`](dms_ai\.views\.[A-Za-z0-9_.]+[A-Za-z0-9_])["'`]/g;
-
-/** Keys built at run time from a value, each with every value it can take. */
-const DYNAMIC_FAMILIES: Record<string, readonly string[]> = {
-	"dms_ai.views.skills.source": ["module", "local"],
-};
-
-function files(path: string): string[] {
-	const full = join(ROOT, path);
-	if (!statSync(full).isDirectory()) return [full];
-	return readdirSync(full)
-		.filter((entry) => !EXCLUDED.includes(entry))
-		.flatMap((entry) => files(join(path, entry)));
-}
-
-function flatten(tree: Tree, prefix = ""): string[] {
-	return Object.entries(tree).flatMap(([key, value]) =>
-		value !== null && typeof value === "object"
-			? flatten(value as Tree, `${prefix}${key}.`)
-			: [`${prefix}${key}`],
-	);
-}
-
-function usedKeys(): string[] {
-	const source = SOURCES.flatMap(files)
-		.map((file) => readFileSync(file, "utf8"))
-		.join("\n");
-	return [
-		...new Set([...source.matchAll(LITERAL_KEY)].map((match) => match[1])),
-	];
-}
-
-const dynamicKeys = Object.entries(DYNAMIC_FAMILIES).flatMap(
-	([prefix, values]) => values.map((value) => `${prefix}.${value}`),
-);
-
-describe("the views' strings", () => {
-	const english = new Set(flatten(en));
-	const french = new Set(flatten(fr));
-
-	it("exist in English and French alike", () => {
-		expect([...english].sort()).toEqual([...french].sort());
-	});
-
-	it("cover every key the views use", () => {
-		const keys = [...usedKeys(), ...dynamicKeys];
-		expect(keys.length).toBeGreaterThan(0);
-		expect(keys.filter((key) => !english.has(key))).toEqual([]);
-	});
-});

package/frontend-vue/tests/panel-header-height.test.ts

@@ -1,40 +0,0 @@
-import { readFileSync } from "node:fs";
-import { resolve } from "node:path";
-import { describe, expect, it } from "vitest";
-
-// jsdom does not lay out, so these read the stylesheets: each panel header must
-// take its height from the DMS navbar's variable, or their borders drift apart.
-const HEADER_RULES = [
-	{ file: "../app/chat/components/PanelHeader.vue", selector: ".cb__head" },
-	{
-		file: "../app/chat/components/ConversationDrawer.vue",
-		selector: ".cb-drawer__head",
-	},
-];
-
-function ruleBody(source: string, selector: string): string {
-	const start = source.indexOf(`${selector} {`);
-	expect(start, `${selector} rule`).toBeGreaterThanOrEqual(0);
-	return source.slice(start, source.indexOf("}", start));
-}
-
-describe("panel header height", () => {
-	it.each(HEADER_RULES)("$selector uses the DMS header height", (rule) => {
-		const source = readFileSync(resolve(__dirname, rule.file), "utf8");
-
-		expect(ruleBody(source, rule.selector)).toMatch(
-			/\bheight: var\(--ui-header-height\);/,
-		);
-	});
-
-	it("centres the status overlay close button in that height", () => {
-		const source = readFileSync(
-			resolve(__dirname, "../app/components/ChatPanel.vue"),
-			"utf8",
-		);
-
-		expect(ruleBody(source, ".dms-ai-panel-close")).toContain(
-			"var(--ui-header-height)",
-		);
-	});
-});