@ai-matrx/records 0.81.3 → 0.82.1

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog — @ai-matrx/records
 
+## 0.82.1
+### lane DESCRIBE-BENCH2 (sweep): the mechanical wrong shapes are read, not refused
+
+- `autofixDescribeSpec` also rewrites, each with an auto-fix note and only when unambiguous: view `filters` written as a list of `{field, op, value}` (→ the store's map; several values → `anyOf`; a condition the store cannot express is dropped and SAID), `sort`/`orderBy` → `sorts`, `group_by`/`date_field`/… → `groupBy`/`dateField`/…, an exact duplicate view dropped; a field typed with `kind`/`type` (or by a plain label) → `parityType`; a formula over bare field names → `{Label}`; a relationship `inverseKey` that is already a field of the target (the store then read the rollup's link as a plain formula) renamed; a rollup named for a status with no filter → the filter when exactly one far-side choice/tick box is that word; a real-looking phone → a fictional one; a copy of the shared team_member block → an ordinary table (name, role, notes).
+- `describeVocabulary()` gains `view_filters_shape`, `field_shape`, `formula_shape`, `relationship_shape`, `phone_rule`, `team_rule`.
+
+## Earlier in this release — a rollup or lookup in the wrong shape is read, not refused
+
+- `autofixDescribeSpec` (so `describeCheck` and the live box) rewrites a rollup or lookup written as `{rollup:{relation,field,fn}}`, `{lookup:{relationField,targetField}}`, `rollupVia/rollupField/rollupFn`, `through/aggregate` and ~20 other spellings into the validator's `via` / `pick` / `agg`, with an auto-fix note, when the relation field, the far field and the aggregate word are unambiguous (sum/total, count, avg/average/mean, min, max …). A rollup through a single link makes that link a list (and its relationship `many`). An unknown relation or aggregate is left for the check to name — nothing is invented.
+- `describeVocabulary()` gains `rollup_shape` and `lookup_shape`: the rule in one sentence and one tiny example in the validator's keys, handed to every describe arm.
+- Confirmed: the 20% governance quota is a gallery bar and the describe profile does not refuse it (0.80.9; guarded by `governance-quota.test.ts`).
+- Bench scripts read a raw answer through the platform's whole-document repair (`content-ir` json-extract), never a hand slice; the scorer re-runs the box's post-processing (safeReuses → describeCheck) with the current package.
+
+**Consumer action:** none (matrx-frontend picks it up on update).
+
+## 0.82.0 — workbook bytes from print, no alchemy
+
+- Spreadsheet import/export reads and writes through `@ai-matrx/print/xlsx` (the one SheetJS
+  engine). records no longer depends on `@ai-matrx/alchemy`, removing the records -> alchemy
+  layer violation (architecture step 13).
+
+Consumer action: none.
+
 ## 0.81.3
 ### lane DRILL-FACTS: a records page is its count
 

package/dist/app-table/index.cjs

@@ -944,7 +944,7 @@ function exportCellText(value) {
   return JSON.stringify(value);
 }
 async function exportPageXlsx(page2, labels = {}, sheetLabel = "Records") {
-  const { writeWorkbookBytes } = await import("@ai-matrx/alchemy/operate/formats/xlsx");
+  const { writeWorkbookBytes } = await import("@ai-matrx/print/xlsx");
   const header = page2.columns.map((c) => labels[c] ?? c);
   const body = page2.rows.map((row) => page2.columns.map((c) => exportCellText(row[c])));
   const name = sheetLabel.replace(/[\\/?*[\]:]/g, " ").trim().slice(0, 31) || "Records";