@ai-matrx/records-ui 0.43.0 → 0.47.0

package/CHANGELOG.md

@@ -1,5 +1,154 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.47.0
+
+Carries 0.45.0 and 0.46.0, neither of which reached npm: the publish of 0.45.0
+failed on a live clause that had gone stale under a store change (see the last
+item), and 0.46.0 was cut behind it.
+
+**A refusal with two remedies, one of them wrong.**
+
+A plumbing company wants to give ONE customer view access to the jobs table her
+work is on. She has an account; she is not in their organization.
+`custom.share_grant` refuses, and it refuses WELL — measured verbatim on the live
+store: *"That person is not in this organization, so they cannot be given access
+to this table yet."*, with three ways forward in its hint: invite them, share
+with their organization instead, or — if they are a client rather than a
+colleague — put them in a portal.
+
+The screen threw all of that away, in three separate ways, all of them in
+`plainWords.ts` and all of them fixed here:
+
+1. **Two remedies, one wrong.** The formatter printed the door's ways forward AND
+   then its own table's *"Change the value so it passes, then try again"*, which
+   is not a thing anybody can do about a membership. A person follows the last
+   sentence they read. The DOOR's hint is the remedy now whenever it survives the
+   machine-identity filter; the table is the fallback it always should have been.
+2. **One footnote binned the sentence around it.** The hint's human half carried
+   `(VIS-23)`, so the whole clause was judged machine identity and dropped — which
+   is why the plumber got no remedy at all. A bracketed contract id is a
+   footnote: it is lifted out, the sentence is kept, and the id still reaches the
+   engineer.
+3. **The cleaner re-wrote a sentence it had no reason to touch.** It splits on
+   `", so "` — one of the store's own `format()` joins, and also how ordinary
+   English joins two clauses — and rejoins with `". "`. So every person, on every
+   such refusal, read *"That person is not in this organization. they cannot be
+   given access to this table yet."* A cleaner that dropped nothing now changes
+   nothing.
+
+`src/one-remedy.test.tsx` runs all five clauses on that exact measured refusal.
+
+**A live clause that had gone stale, and was blocking every publish.**
+
+`demo/live-smoke.test.tsx` asserted that a table declared with one column NAME has
+no columns — true until lane LIMITS-FIX landed "a table's declared fields exist"
+(2026-09-21, and the root cause behind crew C's fifty-one rows under "this table
+has no columns yet"). The store cannot produce that state any more. The clause
+asserts what it produces instead, which is strictly the stronger of the two, and
+`declareTableWithNoColumns` — a name that had become a lie — is
+`declareTableWithItsFirstColumn`.
+
+**Consumer action:** none.
+
+## 0.45.0
+
+**The record grid vanished when you looked at a dashboard and then opened a panel.**
+
+Ridgeline Physical Therapy keeps ten patients in a table. Its owner pressed
+Dashboards, then Checklists to compare the two panels, and the patients were
+gone — with no New record button and no way back but a reload. Reproduced
+headless on the live app: `aria-pressed` was `"true"` on Dashboards, ABSENT on
+Checklists, no grid in the document.
+
+That row of buttons was TWO state machines wearing one coat. `main` decided the
+middle of the page, `rail` decided the right-hand panel, nothing joined them,
+and the NINE rail buttons carried no pressed state at all — so the only tab that
+ever looked chosen was the one that was not.
+
+`chooseSurface` decides both now and `surfaceChosen` answers, for every button
+in the row, whether it is the chosen one. Opening a panel brings the records
+back (a panel is read BESIDE the records); opening the dashboards over a panel
+leaves the panel alone, because that direction takes nothing away. Pressing the
+chosen button closes it, as it always did. `src/surface-choice.test.tsx`, five
+clauses, all red on 0.44.0.
+
+**The Share button was called something it never said.**
+
+It read "Share" and carried `aria-label="Share this table"` — and an
+`aria-label` REPLACES the visible text as the accessible name. So a screen
+reader, a voice user saying "click Share", a keyboard palette and every
+automation all resolved a sentence the screen never shows. A crew reported it
+twice as an absent button ("Playwright could not find a clickable, visible
+'Share' button even though the same label renders as a normal-looking button"),
+and the clinic's front desk never got read access to the patients table.
+
+The context is the `title` now, which describes and never renames.
+`scripts/check-label-in-name.mjs` is the census — it carries `--self-test`,
+which plants this exact rename and requires the census to go red on it — and it
+found one more of the same: the grid's Delete button, which read "Delete" and
+was named "Delete this record". Wired into `check:package`, so the class cannot
+come back. A glyph (`+`, `×`) is not a label and is not judged: there
+`aria-label` is the only name there is.
+
+**Every cell asked "who?" and never answered.**
+
+A crew reading ten real patients: *"Every single cell shows a small 'who?' hover
+badge next to its value instead of a resolved author name, an agent/rule label,
+or even 'system' — the attribution feature is visibly wired up (it renders on
+every cell) but never resolves to anything readable."* They were right, and the
+reason was that nothing ever asked: the badge opened a panel and looked nothing
+up, while `custom.field_history` on those exact patients had been answering
+*created by admin* since the day they were written.
+
+It asks now, on the hover or the Tab that already makes it visible, for that one
+cell — so a page of two hundred cells nobody points at costs nothing. `who?` is
+what it says while the question is still a question; the moment it has the
+answer, the answer is what it wears, and the hover carries the whole sentence.
+`src/whoChanged.ts` owns those words for every surface that shows an author: an
+agent ALWAYS names the person it acted for, the platform is "the system", a
+person the door did not name is resolved through the app's one
+organization-scoped roster (the `members` port), and a uuid is never printed at
+anybody.
+
+**Opening a table showed an error about a column in a table you will never see.**
+
+The Alvarado-Chen family opened their recipes and met *"That already exists —
+This table already has a field called 'Name'"*, every time. `Name` is the first
+column of the PACKAGE's own bookkeeping table (`records_ui_view`, where a saved
+view is a record), which `ViewBar` levels on every table page: the store's read
+answered without the field, the store's write answered 23505 with it, and that
+refusal was painted over the family's recipes.
+
+Two classes, both closed. A step written to be idempotent no longer calls its own
+desired end state a failure — 23505 from `field_declare` means exactly what
+`addMissingFields` was trying to arrange, and every other refusal still comes
+straight back out. And bookkeeping is never the person's error: a refusal
+levelling the package's own table degrades the saved views with one sentence
+(`SAVED_VIEWS_UNAVAILABLE`) and leaves the table's own screen alone.
+`src/ensure-idempotent.test.tsx`, two clauses, red on 0.44.0.
+
+**Consumer action:** none. No export changed — `chooseSurface`, `surfaceChosen`,
+`WhoChangedSource`, `useWhoChanged` and the `whoChanged` vocabulary are added.
+
+## 0.44.0
+
+**Pressing Open in the inbox landed you on the table with the record still shut.**
+
+`ActionInbox` has always handed its host `onOpenRecord(recordId, tableId)`, and
+the app has always routed that to `/data-v2/<table>?record=<record>` — and
+NOTHING read the parameter. So an approval, an assignment, an agent's proposal
+and (since 0.41.0) a checklist step all offered an Open that did not open
+anything. Measured in the real app on a dental practice's onboarding steps.
+
+`TablePage` takes `activeRecordId` and opens the record rail on it, moving the
+rail when a later link names a different record. Absent, the page opens exactly
+as it did. `openingRail` is the exported seam and `src/record-link.test.tsx`
+fails on 0.43.0's bytes.
+
+**Consumer action:** pass `activeRecordId` from your route's `?record=`
+parameter, beside the `activeDashboardId` you already pass. Without it the Open
+control in the inbox still goes nowhere.
+
 ## 0.43.0
 
 **Five headings carrying the store's real counts, over five empty columns.**