@ai-matrx/records-ui 0.85.10 → 0.85.13

package/CHANGELOG.md

@@ -1,6 +1,78 @@
 # Changelog — @ai-matrx/records-ui
 
-## Unreleased
+## 0.85.13 (2026-09-25 — published by PUBLISH-SWEEP-6)
+
+**Needs `@ai-matrx/records` 0.58.11.** 0.85.12 was tagged but never reached npm: its packed-consumer
+canary could not import `wholeValueOf` because records 0.58.10 never published. Everything under
+0.85.12 below ships here.
+
+## 0.85.12 (2026-09-25 — tagged by PUBLISH-SWEEP-5; never published, see 0.85.13)
+
+**Needs `@ai-matrx/records` 0.58.10** (the decision hold). Carries UI-FIX-19's dashboard read-back and
+store-sentence-first refusals (`0989c57e69`) and S5-PRIME-2's Undo hold (`3e2c93da3c`). ORDER-FILTER
+shipped in 0.85.11 (below).
+
+### Lane MOVER-BIG-VALUES (2026-09-25)
+
+* **A value kept as a file shows its words and opens the file** (`WholeValue.tsx`): every read
+  layout draws the first words, the whole text's size and "Open the whole text" through the new
+  host port `hrefForFile`; unbound, it says the rest is in a file (never a dead link). The export
+  writes the file's whole content through the new host port `readFileText`.
+
+### Lane S5-PRIME-2, VERIFIER-20 (2026-09-25)
+
+* **A decision is held for Undo before it is made** (Gmail's undo send). Approve or decline — by
+  key, click or a selection — and the row says "Approved · made in 5s · Undo" for the row's
+  `undo_seconds`, then the decision is made through the one door. Undo (or `z`) inside the window
+  calls nothing: the item is waiting again exactly as it was, with no history. A row the store
+  gives 0 (a run already waits on the answer) is made at once and says so. A hold still open when
+  the page goes away or the inbox unmounts is made then, never dropped. Suite
+  `inbox-decision-undo.test.tsx`: RED 5/5 on the prior bytes, GREEN 5/5. Needs `@ai-matrx/records`
+  with `undo_seconds`.
+* **The inbox's clear is named Clear, and its view Cleared** (was Done / Done). A checklist step
+  row already has a Done — it FINISHES the step — so two buttons named Done on one row meant two
+  different things (found walking the live inbox as admin@admin.com). `e` still clears.
+
+### Lane UI-FIX-19 (2026-09-25, VERIFIER-20)
+
+* **A new dashboard says nothing the store did not lose** (VERIFIER-20 a). The read-back treats an
+  empty default the store fills in (`group_by: []`, `filter: {}`) as the same "nothing" that was
+  sent, beside the earlier rule that keys the store adds to a setting are not a loss. Suite: a
+  fresh dashboard created and read back as production stores it — RED 2 on the prior bytes, GREEN.
+* **A refusal is headed by the store's own sentence, and no SQLSTATE or codename reaches a person**
+  (VERIFIER-20 b). `PlainRefusal.storeSaid`; `RefusalNotice` heads with the store's sentence (the
+  generic title only when nothing of its words survived) and says it once. Engineer text (SQLSTATE,
+  an engineer's hint) is on `data-for-engineers` only: no longer the notice's tooltip or a hidden
+  line, and `RefusalLine` likewise. `WhereItLives` passes a refused move's hint through
+  `hintForAPerson`. Suite `a-refusal-heads-with-the-store-s-own-sentence.test.tsx`: RED 2/2 -> GREEN.
+  **Consumer action:** a host that read the notice's `title` for debugging reads
+  `data-for-engineers`.
+
+**Needs the next `@ai-matrx/records`** (`readInViewOrder({ filter })`).
+
+* **A filtered, hand-ordered view reads exactly its rows, in their places.** `useHandOrderRows`
+  takes the view's `filter` and hands it to the order door, which pages the filtered hand order.
+  It used to read the first 500 positions of the WHOLE table and lay them over the list door's
+  page, so a matching row placed past position 500 fell to the end in arrival order and every page
+  read hundreds of rows the view does not show (GRID-MANUAL's named limit). The Grid and the
+  board/gallery/calendar (`useViewRecords`) pass the filter they already hold; page two of a
+  filtered hand order is the door's page two. The client-side `inHandOrder` helper is gone.
+  Tests: `a-hand-set-order-is-the-grids-sort.test.tsx` RED 3/16 on the prior bytes, GREEN 16/16.
+
+## 0.85.11
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/records-ui/v0.85.10..npm/records-ui/v0.85.11 -- apps/shared/records-ui`).
+No source changes intended and no consumer action required.
+
+### Lane ORDER-FILTER (2026-09-25)
+
+## 0.85.10 (2026-09-25 — published by PUBLISH-SWEEP-5)
+
+**Needs `@ai-matrx/records` 0.58.8** (`TableHomeDestination.slug`). Carries UI-FIX-19's move-destination
+address (`461302fbf7`), the lane-tag filter in `hintForAPerson` (`1fd6f9a527`) and the move confirmation
+through the host's notify (`7b7936fb27`).
+Also GRID-MANUAL: the grid draws a hand-set order as its Manual sort (code swept in `dea2f82a14`).
 
 ### Lane GRID-MANUAL (2026-09-25) — a hand-set order is the grid's sort
 
@@ -27,12 +99,6 @@
   GREEN 13/13. **Consumer action:** none; with this published and installed, a hand-ordered view no
   longer needs to open as the Sheet.
 
-## 0.85.10 (2026-09-25 — published by PUBLISH-SWEEP-5)
-
-**Needs `@ai-matrx/records` 0.58.8** (`TableHomeDestination.slug`). Carries UI-FIX-19's move-destination
-address (`461302fbf7`), the lane-tag filter in `hintForAPerson` (`1fd6f9a527`) and the move confirmation
-through the host's notify (`7b7936fb27`).
-
 ### Lane MOVE-AND-OUTSIDER (2026-09-24)
 
 * **A refused move stays on the confirm and says why, with the store's remedy.** `WhereItLives`