@ai-matrx/records-ui 0.83.1 → 0.84.0

package/CHANGELOG.md

@@ -1,5 +1,51 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.84.0
+
+**A refusal is said once, with the doors that fit it, and a change a person made is kept or
+said — never dropped.** (lane RECORDS-UI-FIX, VERIFIER-15 H2, H3, M3, M4, M6, M7.)
+
+* **The grid's cell refusal is the one notice.** A rule refusal (`-3` in a column "at least
+  0") used to draw a small red line with *Try again* (which re-sent the refused value) and
+  *Keep theirs* (conflict wording when nobody else wrote). It is now `RefusalNotice` with
+  **Keep editing** — the cell reopens holding `-3`, the reason still beside it — and
+  **Discard**. *Try again* / *Keep theirs* appear only on a real version conflict, beside
+  the other person's value. A tick box's refusal carries Discard.
+* **The record form says a refusal once, with Keep editing / Discard, and before Save.** The
+  mirror's per-column notice is the store's rule, so the store's copy under the form is no
+  longer drawn beside it; the mirror speaks the moment a changed column would be refused.
+  What was typed survives the (slower) version read landing late. An edit sends only the
+  columns the person changed, and a Save with nothing changed writes nothing.
+* **A board's layout or grouping change is kept, or said.** Every view save carried a version
+  read from the view's history, which can stop short of the record, so every Kanban / Group
+  by press was refused `stale_write` and dropped in silence. New `saveViewPatch` (the one
+  view-save door) writes on the version the refusal names; a save still refused is said
+  through `RefusalNotice` with Try again / Discard.
+* **"Someone else wrote first" only when somebody did.** The store's `contested_fields`
+  carries each patched column's current value; when every one is still what the screen
+  started from, the write goes once more on the winning version (the grid cell session, the
+  record form and saved views apply the same rule — internal `updateOnTheWinningVersion`).
+* **The next digest summary is never in the past.** New export `nextSummaryAt(subscription,
+  now)` carries a passed due time forward by whole periods to the first slot after now,
+  keeping the store's alignment (tested at a fixed clock).
+* **Table Settings never cuts a field name to two letters** — the name wraps with a readable
+  minimum and the row wraps its controls first.
+* **On a phone the table's rail is a sheet over the table** — below the design system's
+  breakpoint (`useIsMobile`, 768px) it renders through the canonical `BottomSheet`, the way
+  `Dialog` and `CommandDialog` already do; dragging it down closes the rail.
+* Tests (each shown failing on the prior bytes): `src/a-refused-cell-keeps-what-you-typed`,
+  `src/a-form-refusal-is-said-once-with-its-doors`, `src/a-board-layout-change-is-kept`,
+  `src/the-next-summary-is-never-in-the-past`, `src/a-rail-on-a-phone-is-a-sheet`, and a
+  new clause in `src/TableSettings.hooks.test`.
+
+**Store-side, reported to the chair (not in this package):** `custom.record_update` of an
+unchanged value moves `version` and writes no history row (reproduced on the dev clone), and
+the digest runner computes the next slot from the last summary SENT, so an empty window
+freezes it.
+
+**Consumer action (matrx-frontend):** none required — install picks it up. A host that
+shows a digest's next time outside `SubscriptionsPanel` should use `nextSummaryAt`.
+
 ## 0.83.1
 
 **A table shared by link is in the World lane, not Community.** (lane HUB-FIX, chair ruling

package/dist/index.cjs

@@ -256,6 +256,7 @@ __export(src_exports, {
   mayNotRestoreLine: () => mayNotRestoreLine,
   memberName: () => memberName,
   nextInWords: () => nextInWords,
+  nextSummaryAt: () => nextSummaryAt,
   openingRail: () => openingRail,
   openingView: () => openingView,
   pageViewFromParam: () => pageViewFromParam,