@ai-matrx/records-ui 0.38.0 → 0.40.0

package/CHANGELOG.md

@@ -1,5 +1,63 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.40.0
+
+**Pressing "Settings" on a table crashed the whole page, and had since the
+enrichment panel was added.**
+
+Lane LAND-SCREENS pressed it in a production build of the app, signed in as the
+admin who owns the table, and the route went to the application's global error
+boundary with React #310 — *"Rendered more hooks than during the previous render."*
+Everything on that panel went with it: rename the table, add a column, take one
+off, reorder, delete the table, and the enrichment panel itself, which lives behind
+a column's own row and was therefore unreachable in the shipped build.
+
+**The cause, and why no suite saw it.** `TableSettings` declared `useState` for the
+enrichment panel BELOW three early returns, one of which fires on the FIRST render
+of every real mount: a host that lets the store decide rights binds no `rights`
+port, so `useTableRights(table.data)` answers `NO_RIGHTS` until `useTable` and
+`custom.my_level` come back. Render one ran eight hooks and returned the "you may
+not change the structure" line; render two, a moment later, ran nine. Every test in
+this package binds `rights: () => tableRightsAt("admin")`, which never takes that
+return — so the panel was only ever rendered with nine hooks and the order never
+changed.
+
+`src/TableSettings.hooks.test.tsx` mounts the panel with NO rights port, which is
+the seat the product actually uses, and fails with that exact error on the previous
+hook order.
+
+Also: `src/form-publish.test.tsx` had two TS7006 implicit-`any` parameters that had
+`tsc --noEmit` red on this package on `main`. Typed; the package typechecks clean.
+
+## 0.39.0
+
+**The kanban view becomes the board, with the store judging every drag.**
+
+`PipelineBoard` renders THROUGH the view that already exists — `ViewSwitcher`'s
+kanban layout — rather than beside it. It draws the very same rows the view holds;
+what it adds is the store's judgement.
+
+* **Drag between columns.** A drop asks `custom.pipeline_transition_refusal` first
+  and either writes the move or leaves the card exactly where it was, carrying the
+  store's own sentence, verbatim. Nothing is written on a refusal, so there is no
+  snap-back to animate — the card never moved.
+* **A stage's demands, prompted on the way in.** When the refusal names the columns
+  a stage needs, they appear on the card with a field each and one button, so the
+  person finishes the move instead of being sent away from it. Until every demand is
+  answered there is no button to press, rather than one that looks live.
+* **Column headings carry the store's numbers** — the count, the chosen measure's
+  total, and the column's limit — over every record this person may see, not over
+  the page the screen happened to load. Which column is totalled is a fact about the
+  VIEW, saved on it like its colours.
+* **A work-in-progress limit shows on the column it belongs to**, and a column over
+  its limit says so in a sentence rather than only turning red.
+* **A viewer's card has no drag handle at all.** Absent rather than dead.
+
+A table that is not a pipeline draws the plain kanban exactly as before; the
+decision is the Table's own `stage_field`, asked once, never guessed from the shape
+of a Choice column.
+
+
 
 
 ## 0.38.0 — 2026-09-20