@ai-matrx/records-ui 0.85.13 → 0.85.16

package/CHANGELOG.md

@@ -1,5 +1,118 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.85.16
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/records-ui/v0.85.15..npm/records-ui/v0.85.16 -- apps/shared/records-ui`).
+No source changes intended and no consumer action required.
+
+## Unreleased — lane VIEW-STATE-PERSONAL (2026-09-25)
+
+Needs `@ai-matrx/records` with `viewLookRead` / `viewLookSet` (Unreleased) and the store doors
+`custom.view_look_read` / `custom.view_look_set` (live on production, 2026-09-25 19:19Z).
+
+### A look at a view is yours until you save it (VERIFIER-23 item 1)
+
+* **Every view-configuration change a person makes while looking is HER look, not the view's.** On
+  production the owner's *Group by → Status* on a board became the tenant liaison's board the next
+  time she opened it: `TablePage` merged every pick onto the shared view (`view_declare`). Now a
+  pick of the board's grouping, the calendar's date field, a sort, a filter, a hidden column, a
+  width, a colour or the layout is kept for that person through `custom.view_look_set` and laid
+  over the view (`applyLook`); a reload keeps it; nobody else sees it. The view row is never
+  written by a pick. (Airtable and Notion's rule; Notion's "Save for everyone" / "Reset".)
+* **One line says so, with its doors** (`[data-view-look]`): *"You changed how this view looks. Only
+  you see it."* · **Save to view** (someone who may edit the table; the one `view_declare`, and the
+  default view's layout stays the person's look — "Make … the default" is that door) · **Save as
+  new view** (editor; the look becomes a view of its own) · **Reset to view** (everyone; the look is
+  archived). A viewer never sees Save to view or Save as new view — absent, not dead.
+* **Reorder is offered only to someone who may edit the table**: a hand-set order is the view's
+  sort for everybody (`view_record_order_set` now needs editor; the store refuses it otherwise).
+* New module `viewLook.ts` (exported): `ViewLook`, `lookPart`, `lookDocument`, `lookFromDocument`,
+  `applyLook`, `lookDiffers`, `saveToViewPlan`, `readLooks`, `keepLook`, `LOOK_WORDS`.
+* Suite `a-look-at-a-view-is-yours-until-you-save-it.test.tsx`: RED 4/6 on the prior `TablePage` /
+  `ViewSwitcher` (the pick sent `view_declare`; no look, no Save / Reset) → GREEN 6/6.
+
+## 0.85.15 (2026-09-25 — published by PUBLISH-SWEEP-7)
+
+The tagged 0.85.14 never reached npm: its deterministic gate failed on `NeverRecorded … custom.field_declare` (fixture recorded against records 0.58.11). The fixture is re-recorded (below); everything 0.85.14 carried ships here. Needs `@ai-matrx/records` >= 0.58.13 (`viewDesignate` / `custom.view_designate`).
+
+### A held decision survives a reload (GATES-TAIL, VERIFIER-21 #3r, 2026-09-25)
+
+* **`ActionInbox` keeps every open Undo hold in the browser until the decide door answers for it**
+  (`localStorage` `records-ui:held-decisions`, one entry per approval). A reload during the
+  five-second hold used to kill the made-on-pagehide request with the page, and the reloaded inbox
+  showed the approval pending with no word, though the screen had said "Declined". Now the
+  reloaded inbox shows it still held ("Declined · Undo") for the rest of its window, then makes it;
+  past its window it is made at once and says so. Undo forgets it; an approval the store no longer
+  lists as waiting on this person is forgotten. The store keeps no pending-decision state, so this is
+  a browser-side promise; the store still decides who may decide. Suite RED 2/2 → GREEN 7/7.
+
+### Gate recording is re-runnable and leaves nothing behind (2026-09-25)
+
+* **The deterministic suite is re-recorded against `@ai-matrx/records` 0.58.12** (demo only; no
+  shipped code changed). The publish of 0.85.14 failed on `NeverRecorded … custom.field_declare`
+  because 0.58.12 sends a column's word as `type`; `demo/fixtures/doors.json` is re-recorded.
+* **Why re-recording kept failing.** Not a name collision — every recording already names its tables
+  with a per-run stamp saved in the fixture. The first-time walk asserted a freshly declared table
+  had NO columns, which the store stopped producing on 2026-09-21 (a declared name is a Field) and
+  cannot produce at all now (`custom.field_retire` refuses a table's title column, REC-2). The walk
+  now asserts what the store makes, as `live-smoke` already did: the declared column, drawn, and no
+  "no columns yet" sentence over it.
+* **A failed recording never overwrites the fixture, and every run archives what it made.** The
+  recording seam keeps a ledger of every record a creating door returned; `afterAll` soft-deletes
+  exactly those, newest first, whatever happened (`recorded-doors.ts`, `deterministic.test.tsx`).
+* **`live-smoke` takes back its package table's Home** (read from the Table's `parent_id`). Every gate
+  run used to leave one "<name> views Home" in the test organization; 144 stray walk records in
+  Test's Org (test@test.com) were archived through `custom.record_delete`.
+
+### Lane VIEW-SWITCH-NOT-DESIGNATION (2026-09-25)
+
+* **A look at a table never changes how it opens** (`TablePage.tsx`, `views.ts`; VERIFIER-21).
+  Pressing Kanban or Calendar saved `layout` onto the table's DEFAULT view, so the next person to
+  open the table landed in the last look anybody took. A press on the default view now carries
+  every other key it changed (a board's grouping, a calendar's date, a colour) and never `layout` or
+  `isDefault` (`viewPatchFor`); the store refuses them through `view_declare` by name. The one way to
+  change how a table opens is the menu's **"Make <layout> the default"** — offered only to someone
+  who may edit the table and only when what is showing is not already how it opens — sent through
+  `designateView` → `custom.view_designate` (editor). New exports: `viewPatchFor`,
+  `openingLayoutOf`, `makeDefaultLabel`, `designateView`. Test:
+  `a-look-at-a-table-never-changes-how-it-opens.test.tsx` (RED on the prior `TablePage`: two layout
+  writes onto the default view and no designate control; GREEN 6/6).
+* **A date stays a date on a board card** (`CardDates.tsx`, `ViewSwitcher.tsx`, `Pipeline.tsx`;
+  VERIFIER-21 item 5). Kanban and pipeline cards carry the table's date columns under the title,
+  drawn by the one value renderer (`RecordValue`), so "Mar 1, 2026" reads the same on the card as
+  in the Sheet, the Grid, the record panel and the Calendar; a blank date draws nothing and a
+  withheld one says so. Test: `a-board-card-shows-its-date.test.tsx` (RED: the card read only
+  "INV-20417"; GREEN, also under `TZ=America/Los_Angeles`).
+
+### Lane BIG-VALUES-READERS (2026-09-25)
+
+* **A row read through the matching door opens its whole text** (`values.tsx`): every store read
+  door (`custom.read_records_matching` — the grid's — `read_record`, `read_records`,
+  `read_records_by_ids`, `read_records_archived`) now carries a value-kept-as-a-file's pointer
+  (`_values.<key>.src` -> `_sources.<ptr>`, file fields only), so `wholeValueOf` finds it and the
+  grid cell shows "Open the whole text" on every read path. `ProvenanceBadge` now draws nothing for
+  such a pointer (the cell already says the text is in a file) instead of the pointer's raw fields.
+  Test `a-row-read-through-the-matching-door-opens-its-whole-text.test.tsx` (RED 1/3 -> GREEN 3/3).
+  Consumer action: none.
+
+### Lane RC-B2b (2026-09-25)
+
+* **Authored form text reads the way it was written** (`host.tsx`, `FormRunner.tsx`): new optional
+  host port `RecordsUiHost.renderText(text, where)` with `RenderTextSlot`
+  (`"form-intro" | "form-help" | "form-thank-you"`). A form's intro, a question's help and the
+  thank-you body go through it, so the host's one markdown renderer draws `**bold**`, math and
+  links; unbound, the text shows exactly as written. Suite
+  `authored-form-text-reads-through-the-host.test.tsx`: RED with the port ignored, GREEN 2/2.
+  **Consumer action:** matrx-frontend wraps `/f/[formId]`'s `FormRunner` in
+  `RecordsUiProvider value={{ renderText }}` returning `RichContentInline` (phrasing, valid in `<p>`).
+
+## 0.85.14 (tagged by the auto release; never published, see 0.85.15)
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/records-ui/v0.85.13..npm/records-ui/v0.85.14 -- apps/shared/records-ui`).
+No source changes intended and no consumer action required.
+
 ## 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