@ai-matrx/records 0.55.1 → 0.57.0

package/CHANGELOG.md

@@ -1,5 +1,53 @@
 # Changelog — @ai-matrx/records
 
+## 0.57.0
+
+**The grid primitives are live, so their doors are in the catalogue.** (published by lane
+PUBLISH-SWEEP-4; built by GRID-PRIMITIVES.) The 2026-09-23 chair window applied G1–G8 to the main
+database and `pnpm records:generate` was re-run (`8df00afbb3`, `fa3434f967`): `store.generated.ts`
+now lists 605 doors, so `tableDecorate`, `gridLayout`, `actionRun`, the table webhooks and the rest
+of 0.56.0's grid methods reach the store instead of answering `door_absent`.
+
+* **`recordChangeTrigger(tableId, { actions, changedFields })`** (G8) builds the event-schedule
+  trigger that runs an agent when a row changes, the same way in either store; the scheduler's
+  one matcher hears it, and the store switch is honoured.
+* **`54000` maps to `store_limit`.** The grid doors refuse past an organization ceiling
+  (`custom/example_rows_max`, `custom/table_webhooks_max`, the action-selection and decoration
+  limits) with 54000 and the knob named in the hint; before this it would have read as `internal`.
+* The refusal census now exempts exactly one raise: `custom.action_run`'s self-caught P0001 probe,
+  and only while it is the sole raiser and the probe sentence is still in the live body.
+
+Suite 111/111, `check:store-registry` OK against the live store.
+
+## 0.56.0
+
+**A Person or File column takes an id** (lane RELATION-TARGETS): `coerceTypedAnswer`'s member and
+attachment arms pass a member's user id, an uploaded file's id or the kernel record's own id
+through as the value, because the store resolves it to the Person / File record at every write
+door; a typed NAME is still refused, with the control that holds it.
+
+**And the grid's store primitives** (lane GRID-PRIMITIVES), below. Published by PUBLISH-SWEEP-4.
+
+### The grid's store primitives
+
+**Everything the /data grid rebuild needs from the store, as typed calls** (`src/grid.ts`):
+`tableDecorate` / `tableDecorations` (row color by a choice column, ordered color rules, hand
+highlights on rows, cells and columns — Fields and records by id), `gridLayout` (platform →
+organization knob `custom/grid_layout` → the saved view's own `definition.layout`, each choice
+saying where it came from), `formulaParse` (the older grid's formula text → the store's
+expression), `actionDeclare` / `rowActions` / `actionRun` (a row action on a whole selection in
+ONE transaction; `actionRefusals(error)` lists every record and field that refused),
+`tableWebhookDeclare` / `tableWebhooks` / `tableWebhookArchive` (every record change out to a
+signed webhook), `tableFromExample` (one real use case of `./use-cases`, built whole),
+`autonumberBackfill`, `ioExport` and `exportXlsx` (the export door's own page as an .xlsx, a
+withheld column named on its own sheet). `AggregateOperation` gains `median`, `filled`, `empty`,
+`unique`.
+
+**Consumer action:** none until the chair applies the five `gridprim_*` migrations to the main
+database (01:00–04:00 PT) and `pnpm records:generate` lists the doors in `STORE_DOORS`. Until
+then every new method answers `door_absent` naming GRID-PRIMITIVES — never a guess, never an
+empty answer.
+
 ## 0.55.1
 
 **0.55.0, actually published.** The tag `npm/records/v0.55.0` never reached the registry: its