@ai-matrx/records-ui 0.61.0 → 0.63.0

package/CHANGELOG.md

@@ -1,5 +1,76 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.63.0
+
+**A relation cell finally SHOWS what its column was configured to show, and the
+six hand-rolled copies of "what is this id called" are gone — all six, by moving
+the code, none by allowlisting.** (lane RELATION-DISPLAY-2.)
+
+* **The display spec reached the store in 0.62.0 and no screen could read it.**
+  REL-DISP gave a relation column a `display` — which of the target's columns it
+  shows, in what order, joined by what — and shipped `ReferenceBuilder` to
+  configure it. But `labels.tsx`, which every grid, board, gallery, calendar and
+  peek cell reads through, resolved names ITSELF: 200 rows of the target Table
+  plus `tableList()` for its `title_field`. So a person could set Rincon
+  Plumbing's `jobs.customer` to read "first name + last name", press Save, and
+  the board would go on drawing "Maria Chen" for both of the Maria Chens. The
+  builder wrote a setting that nothing displayed.
+  `labels.tsx` now fetches NOTHING up front and asks `relation_words_many` for
+  the ids the page actually draws — one call per Field per tick, the store's one
+  resolver, this column's own spec, the visibility ladder asked BEFORE the name
+  is read, and no 200-row prefetch ceiling. Its own comment recorded the batch
+  door as missing ("there is still no batch door on the store"); REL-DISP built
+  it, so the per-id `record_read` lane is gone entirely.
+* **`RelationPicker` offers the same words the cell shows.** It had the third
+  copy of the derivation, which is why a column configured to read "Maria Chen —
+  Rincon" still asked a person to choose between two identical "Maria Chen"s.
+  One `relation_words_many` now covers the offered rows AND the already-picked
+  ids, so what you pick from and what you read back can never disagree.
+* **`recordNameIn` / `rowNameIn` — the one naming call for a record whose Table
+  you already hold.** `Grid` (the Talk action), `Peek` (the peek title),
+  `PortalsPanel`'s client picker and the host test bench were each writing
+  `recordName(row.document, table.title_field)` out by hand. That is not the
+  store's question — there is no id to resolve — but it is the same question
+  answered five times in four files, which is how a Table titled by `cname` read
+  "Untitled" on one screen and correctly on the next. It lives once now.
+  NOT a second resolver: hold an id, and the answer is still the store's.
+* **`check:one-reference-builder` goes from a baseline of SIX to ZERO.** The
+  guard shipped saying out loud that allowlisting the six "would be the same lie
+  with extra steps". None was allowlisted. Proven red on a planted copy at
+  baseline 0, then green.
+
+**Consumer action:** none for a host that only mounts these components — the
+change is behind them. A host resolving a relation label itself should delete
+that code and call `client.relationWordsMany`; one holding a Table and a
+document should call `recordNameIn` / `rowNameIn`.
+
+## 0.62.0
+
+**THE ONE REFERENCE BUILDER.** (lane RELATION-DISPLAY.)
+
+*Written after the fact by lane RELATION-DISPLAY-2 — 0.62.0 published with no
+entry here, and a released version with no changelog row is a version nobody
+downstream can read. Sourced from that lane's own progress note, not invented.*
+
+* **`ReferenceBuilder` + `previewWords`** — the one place a reference to another
+  table is built. It asks, in the order a person thinks of it: which table →
+  what a record of it is called TODAY (its own reference column, SHOWN rather
+  than hidden) → only if they want it, which columns instead, in order, with a
+  separator → a preview on that table's REAL first rows. `FieldEditor`'s private
+  `TableToPointAt` is deleted and this stands in its place.
+* **A relation is asked its questions when EDITING too.** That branch skipped
+  every existing column that was not a choice list, so there was nowhere to say
+  which columns a link should show — the one thing about an existing relation a
+  person most wants to change. The target stays locked there, because the panel
+  sends no `relation_target` in a patch and a picker that changed it would be a
+  control that silently does nothing.
+* **`looksLikeId` and `WITHHELD_RECORD_LABEL` are exported at last** — they were
+  defined and unreachable, so a host could not agree with the package about what
+  a name is.
+
+**Consumer action:** a surface that lets a person choose a column's target table
+mounts `ReferenceBuilder` instead of building its own dropdown.
+
 ## 0.61.0
 
 **A link to a board opens a board, and a cell that is still resolving says what