@ai-matrx/records-ui 0.49.0 → 0.51.0

package/CHANGELOG.md

@@ -1,5 +1,86 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.51.0
+
+**Paste fifty rows out of a spreadsheet, see what they will become, and only
+then write them.**
+
+Real-data crew C, 2026-09-21, entering fifty US airports: *"No 'Paste' control
+(bulk paste of a spreadsheet block) exists on the `/data-v2` grid toolbar —
+only 'New record' (one blank row at a time) and per-cell double-click
+editing"*. That is two hundred and fifty double-clicks for one ordinary
+spreadsheet. The canonical grid has had Excel/Sheets TSV paste since lane
+GRID-ONE; the store's own table never opted in.
+
+It opts in now, with the three things a paste into a real store needs and a
+spreadsheet's paste has none of:
+
+* **Per-cell refusals in plain words, before the write.** Every clipboard
+  string is coerced the way that column's own editor coerces it — `$1,250.50`
+  is 1250.5 on a money column, `(75.00)` is −75, `TRUE`/`yes`/`N` are a tick
+  box — and what cannot be coerced is left alone and named: *"Callout fee holds
+  a number, and “waived” is not one."* A list, a person, a file or another
+  record is an identity rather than a word, so a pasted word into one of those
+  is refused with the control that does hold it. Then the row is put to
+  `predictValueRefusals`, the package's mirror of `custom.validate_values`, so
+  a required column left empty comes back in the STORE's sentence rather than
+  one this screen invented.
+* **A preview.** The grid's new `onPastePlan` means the primitive applies
+  nothing: the person sees the values as they will be stored, how many records
+  change and how many are **created**, and every cell that will be left alone
+  with its reason — then presses the button themselves.
+* **Success only after a read-back.** The writes go through the two doors the
+  grid already uses — `recordUpdate` for a row that exists, `recordWrite` for
+  one that does not — one call per row rather than per cell, and then the table
+  is READ AGAIN and the values counted. The door's yes is not the answer; that
+  confusion is what made "Add field" report success over a column that was not
+  there.
+
+The rows past the last row become new records, which is the whole point: a
+person filling a new table has three rows on screen and fifty lines on the
+clipboard. Needs `@ai-matrx/design-system` 0.29.0.
+
+## 0.50.0
+
+**Rules for entering this stage — the screen that writes a gate.**
+
+A board could enforce a rule and nobody could write one: gates arrived through
+`custom.pipeline_declare`, which is a person at a terminal, an agent, or the
+`pipeline_propose` verb. The homeowner this was built against told her partner
+her rule out loud — "nothing over $5,000 gets approved on a single bid" — and
+there was nowhere to type it.
+
+`StageRulesSection` is a fourth section of the table settings rail, drawn only on
+a table that is a board. One row of header: the heading, which stage, how many
+rules, and Add a rule.
+
+Four things it has to get right, each of which is a defect if it does not:
+
+- **It opens the rule that is there.** `PipelineRule` now carries the gate's own
+  `when` and `demands`, so the editor shows "When Quote amount is more than 5000,
+  it cannot get here unless…" instead of a blank condition it would overwrite on
+  Save. A gate the store never kept the words for says exactly that, with its
+  sentence, rather than being drawn as an empty condition somebody saves over.
+- **It says what the rule would do today**, in cards and by name, while she is
+  still typing — "3 of 13 quotes would be refused today — Primary Bathroom,
+  Primary Bathroom, Guest Bathroom". The old way to find out was to drag a card
+  and be refused.
+- **Its third answer is the organization's, not the rule's.** A gate chooses
+  between turning a card away and asking for approval. Whether a refusal is
+  softened to a warning is one switch for the whole organization, so the screen
+  SAYS which mode it is in instead of offering a third option that quietly means
+  something else.
+- **It will not save a refusal with no words.** The button is absent with a
+  sentence saying what is missing, never present and dead.
+
+**There is still exactly one condition builder.** The form builder's private
+`Condition` moved to `./Condition` as `ConditionRow` and both screens mount it —
+a second one would be a second dialect of the store's one Rule language. Moving
+it found a defect: the value was written as a STRING always, so
+`{"op":"gt","args":[…,{"const":"5000"}]}` compared a number column against text.
+A value that is a number is now written as a number, which is the difference
+between "nothing over $5,000" working and not.
+
 ## 0.49.0
 
 **"Add field" said it worked and the column was not there.**