@ai-matrx/records-ui 0.85.4 → 0.85.7

package/CHANGELOG.md

@@ -1,6 +1,141 @@
 # Changelog — @ai-matrx/records-ui
 
-## Unreleased — lane DATA-V2-FACE (2026-09-24)
+## 0.85.7 (2026-09-24 — published by PUBLISH-SWEEP-5)
+
+**Needs `@ai-matrx/records` 0.58.6** (the inbox doors: `inboxSnooze`, `inboxClear`, `inboxCounts`,
+`workInbox({view})`). Also carries GRID-TAILS' agent-button target with the table's name, fields,
+document and level (`676aa103ca`, reached main through an integrator sweep) and VIEW-KEYS-SHEET's
+`designatedLayoutOf` (`4a049f0c97`).
+
+### Lane S5-PRIME-2 (2026-09-24)
+
+* **`ActionInbox` snoozes and clears at Superhuman's bar.** `s` opens the snooze choices on the row
+  (Later today, Tomorrow 8 AM, Next Monday 8 AM — `1`/`2`/`3` — or a picked date and time) and it
+  comes back to the top of the inbox then; `e` clears a piece of work you have seen (it comes back
+  if somebody else changes it); `z` or the Undo in the status line takes either back. **A decision
+  still owed has no Done control** — deciding is what takes it away. Three views, `v` cycles them —
+  Inbox, Snoozed (each says when it comes back; `u` or Unsnooze), Done (`u` or Put back) — each
+  counted by the store's `inboxCounts`, the same number the shell badge shows. Empty Snoozed and
+  Done views say what they are for. Only this person's inbox changes: nothing is written on the
+  approval or the record.
+* **A checklist step is drawn once.** The inbox's "Your checklist steps" group shows only the steps
+  the inbox door still lists as waiting (so a snoozed or cleared step leaves it too), and those steps
+  are no longer drawn a second time as assignment rows above; each carries Snooze and Done.
+  `MyChecklistSteps` gains `onlyIds`, `onSteps` and `actions`.
+* Exports `snoozeChoices`, `SnoozeChoice`, `INBOX_VIEWS`. Suite `inbox-snooze-and-done.test.tsx`:
+  RED 6/6 on the prior bytes, GREEN 6/6. Needs `@ai-matrx/records` with the S5-PRIME-2 inbox doors.
+
+### Lane S5-PRIME (2026-09-24)
+
+* **`ActionInbox` reaches Linear's and Superhuman's table stakes.** Grouped by kind (default:
+  Approvals, Agent proposals, Assigned to you) or by table, each heading counted; a `Group by`
+  control and `g` cycle kind → table → none; `j/k`, `x`, `a/d` walk the rows in the order they are
+  drawn. `h` / "Show decided" brings closed items in, and **a closed item says who decided it and
+  when** ("Approved by … · <time>", or "Withdrawn when … archived it") with the store's sentence and no
+  controls. **An empty inbox says why** (what arrives here; nothing ever decided; or, narrowed to a
+  table, how many wait in other tables with "Show all"). `tableId` now actually narrows (it kept every
+  row). Exports `groupInbox`, `InboxGrouping`, `INBOX_GROUPINGS`; `enumLabels` adds
+  `WORK_INBOX_KIND_GROUP_LABEL`, `WORK_APPROVAL_STATES`, `WORK_APPROVAL_STATE_LABEL`. Suite
+  `inbox-groups-and-closed-items.test.tsx`: RED 6/6 on the prior bytes, GREEN 6/6. Needs
+  `@ai-matrx/records` with the S5-PRIME `WorkInboxItem` fields.
+
+### Lane VIEW-KEYS-SHEET (2026-09-24)
+
+* **The Sheet is designated one way: `layout: "sheet"`.** `designatedLayoutOf` no longer reads the
+  mover's mark (`moved_from.kind = "default_view"` with no layout) as the Sheet; `moved_from` is
+  provenance only. The store's view-keys registry declares `sheet` as a layout, the mover writes it,
+  and a production repair wrote it on every copied table's default view (none left on the mark
+  alone — measured on production before this change). Suites: `a-table-opens-the-way-it-was-designated.test.tsx`
+  (the mark alone designates nothing: RED on the prior bytes, GREEN), `the-designated-default-wins-over-a-seed.test.tsx`.
+
+### Lane UI-FIX-18 (2026-09-24)
+
+* **A card is titled by what names its record** (VERIFIER-18 H5). New `cardTitleField(fields, titleKey,
+  exclude)` in `names.ts`: the Table's `title_field` → a conventional name key → the first text column
+  in declared order → any other column that can title; never a checkbox, the group/stage column or a
+  system stamp. The kanban, the calendar and the pipeline all read it (the kanban used to take the
+  first non-group column, so a board grouped by Stage read "false"/"true"). The table's title column
+  is handed down by the host that already read the table — new `ViewSwitcher` prop `titleField`
+  (TablePage passes it) and `PipelineBoard` prop `titleKey`; neither reads the table a second time.
+  Suite `a-card-is-titled-by-what-names-its-record.test.tsx` (RED 1/7 on the prior bytes, GREEN 7/7).
+* **A date is a date — the control and the text follow the stored value, never `config.kind` alone**
+  (correction to the 0.85.6 date line). `carriesTimeOfDay(field, value)` / `dateFormatFor(field, value)`
+  read the value's shape: a value with no time part (a date of birth on a `kind: "datetime"` Field) gets
+  a date-only control and a date-only reading in the grid, the form, the panel and the calendar; with no
+  value, only `format: "datetime"` or the store's own Created / Last changed stamps carry a time. The
+  one-day-early fix stays: a bare date is read as a local calendar day. The recorded public form's
+  "date of birth" asks for a date again (`demo/form-runner.test.tsx` GREEN on the unchanged fixture);
+  the date suite gains the birthday clauses (GREEN 15/15).
+* **A dashboard save is confirmed, and what the store did not keep is said** (VERIFIER-18 M2). Every
+  `declare()` on the canvas (shape, grouping, comparison, target, remove) reads the dashboard back and
+  `whatTheStoreDidNotKeep(sent, stored)` names any setting the store answered differently, on its block
+  ("The store did not keep its comparison for “Jobs by status”…"), in a status line; the controls show
+  what the store really holds. Suite `a-dashboard-save-says-what-the-store-did-not-keep.test.tsx`
+  (RED 4/4 on the prior bytes, GREEN 4/4); S3 and canvas suites still green.
+* **A withheld value says why, in every layout** (VERIFIER-18 H1, the screen half). New `withheld.tsx`
+  is the one helper: `withheldNoticeOf(hidden, key)`, `withheldSentence(field, notice)` (the store's
+  own `says` — "Budget with contingency is worked out from Budget, which you have not been given." —
+  or its reason, the level it needs and the other way in), `WithheldValue` and `WITHHELD_WORD`.
+  `RecordValue` takes `withheld` and draws "Withheld" with the sentence on hover and for screen
+  readers, never "—"; the grid cell, the editing cell, the gallery, the record panel and the public
+  page hand it `row.hidden[key]`; every card (kanban, calendar, pipeline, unplaced list) reads one
+  `cardWords(record, field, labels)`; the export writes "Withheld: <sentence>". A source guard refuses a
+  `<RecordValue` that draws a row's value without its notice. Suite
+  `a-withheld-value-says-why-in-every-layout.test.tsx` (RED 5/6 on the prior bytes, GREEN 6/6).
+* **`TablesHome makingOnly`** (VERIFIER-18 M3): only the ways to make a table (New table, Start from an
+  example, the import that follows) and none of the lists — no table sections, no dashboards list (and
+  no `dashboards` read), no booking pages, no "Show everything" line. matrx-frontend's organization hub,
+  which lists the organization's tables (pick lists under "Kept by the app"), dashboards and booking
+  pages itself, passes it once this version is in its lockfile, so the page draws one list. Default
+  false. Suite `the-organization-page-lists-its-tables-once.test.tsx` (RED 1/2 on the prior bytes,
+  GREEN 2/2).
+* **Exported for hosts:** `resolveTableStyle` and `styleFromDecorations` (the one color resolver —
+  matrx-frontend's Sheet moves onto them and deletes its own translation once this version is in its
+  lockfile), the date helper (`dateText`, `calendarDayOf`, `calendarDayLabel`, `carriesTimeOfDay`,
+  `dateFormatFor`, `hasTimePart`, `isDateField`) and `cardTitleField`.
+
+## 0.85.6 (2026-09-24 — published by PUBLISH-SWEEP-5)
+
+**Needs `@ai-matrx/records` 0.58.4** (published first: its catalogue carries the doors this release
+draws — `table_home`, `table_move`, `portal_form`, the `entity_reference` kind). 0.85.5 (the release
+run's automatic tag) never reached npm: `every-kind-the-store-takes-is-on-the-menu` found
+`entity_reference` published by the store with nothing classifying how the menu sends it (it goes as
+its word, with `allowed_types`, exactly like `signature`); and `every-table-row-says-where-it-lives`
+asserted the door-absent sentence for `custom.table_home`, which is live now — it asserts the store is
+asked once, when the chip is pressed, and that its organization is drawn (RED on the pre-apply
+catalogue, GREEN on the live one).
+
+### Lane UI-FIX-18 (2026-09-24)
+
+* **A date reads the same day in every layout, in every time zone** (VERIFIER-18 H2). New `dates.ts`
+  is the one date helper: `dateText` prints through the design system's registry (`formatFieldValue`,
+  what the grid already used), `calendarDayOf` / `calendarDayLabel` file and head a calendar day
+  without UTC midnight, `carriesTimeOfDay` / `dateFormatFor` read `config.kind` (with the older
+  `format: "datetime"` honoured). `scalarText` (gallery, cards, record panel, history), the calendar,
+  the date editor and `formatForField` all read it. A bare `2026-04-01` is Apr 1 in Los Angeles and in
+  Tokyo, never Mar 31. Suite `a-date-reads-the-same-day-in-every-layout.test.tsx` (RED 7/13 on the
+  prior bytes, GREEN 13/13), with a source guard refusing `toISOString().slice(0, 10)` and UTC-midnight
+  dates in any screen.
+* **Created time and Last changed time print like every other date and time** (VERIFIER-18 M1):
+  `formatForField` answers `{ id: "datetime" }` for `config.system` `created_time` / `modified_time`, so
+  the grid, gallery, record panel and the panel's "Worked out by the system" line read
+  *Sep 24, 2026, 5:13 PM*, not `2026-09-25T00:13:34.564Z`.
+
+### Lane DATA-V2-FACE-2 (2026-09-24)
+
+* **One name, one place: the Grid draws no name of its own.** `Grid` no longer draws the table's name
+  and row count above the records, nor the design system's per-browser working-view tabs ("Default
+  view" + "+") and "Default view ▾" menu (`viewTabs={false}`, no `tableId` handed to `MatrxDataTable`).
+  The page that places the grid names the table; the page's view bar is the one place views live; the
+  data table's footer counts the rows. `toolbarActions` still draw, on their own row, only when given.
+  Suite: `the-grid-names-nothing-the-page-already-names.test.tsx` (RED 3/3 on the prior bytes, GREEN 3/3).
+* **`defaultViewOf(views)`** — when two views both claim the table's default (the mover's designated
+  Sheet and a page seed a later move of the view bar's older store brings in, both "All records"), the
+  designated one wins; `ViewBar` opens on it. Suite `the-designated-default-wins-over-a-seed.test.tsx`.
+* **`WhereItLives` `variant="title"`** — quiet, frameless, for the page header beside the object's name
+  (matrx-frontend's /data-v2 table header uses its own copy today; the swap keeps the look).
+
+### Lane DATA-V2-FACE (2026-09-24)
 
 * **A table opens the way it was designated, and its face is one row.** `TablePage` draws, above the
   records, only the saved-views bar (when the table has two or more views, or the person asked for it),
@@ -17,13 +152,16 @@
   (no second "All records" is seeded beside it). A package layout (`grid`, `kanban`…) never designates,
   because a click writes those; on a designated table a layout picked from the menu is for the visit and
   is never written over the designation.
+* `TablePage` takes `leading` (the host's quiet where-it-lives chip, at the start of the one row) and
+  `menuExtras` (host capabilities in the table menu, e.g. "When a row changes, run an agent…").
+  `designatedLayoutOf`, `tableOpening` and `TABLE_MENU` are exported.
 * `ViewSwitcher` takes `chooser={false}` (the page draws the choice) and `openExport`; a host layout's
   `render` receives `openExport`, so the Sheet's "Export this table…" opens the page's own export.
   `ViewBar` takes `quietWhenAlone` and `onViews`.
 * Tests: `a-table-opens-the-way-it-was-designated.test.tsx` (RED 3/3 against the pre-lane page, GREEN
   8/8); `every-table-can-reach-its-archive.test.tsx` now reaches Archived through the menu.
 
-## Unreleased — lane SC-1-TAILS (2026-09-24)
+### Lane SC-1-TAILS (2026-09-24)
 
 * **`WhereItLives`** — the one chip for "Lives in <organization>" and moving a table, moved here from matrx-frontend
   so every host (and `TablesHome`) mounts the same builder. The consequence is said in the panel before "Move it";
@@ -35,6 +173,12 @@
 * **Consumer action:** matrx-frontend passes `organizationName` to `TablesHome` in `OrganizationHub.tsx` and swaps
   its three `WhereItLives` call sites to this export.
 
+## 0.85.5
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/records-ui/v0.85.4..npm/records-ui/v0.85.5 -- apps/shared/records-ui`).
+No source changes intended and no consumer action required.
+
 ## 0.85.4 (2026-09-24 — published by PUBLISH-SWEEP-5; folds every section below down to 0.84.8)
 
 **0.85.3 never reached npm** (the release run's automatic tag, run 36064683447): every test passed
@@ -80,6 +224,13 @@ integrator's sweeps (`79b505cfa5`, `9a6618f2d0`, `452e363c2e`) rather than their
   Every change is one `custom.action_declare` with the whole list; a store refusal is shown under the
   form and what was typed stays. Same controls as the field panel. Suite
   `an-owner-writes-the-tables-own-buttons.test.tsx`: RED 6 on the bytes without the section, GREEN 8.
+* **An agent button hands over what the grid holds — the host reads nothing on press.** `runAgentAction`'s
+  target gains `tableName`, `fields`, `document` (the row as this reader sees it) and `level`. **Consumer
+  action:** a host that re-read the table, its fields, the record or the level to start the job drops those
+  reads and takes them from the target. Test RED without them, GREEN with them.
+* **An agent action is never labelled "a column it changes is gone".** The store answers `runnable: false`
+  for every agent action; the badge is for update actions only (found on the live walk of Rincon's Invoices;
+  test RED → GREEN).
 * **A button declared in settings appears on the grid beside it without a reload.** `rowActionsChanged(tableId)`
   (gridActions.tsx): every mounted `useTableActions` of that table reads `custom.row_actions` again after a
   declare. Test RED without the listener, GREEN with it.