@ai-matrx/records-ui 0.48.0 → 0.50.0

package/CHANGELOG.md

@@ -1,5 +1,70 @@
 # Changelog — @ai-matrx/records-ui
 
+## 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.**
+
+A trip planner loading the fifty-one US National Parks — name, state, date
+established, area — so she could sort a road trip by region. Crew C, driving the
+real screens on 2026-09-21: *"Every 'Add field' attempt appeared to succeed on
+screen (no error text), but a direct fields() read afterward showed only the
+table's default Title column — none of the 5 fields actually persisted."* The grid
+then drew "This table has no columns yet" over fifty-one real, complete rows.
+
+The panel closed on the DOOR'S answer. **Success is a read-back now**: after the
+declare it asks the table for its columns and looks for the one it just made, BY
+ID. If it is not there the panel stays open and says so — what is true, that no
+record value was lost, and what to do — instead of reporting a success it has not
+confirmed, which is the one thing a person cannot recover from, because they move
+on.
+
+The store's own cause was fixed by lane LIMITS-FIX the same day. This is the half
+that means the SCREEN can never claim it again, whatever the store does next.
+`src/add-field-readback.test.tsx`, three clauses.
+
+**Consumer action:** none.
+
 ## 0.48.0
 
 **The record panel says when it could not read the footnote.**