@ai-matrx/records-ui 0.5.4 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,90 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.7.0
+
+What the first headless walk of 0.6.0 through a real browser found, in the same
+hour — every one of them on a table a person had just made.
+
+- **A new table takes an empty record.** `DEFAULT_FIELDS` made `title`
+  REQUIRED, so "New record" — which writes an empty record and opens its first
+  cell — was refused (`REC-51: Title is required`) on every table the app makes.
+  A title is what makes a record a chip (REC-2), not a promise it can never be
+  written without; an organization that wants it demanded says so in the field
+  editor and the store then enforces it for everyone.
+- **`TableSettings` can delete the table.** SCR-3 claims rename, reorder,
+  retype and delete; the panel only ever deleted a FIELD, so a table made in the
+  product could not be got rid of from anywhere in it. It is the same soft
+  delete every record gets, through the same door, and the consequence is named
+  before the second press. `onDeleted` lets the host leave the page, and
+  `TablePage` passes its `onLeave`.
+- **Nobody conflicts with themselves any more.** Three separate paths wrote a
+  record twice against one version and were — correctly — refused `PT409` by the
+  store, so the screen showed a person a conflict with nobody but themselves:
+  Tab fired the cell's key handler AND its blur handler; two cells of one record
+  were written in parallel; and `useRecordVersion` never moved after a save, so
+  switching a saved view's layout twice, or saving a form twice, conflicted with
+  the save before it. One commit per opening, one write at a time per record,
+  and every successful write hands its new version back.
+- **The demo harness renders like the product.** It imported the design
+  system's structural sheet and nothing else, so every page was unstyled HTML in
+  a real browser while `pnpm test` was green. It now runs Tailwind over this
+  package's own source, and the address bar takes `?demo=` and `?table=` so a
+  walk can make a throwaway table, work in it and delete it again.
+
+### Consumer action
+
+**`useRecordVersion` now answers `{ version, note }` rather than a number.** A
+screen that writes the same record more than once must hand each successful
+write's new version back through `note(...)`, or the next write will be refused
+as a conflict with the person who just made the last one. Nothing else changed:
+`version` is the same value the hook used to return, and `null` still means "no
+version was read", which is the store's ordinary last-writer-wins write.
+
+A host that shows `TableSettings` on a page about one table should pass
+`onDeleted`, or the person is left on a page about a table that is gone.
+
+## 0.6.0
+
+Editing where the value is shown, and four other things an independent walk of
+the real screens (19 September) found a person could not do.
+
+- **`Grid` edits in place** (`src/gridEditing.tsx`). Click a cell, or focus it
+  and press Enter, and the Field's own editor opens there; Enter saves, Escape
+  cancels, Tab saves and opens the next cell. The write goes through the one
+  write door carrying the version the person started from, so the STORE decides
+  whether somebody else got there first — and on `PT409` the cell shows the
+  other person's value with Try again and Keep theirs beside it. Optimistic,
+  and the value comes back off the screen the moment the store refuses.
+- **Rows can be added and deleted from the grid.** "New record" writes an empty
+  record and opens its first cell; a Table with a required Field refuses in its
+  own words and the grid offers the whole form by name. Delete names the
+  consequence and the Table's own restore window before it happens.
+- **`PersonPicker`** (new) and the **`members` port** on `RecordsUiProvider`. A
+  person field offers the organization's members and resolves whoever is picked
+  to their record in the kernel Person Table. It no longer offers the Homes
+  that also live in that Table.
+- **Kanban and calendar carry the picker their sentence always promised.** The
+  group-by Field and the date Field are chosen on the board and saved onto the
+  view record (`onViewChange` → `viewPatchDocument`), so the choice is
+  remembered per saved view. `ViewBar`'s duplicate layout `select` is gone: the
+  switcher owns the layout, and the two controls can no longer disagree.
+- **`TablePage` says when a table is not reachable** (`TABLE_NOT_REACHABLE`)
+  instead of rendering an endless skeleton, and takes `onLeave` for the way out.
+- **Names, never tokens** (`src/names.ts`). Field headers, table cards, record
+  chips and type words all read as a person writes them; the app's own
+  bookkeeping Tables get their own lane in `TablesHome` ("Kept by the app")
+  instead of sitting among a person's data under their slug.
+- A `json` parity editor, and honest empty states for a choice field whose
+  options Table is empty versus one that names no Table at all.
+
+### Consumer action
+
+`RecordsUiHost.members` is OPTIONAL: unbound, a person field is absent with
+`NO_MEMBERS_REASON` rather than offering the wrong things. Bind it to your
+host's organization roster to get the picker. `Grid` takes `editable` (default
+true) — pass `false` on a read-only surface. `TableLane` gained `"app"`, so an
+exhaustive switch over it needs the new arm.
+
 ## 0.5.4
 
 Makes the live FormBuilder certification wait for the editor state that follows