@ai-matrx/records-ui 0.84.0 → 0.84.7

package/CHANGELOG.md

@@ -1,5 +1,160 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.84.7 (unpublished — needs @ai-matrx/records 0.57.3)
+
+* **The suite is green again (386/386), and the class is gone rather than patched.** 0.84.5's
+  publish gate went red in 15 files because records 0.57.2 made every table list ask
+  `custom.table_facts`. Only `TablesHome` sorts tables into sections, so only it asks now
+  (`client.tableFacts()` + `withTableFacts`); no test double had to learn the door. It says
+  `SECTIONS_UNKNOWN` only when the store has the door and it failed.
+
+## 0.84.6 (unpublished)
+
+**A choice column that takes other values lets a person type one.** (lane STORE-RULE-GAPS.)
+The production walk found the "A value that is not one of the choices is added to them" tick
+saved, while the grid cell and the record form drew a closed drop-down — nothing could send an
+off-list word. Now, on a column with `config.allow_other`, `FieldControl` (the one editor the
+grid cell, the record form and the form runner draw) is the relation picker's shape: a search
+over the choices and **Add “<typed>”** at the foot, which sends the word as typed (the store adds
+it to the column's choices and stores its key). A word that already names a choice picks that
+choice. Several-choices columns keep what was picked. Columns that do not take other values are
+unchanged. The field editor's tick is gated on the same code path
+(`CHOICE_EDITOR_ADDS_WHAT_IS_TYPED`). Paste keeps its own "add these options" step.
+
+**One "pick or add" builder.** `PickOrAdd` (search box, list, Add/Create “<typed>” foot) is the
+ONE layout both `RelationPicker` and the open choice editor are built from — same look, one place.
+The choice editor orders choices by the store's own `metadata.option_position` (`inTheStoresOrder`),
+so a choice added by typing is last, where the store put it, not wherever the lookup returned it.
+
+Consumer action: none.
+
+## 0.84.5 (unpublished — needs @ai-matrx/records 0.57.2 published first)
+
+**Mine is what you made, and an archived table's own address says it is archived.** (lane
+HUB-FIX, guide re-walk 2026-09-23 + chair ruling.)
+
+* `TablesHome`'s Mine section is the tables the person signed in MADE (`created_by`, folded in
+  by records 0.57.2's `tableList` from `custom.table_facts`), whatever their visibility — a new
+  internal table is under Mine AND My organization. When the store HAS `custom.table_facts`
+  and it does not answer, the page says so (`SECTIONS_UNKNOWN`) instead of filing everything
+  under My organization with Mine empty; when the store's catalogue does not carry the door at
+  all, nothing is asked and nothing is said (the door-presence pattern). `TablePage`'s archived
+  screen reads only the archive door every table already uses — it does not depend on
+  `table_facts`. `LANE_EMPTY.mine` says what is true under the new meaning.
+* `TablePage` asks the archive (`client.tableArchived`) before saying a table is not here. An
+  archived table reads "This table is archived", who archived it and when, and **Bring it
+  back**; `TABLE_NOT_REACHABLE` no longer says "…or it may have been deleted".
+* New exports `SECTIONS_UNKNOWN`, `TABLE_IS_ARCHIVED`. Full suite 379/379.
+
+**Consumer action:** none beyond installing it with records 0.57.2.
+
+## 0.84.4 (unpublished — needs @ai-matrx/records 0.57.1 published first)
+
+**The guide re-walk's small wrong things, each fixed as a class.** (lane RECORDS-UI-FIX,
+2026-09-23.)
+
+* **Two records with one name are told apart in the linked-record picker.** Rincon's
+  Customers really holds two Patricia Marshes; the picker drew only the name, so the list
+  read as duplicates. New `tellApart(rows, nameOf)`: a colliding name carries the first of
+  its own columns that differs (an address), and search reads it too.
+* **Charts no longer print their timing ("34.5 ms").** The number stays on the block as
+  `data-store-ms` for whoever measures dashboards.
+* **The Bookings suggestion is English** ("a 30-minute appointment … put each one in Jobs",
+  never "a 30-minute appointments slot"). `bookingSuggestion` is exported.
+* **Table Settings' Proposed box names no door by its code** and shows no baseless "0"; it
+  says proposals wait in the table's Inbox.
+* **A record's history follows the writes on its page.** `HistoryPanel` re-reads on
+  `useRecordChangeRevision` (records 0.57.1). This was not the no-op-version class: the
+  store had the row, the panel never asked again.
+* A refused value no longer lights the app's error pill — see records 0.57.1.
+* Tests (red on 0.84.3): `two-customers-with-one-name-are-told-apart`,
+  `the-history-count-follows-the-writes`, `guide-rewalk-words`, and the reversed ms clause in
+  `demo/dashboard-canvas.test.tsx` (it had enshrined printing the timing).
+
+**Also, in matrx-frontend (`features/sharing`):** the Share dialog's Access tab no longer
+reads "Internal — readable inside the owning organization" over "Private — only you".
+
+## 0.84.3 (unpublished — rides on top of 0.84.2)
+
+**After an import writes, the wizard is a report — never the same import again — and every
+line it names is the line in the person's file.** (lane RECORDS-UI-FIX, VERIFIER-16 H1 + M8,
+VERIFIER-15 M5.)
+
+* **No second write of the same file.** A run that landed rows used to leave the pre-write
+  notice ("…Nothing has been written yet", now false) and a live "Import N rows" beside the
+  result. Once a file has been offered to the store — finished, stopped part-way, or turned
+  away as already imported — every pre-write step (what each record is called, the mapping,
+  the options, the rule notice, the Import button) is replaced by one sentence saying the
+  file was sent, and the report of what landed and what was refused stays. Another run
+  means choosing a file again.
+* **Line numbers are the file's.** The store and the rule check number rows from 1 under the
+  header; the file has its header on line 1. New export `lineInYourFile(dataRow)` is used on
+  the column's refusal, the run's refused rows and past runs' refused rows — the `-3` on
+  line 3 is called line 3.
+* **Nothing sits past the rail.** The mapping is one block per column (name, where it goes,
+  what it is, what would be refused, first values) instead of a 52rem row in a 26rem rail.
+* **No machine word.** A column the table already has is named from its Field
+  (`fieldTypeLabel`), so a number reads "Number", never "range"; an unknown token is written
+  out, never shown raw.
+* **Whole sentences.** `refusalLineForAPerson` ends the store's sentence before the remedy
+  ("…at least 0. Send this column…"). The report's "The 1 row that was refused is kept".
+* Tests: new `src/the-import-after-a-write-is-a-report.test.tsx` (4, red on 0.84.1 bytes);
+  `import-asks-the-rules-first` now expects line 4 for the fourth line (it had enshrined the
+  off-by-one); `import-wizard` expects "is kept"; the F9 source guard now forbids a row wider
+  than the rail and keeps the 14rem "Goes to" floor.
+
+**Consumer action:** none.
+
+## 0.84.2 (unpublished — rides on top of 0.84.1)
+
+**A booking link opens that booking page, and the table list's empty sections stop
+describing a product that does not exist.** (lane HUB-FIX, VERIFIER-16 M4 + M6.)
+
+* `BookingSlots` gains `activeBookingId`: the page a link named is marked (`data-linked`) and
+  scrolled to; a page the rail does not list says `BOOKING_NOT_HERE_LINE`, never a different
+  page. `TablePage` hands it `?item=` when `?rail=bookings`.
+* `LANE_EMPTY.mine` said "New table makes one that only you can see" and
+  `LANE_EMPTY.organization` said "a table you make is yours until you change its visibility
+  to internal" — New table makes an internal table, and no screen here changes visibility.
+  Both now say what is true.
+* New export `BOOKING_NOT_HERE_LINE`. Tests: `rail-deep-link.test.tsx` +1,
+  `visibility-lanes.test.tsx` +1.
+
+**Consumer action (matrx-frontend):** the hub's Bookings row links
+`/data-v2/<table>?rail=bookings&item=<form_id>` (it already can; the item is marked from
+this version).
+
+## 0.84.1 (unpublished — lands with the 2026-09-24 window)
+
+**A blank the store can explain is never drawn as a dash.** (lane OLD-TABLES-4, VERIFIER-16.)
+`renderValue` — the one value renderer for the grid, the peek and the forms — now says two
+things a dash used to hide:
+
+* **A relation whose record no longer exists** reads *"The record this pointed at no longer
+  exists"* (the id it held is in the tooltip). The move of an older table lands such a cell
+  empty and keeps the id on the record's provenance entry, `_sources.<ptr>.unresolved.<key>`;
+  `unresolvedFor(document, key)` is exported for any other reader of that fact.
+* **A worked-out column with no formula in it yet** reads *"Worked out once its formula is in
+  place"* instead of an answer of nothing.
+
+Consumer action: none.
+
+**The field editor sets the three column settings the older grid carried.** (lane
+STORE-RULE-GAPS.) Existing controls only, no new primitive:
+
+* **A pattern's example** — a box beside a "Looks like" check (`rule.example`). A refused value
+  is told "Enter it like 949-555-0142.": `refusalForAPerson` reads the example from the store's
+  `detail.example` as data, so an example shaped like an identifier ("SKU-12") is never dropped
+  by the machine-identity filter.
+* **A length's shortest** — the "Number of characters" check (was "No longer than") has a
+  *fewest* box beside its *most* (`rule.min`).
+* **A choice list that takes other values** — one tick, "A value that is not one of the choices
+  is added to them" (`allow_other`), on select / multi-select columns only; unticking sends false.
+
+Consumer action: none. Needs `@ai-matrx/records` with `FieldRule.example` / `.min` and
+`allow_other` (aidream `290411764c`) and, for the store to honour them, matrx-frontend
+`storerulegaps_an_example_a_shortest_length_and_other_choices.sql` on the database.
+
 ## 0.84.0
 
 **A refusal is said once, with the doors that fit it, and a change a person made is kept or