@ai-matrx/records-ui 0.53.0 → 0.57.0

package/CHANGELOG.md

@@ -1,5 +1,122 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.57.0
+
+**The builders are usable where a person actually reaches them: a 384px rail.**
+
+The first browser walk (lane BUILDERS, Ironline Fitness, 2026-09-21) pressed
+"Build the form" on a real gym's members table and got a preview of an empty
+form and **no controls at all**. `FormBuilder` was authored as two desktop
+columns — controls left, live preview in a `w-96` aside right — and the rail it
+is mounted in is itself `w-96`, so the fixed-width preview took the entire rail
+and squeezed the controls to nothing. The screen looked like a builder and could
+not build.
+
+A viewport breakpoint cannot fix that: the viewport was 1680px wide while the
+container was 384px. Every split in these four screens is now a **container
+query**, so they are the same screen in a rail, a dialog or a full page:
+
+* `FormBuilder` stacks to one column and its preview goes full-width below the
+  controls until the component itself is wide enough for two (`@3xl`).
+* `BookingBuilder`, `PortalBuilder` and `DigestScheduler` drop their two-column
+  grids and fixed-width inputs to one column under `@md`.
+
+**Consumer action:** none. The host must already scan this package's `dist` for
+Tailwind classes (`@source "…/@ai-matrx/records-ui/dist"`), which matrx-frontend
+does; the container variants are generated from there like every other class.
+
+## 0.56.0
+
+**A condition the builder cannot draw is said in words, not blanked.**
+
+Found by a screenshot, which is what the screenshots were for. The Birchwood
+Avenue renovation's own rule demands "a second quote from a DIFFERENT
+contractor" — a `sibling_count`, which the one-clause builder cannot draw — and
+the editor rendered it as **"— pick a column —"**. That is the screen saying
+there is no condition when there is one, beside a live Save button, on a rule
+that is turning people's work away right now.
+
+It now reads: *"it cannot get here unless **how many others there are for the
+same Room from a different Contractor** — this part of the rule is not something
+this builder can draw yet, so it is shown as it reads"*, with a **Replace it**
+button. Replacing is a thing a person DID, never a thing that happened to them
+because a control looked empty — and until they press it, the clause they cannot
+draw is still the one that saves.
+
+`conditionIsSimple` and `conditionInWords` are exported, so every screen that
+mounts the builder gets the same honesty rather than each deciding for itself.
+
+## 0.55.0
+
+**Three things the bulk paste got wrong on its first real fifty rows.**
+
+Proved headlessly on **Rincon Plumbing Co's September billing run** — fifty real
+invoices, `INV-5100`…`INV-5149`, a `$1,250.50` and a `(285.00)` credit, two
+cells deliberately wrong. The paste itself worked end to end: the preview
+appeared with the store untouched, the money arrived as `1250.5` rather than the
+sheet's string, the bracketed credit as `-285`, and the outcome read *"All 198
+values are in the table — read back out of it, not just accepted"*, confirmed by
+an independent read as the same identity. These are the three things that were
+wrong with it anyway.
+
+* **Every refusal said "Row 0" and named a raw column key.** `validateCell` and
+  the planner ask the same question, and for a cell on a row that already exists
+  the primitive asks first — so the refusal arrived already decided, with a
+  column id and no line, and the planner's correct "Row 12, Amount Due" could
+  only ever fire for an overflow row. The refused cells are folded back into the
+  block with their own values (design-system 0.31.0 keeps them) and the planner
+  judges the whole thing: one place deciding, one set of words, a line number and
+  the column's own name on every refusal. With fifty rows on a clipboard that is
+  the difference between a fixable cell and a shrug.
+* **"This will change 28 Invoicess and create 22 new Invoicess."** The sentence
+  appended an "s" to `label_singular`, which for that table is already
+  "Invoices". A plural is a word a table knows (`label_plural`), never a rule
+  applied to another word.
+* **Every pasted date drew one day early**, systematically, across all fifty.
+  `2026-09-01` parsed as an INSTANT is midnight UTC, and a Ventura grid renders
+  that as 31 August. A date field holds a DAY — the day the invoice was issued is
+  the same day in Ventura and in Berlin — so a pasted day is kept as that day,
+  and only a field that actually declares a time becomes an instant. A
+  spreadsheet's own format ("9/1/2026") keeps the day the reader can see, not the
+  UTC one.
+
+**And the demo harness could not stand up in a fresh organization.** All four
+`ensure*Field` helpers updated the Table's `fields` list BEFORE inserting the
+Field definition, which `custom._claimed_column_guard` refuses outright — *"Records
+UI Demo says it has a column called \"signed_by\", and there is no such field."*
+The harness only worked in organizations provisioned before that guard landed.
+The order is the fix; the guard stays.
+
+Needs `@ai-matrx/design-system` 0.31.0.
+
+## 0.54.0
+
+**The grid shows a column the panel beside it just added, without a reload.**
+
+Measured on production 2026-09-21, Ridgeline Physical Therapy's patients table:
+"Add field" succeeded, the panel confirmed the column with its own read-back and
+closed — and the grid did not show it until the page was reloaded. The panel was
+telling the truth; the grid next to it was drawing a table that no longer
+existed.
+
+The cause is not in this package's screens, and that is the point: the grid and
+the field panel are siblings, each calling `useFields(tableId)`, each holding
+its own copy, with nothing joining them. Fixing the pair that surfaced it would
+have left the same staleness between every other pair — the rail and the grid,
+the filter and the form builder. So the signal is `@ai-matrx/records` 0.39.0's
+`tableShapeChanged`, which every shape-changing door announces and every reader
+subscribes to, and this package simply inherits it.
+
+`src/shape-changed.test.tsx` holds the five clauses at the pair a person
+actually sees, against the real client through the real doors: a column added in
+the panel appears in the grid beside it; every screen on that table re-reads,
+not one; a screen on a DIFFERENT table is left alone (a signal that woke the
+whole app would be a storm with a sensible name on it); the tick carries no data
+and the listener re-reads through the door; and a retired column disappears the
+same way. Four of the five are RED on 0.53.0's bytes.
+
+Needs `@ai-matrx/records` 0.39.0.
+
 ## 0.53.0
 
 **Every card on every board said "Loading…", forever.**