@ai-matrx/records-ui 0.84.7 → 0.85.4

package/CHANGELOG.md

@@ -1,6 +1,363 @@
 # Changelog — @ai-matrx/records-ui
 
-## 0.84.7 (unpublished — needs @ai-matrx/records 0.57.3)
+## Unreleased — 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),
+  and on the right ONE cluster: the layout chooser (only when nothing is designated; in the menu on a
+  phone), the view's filter (absent over a host layout, which reads its own records), New record on a
+  board, whatever the menu opened (pressed; pressing it closes it), Share, and the table menu. The menu
+  holds everything that was fourteen buttons in a row: Add field, Dashboards, Archived, Forms, Bookings,
+  Checklists, Notifications, Portals, Inbox, Import, Export (now a rail), Settings, the other layouts
+  when one is designated, and the saved views. Owner, 2026-09-24: "not confusing with 1,000 options…
+  just shows them the way it should in the default view."
+* **Designation** (`designatedLayoutOf`, `tableOpening`, `SavedView.designatedLayout`): the default view
+  names a layout the host draws (`layout: "sheet"`), or is the older table's own default view the mover
+  carried in (`moved_from.kind = "default_view"`), which reads as the Sheet and as the table's default
+  (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.
+* `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)
+
+* **`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";
+  a refusal shows the store's sentence and says nothing moved. Needs the unreleased `@ai-matrx/records`
+  `tableHome` / `tableMove`.
+* **`TablesHome`**: what the app keeps for itself sits behind one **Show everything** control that says how many
+  there are, each kept table carries the store's `keeper_says`, and every row carries a quiet organization chip
+  (new optional `organizationName` prop; absent, the list asks the store once).
+* **Consumer action:** matrx-frontend passes `organizationName` to `TablesHome` in `OrganizationHub.tsx` and swaps
+  its three `WhereItLives` call sites to this export.
+
+## 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
+and vitest exited red on unhandled rejections again, this time from `TableSettings.hooks.test.tsx`,
+whose double never answered `row_actions` (GRID-TAILS' section) or `table_decorations` (the one
+colour resolver). It now answers both with what the live store says for a table without actions or
+colours. The gate was proven with zero unhandled errors on an origin/main export before this tag.
+
+**Needs `@ai-matrx/design-system` 0.39.0** (S4's `toggleSelection`). 0.85.2's tag (run 35969941639)
+passed every test and failed the packed-consumer canary because the board imports
+`toggleSelection`, which design-system 0.38.1 does not export; 0.39.0 was published first this time.
+
+**0.85.1 was tagged and never reached npm either** (run 35967872646): every test passed, and vitest
+still exited red on 15 unhandled rejections. The grid and the board began asking
+`custom.table_decorations`, `custom.grid_layout` and `custom.row_actions`, which the deterministic
+gate's recordings never held, and S4's `many-at-once` double never modelled `table_decorations`. The
+recordings now carry the live store's answers for those three doors (read as test@test.com), and the
+double answers an undecorated table (`7b4d49b3ad`). Nothing in the shipped code changed.
+
+**0.85.0 was tagged and never reached npm** (run 35966710984): the publish gate lost a race in
+`a-table-can-start-from-a-real-example.test.tsx`, which counted the example cards after 20
+zero-delay ticks while they still loaded; it now waits for the cards (`5da1344ffc`). 0.85.1 also
+carries DEFAULT-GRID-PARITY's export fix (`3443eb823e`, an export writes a relation's words).
+
+**Needs `@ai-matrx/records` 0.58.0** (published first). One publish carries everything since 0.84.8:
+source versions 0.84.9 and 0.84.10 were never published on their own and are folded below, and
+"0.84.11" in UI-QUICK-1's correction line is this release. Also in it without a section of their
+own: S0 ONE-SAVED-VIEW (the view bar reads and writes `platform.saved_view`, `5367edd12e`) and
+S2-PRIME FILTER-GROUPS (nested conditions in the one condition builder and a view's own
+`definition.where`, `0efe199849` / `1ef813282e` / `54a23e5608`; S1-PRIME's `c58088eecc` stops a
+table's saved views being re-read many times a second). Some of these bytes reached main through the
+integrator's sweeps (`79b505cfa5`, `9a6618f2d0`, `452e363c2e`) rather than their lanes' own commits.
+
+### Lane GRID-TAILS (2026-09-24)
+
+* **An owner writes the table's own buttons (TABLE-PARITY M4).** Table settings gains a "Row actions"
+  section (`RowActionsEditor.tsx`, `RowActionsSection`): list the table's actions in its order with a
+  plain sentence each, add one ("Changes the record" with its column changes — set to, clear, work out
+  from a formula — or "Asks an agent" with the words to ask), edit, move up and down, and retire (the
+  consequence is named first; "Put it back" restores it at the same place with the same id). Start
+  from a record turns a real record's values into the changes; the before-and-after preview shows the
+  chosen record column by column, and a worked-out column says it is worked out when the action runs.
+  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.
+* **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.
+
+### Lane S1-PRIME VIEW-KEYS (2026-09-24)
+
+* **Every per-view setting is a declared key of the one saved view.** `viewKeys.ts`: `VIEW_KEYS` mirrors
+  the store's registry `custom.view_keys()` (path, shape, the layouts that read it, who writes it);
+  `viewSettings(definition)` is THE reader `viewFromRow` goes through; `viewSettingsFor(view, layout)`
+  hands a layout only the keys it reads; `viewSettingsPatch` is the writer's shape `saveViewPatch` sends.
+* `SavedViewSpec` gains `swimlaneField` (board swimlanes) and `collapsedColumns` (board columns kept shut);
+  `GridGrouping` gains `then` (up to two sub-group levels) and keeps it when the look is written back whole
+  — a colour change no longer erases sub-groups.
+* **A page open never writes.** `ViewBar`'s default seed is a read, then a declare only on absence: a table
+  with a default view of any name (a renamed "All records") is opened without a write, and the loader no
+  longer re-runs on every parent render (a host passing `seed={[…]}` inline re-read the views in a loop).
+  Exported `seedIsSatisfied`.
+
+### Lane S4 BATCH-DOORS (2026-09-24)
+
+* **The board takes many cards at once.** `PipelineBoard`: cmd/ctrl-click takes one card, shift-click
+  takes the run (the data table's own `toggleSelection` rule, now in `@ai-matrx/design-system`), `x`
+  takes the focused card, shift+arrow extends, Esc clears. A bulk bar says "N cards selected" with
+  "Move N to…" and one menu item per stage ("Move 6 to Scheduled"); it sends each card's loaded version
+  in ONE call and paints each refused card with its own sentence (needs a column, changed since loaded,
+  no right). A Viewer can select nothing, so a Viewer never sees the bar.
+* **The inbox decides many at once.** `ActionInbox`: a checkbox per actionable item, shift-click for a
+  run, "Approve N" / "Decline N" in the same bar; `x` selects, `a`/`d` act on the selection. One call,
+  one sentence back ("6 approved."), and each item that was not decided says why.
+* Headless two-seat walk on the dev clone: `demo/batch-doors-walk.mjs` (serve with
+  `demo/vite.walk.config.ts` so a peer's save does not reload the page mid-walk).
+
+### Lane S6 PORTAL-BRANDING (2026-09-24)
+
+**A portal carries the business's own look and its forms** (UI-CHAMPIONS rows 45, 46, 55; champions
+Softr's branded portal and the Stripe customer portal).
+
+* **`PortalLookEditor`** (new export), shown inside every portal card in `PortalsPanel`: the name
+  clients see (empty = the organization's), a welcome line, a logo chosen from the organization's
+  own PUBLIC pictures (`card.logo_candidates`), a colour from the design system's seven names (the
+  same swatches the table highlights use), footer links (`https://`, `mailto:`, `tel:`), and every
+  form on the tables the portal shows — tick to offer it, optional button words, Up/Down order. Saved
+  through `portalDeclare({ …, config })`, re-stating the portal exactly as the card read it; the
+  store's refusal is drawn by `RefusalNotice`.
+* **`PortalCardViewProps.look`** — the slot the editor renders in (absent = none offered).
+
+**Consumer action:** needs `@ai-matrx/records` with `PortalCard.config/style/forms/accents/logo_candidates`
+and `portalDeclare({ config })` (aidream `4bf803c452`), and the S6 store doors on the database.
+
+### Lane SC-R (2026-09-24; landed by DEFAULT-GRID-PARITY)
+
+* `EntityReferenceControl` (chips of what an entity-reference value names, withheld words said,
+  take-off, no add control until the store has a search door), `EntityReferenceKindPicker`,
+  `entityReferenceSpec`, `whatIsMissingForEntityReference`; an entity-reference cell reads as its
+  words instead of `[object Object]`.
+* The field panel asks an entity-reference column which kinds it points at, sends
+  `allowed_types`, and shows an existing column's kinds locked. The menu entry "Points at
+  something else on the platform" is drawn only once `custom.field_kinds()` publishes
+  `entity_reference` (after the chair's apply and `pnpm records:generate`).
+
+### Lane DEFAULT-GRID-PARITY (2026-09-24)
+
+**The default grid shows what the store holds** (TABLE-PARITY, "in the store but not shown by the
+default grid"). Each item is read through the store's own door and drawn through the data table's
+own seams (`rowActions`, `selection`, `defaultSort`, `footerRows`, `rowHeight`, `copy`), with no
+second table. A control the store cannot serve for a table is absent, never dead.
+
+* **Row actions (M1–M3).** A table's own actions (`custom.row_actions`) are one-click buttons on
+  every row, and on the selection bar for the ticked rows. One press is ONE `custom.action_run`,
+  and it asks first when the action says to. A refusal names the record and the column. Undo writes
+  back what each row held. An `agent` action hands the row and its prompt to the new optional host
+  port `runAgentAction`, and is absent when the host does not bind it. Readers get no buttons.
+* **The table's default sort (S2).** `data.default_sort` (`[{field, direction}]`; older spellings
+  also read) is where the grid opens.
+* **Summary bar (F1).** Under each column, a summary the view keeps (`presentation.summaries`),
+  worked out by `custom.record_aggregate` over the whole table. It offers only the measures
+  `custom.agg_operations` lists that mean something for that column.
+* **Layout knob (D1 D5 D6).** Row height, freeze first column, wrap and fit/scroll are read from the
+  organization's `custom/grid_layout`, and the view's own choice wins (`presentation.wrap`, `fit`,
+  `freezeFirst`). A Layout menu says where each choice came from.
+* **Formula columns (K1 K2).** A worked-out column's header carries an `fx` mark with what it is
+  worked out from. The field panel writes a formula in the language a person types
+  (`formula_text`, checked live by `custom.formula_parse`) and can re-aim an existing one.
+* **System columns (H2 H3).** The field menu offers Record number, Created time and Last changed
+  time (the store's `autonumber` / `created_time` / `modified_time` words). A new record-number
+  column numbers the records already there through `custom.autonumber_backfill`, and says so if it
+  was refused.
+* **Duplicate a row (A7)**: the typed values only, never the worked-out ones.
+* **A reference for a prompt (R3)**, beside Copy: named by the row label, carrying the table and
+  row ids.
+* **Webhooks in the Notifications rail (N3)**: list, delivery health, start one (the signing
+  secret is shown once), archive. A reader gets no controls.
+* **Start from an example (P2)** on the tables home: builds a registered real use case through
+  `custom.table_from_example`.
+* **A row opens its record (VERIFIER-17).** An editable grid's cells are each their own control, so
+  a row click never fired and nothing opened the record. The first cell of every row now carries an
+  Open control, named for the record and always reachable by keyboard and touch. Space on any
+  focused cell opens that row's record, and Enter still edits. Absent when the host cannot open a
+  record (`onOpenRecord`). Kanban, calendar and gallery cards already opened on click.
+* **An export writes what the grid shows (GRID-PORT finding).** CSV and XLSX used to write a
+  relation's stored record id. They now write the words the grid draws for it: the same resolver
+  (`useRecordLabels`), and `relation_words_many` for any id no cell on screen has drawn yet. An id
+  nobody can resolve stays the id rather than a blank. Choice cells carry their labels, and a
+  worked-out column carries the store's value.
+* **No machine "…ss" plurals (VERIFIER-16/17 M3).** `realPlural` and `pluralNoun` (`names.ts`): a
+  `label_plural` that is only the name with an "s" appended ("Customerss", "Status optionss") is
+  never shown, and a sentence's noun never doubles a final "s". The stored values come from the
+  store's `name || 's'` fallback. That root is the store's to fix.
+
+### Lane S3 (2026-09-24)
+
+**Period comparison, date grain and targets on the dashboard canvas** (UI-CHAMPIONS-PLAN rows 17,
+18, 20). Needs `@ai-matrx/records` with `recordAggregate({compare})` / `dashboardRun({compare,
+grain})` and the store's `uichamp_s3_*` files; on a store without them nothing new is drawn.
+
+* **A number tile shows the trend and the target.** A block the store compared (`block.compare`)
+  shows its total with an arrow and signed percent against the prior window ("16,930 ▼ -7.9% —
+  September 2026 · 18,380 in August 2026"), and a block with a `target` draws a progress ring
+  ("Monthly target 25,000 · 68%"). The arrow is coloured only when the block declares a target (the
+  one declared fact that says up is good); otherwise it is the neutral tone.
+* **A compared chart draws the prior period behind the current one** in the palette's new
+  comparison tone (`COMPARISON_COLOR`, `--muted-foreground`), with a legend naming both windows and a
+  dashed goal line (`GOAL_COLOR`) at the target's pace per bucket. A quiet week inside the window is
+  dated ("Week of Sep 27"); only a position past the window's last bucket is named by its place.
+* **A date-grain picker on the canvas** ("By the saved grain" / day / week / month / quarter / year),
+  shown only when a block runs along a date; it re-cuts every bucketed block through
+  `dashboard_run(p_grain)`, in the organization's own time zone and week start.
+* **Buckets are named in the organization's calendar** (`bucketName`, `windowName`,
+  `positionBucket`), read from the store's local ISO moment and never from the browser's clock.
+* **Drill-through on a bucket opens that period of its date Field** (`bucketWindow`) — it used to ask
+  for a Field called `completed_on_week`, which matched nothing — and a compared block opens its
+  current window only.
+* Harness: `RECORDS_UI_DEMO_TABLE` opens every page on an existing Table and writes nothing of its
+  own into that organization; `demo/walk-s3-periods.mjs` walks the canvas headless from two seats.
+
+**Added at publish (S3's lines, owed because the file held another lane's uncommitted edits):**
+
+* **The owner's canvas is the owner's from its first frame.** `DashboardCanvas` shows its skeleton
+  until the rights answer (`custom.my_levels`) is in, instead of drawing the blocks first with no
+  controls.
+* **Per-block compare and target editor** in each block's settings row (the same `Select` /
+  `BasicInput` as the grouping picker): no comparison / the period before / the same period last
+  year, the period, and no target / a target number / a goal column (number, money and percent
+  columns only). Absent on a list that does not move and, for compare, on a table with no date column.
+* **A target read from a goal column** (`target {field, op: sum|avg|min|max}`): a reader who may not
+  read that column sees the store's sentence in place of the target and the block still draws its number.
+
+### Also in this release
+
+**Lane S7-PRIME — a stranger starts from a link that already knows something, stops, comes back
+on another device, and leaves by the owner's door (UI-CHAMPIONS-PLAN rows 34, 35, 40).**
+
+* **Prefill.** `FormRunner` takes `initialAnswers`: the form starts with those answers in their
+  questions, changeable, and hands them to `whichAsked` like typed answers, so a question that
+  depends on a prefilled one branches exactly as if the person had typed it.
+* **Keep my place.** `FormRunner` takes `onAnswersChange` — every change to the answers after the
+  first paint, for the host to keep (the public page saves it through `custom.form_draft_save`).
+  A form resumed part-way opens on the first question still waiting for an answer.
+* **The thank-you screen leaves by the owner's door.** `FormSpec.thankYou` is now `FormThankYou`
+  (`title`, `body`, `redirectUrl`, each optional); the runner shows the message, then goes on to
+  `redirectUrl` a moment later with a "Go now" link beside it (a preview never leaves and says
+  where the live form would go). The store judges the address — a secure page on the
+  organization's own sites — so the runner never does. `formPresentation` / `formFromSummary`
+  carry it as `presentation.thank_you.redirect_url` through `thankYouDocument` /
+  `thankYouFromDocument`; an empty thank-you is `null`.
+* **`FormBuilder`** gains an "After somebody sends it" section beside the notify editor: title,
+  message and "Then go to (optional)". A foreign address is refused on Save in the store's words,
+  naming the sites it may use.
+
+**Consumer action:** matrx-frontend's `PublicFormRunner` hands `whichAsked`, `initialAnswers` and
+`onAnswersChange` through a spread and casts the spec so it compiles on 0.84.8; on adopting this
+version, import `FormAsked`, pass the three ports by name and drop the cast.
+
+**Added at publish (S7-PRIME's lines, owed for `ec860af7ac` and `cd33e86359`):**
+
+* `resumed`: only a saved place being resumed opens on its first unanswered question; a link that
+  only prefills opens on question one with the prefilled answer in place.
+* FormBuilder: a write the store refuses (Save, publish, notify choice, New form) shows the store's
+  words above the builder with Keep editing / Discard; only a failed load replaces the screen.
+
+### Lane UI-QUICK-1 (TABLE-PARITY review)
+
+**The class 0.84.9 left open.**
+
+* **A table colored at the TABLE level now paints everywhere, not just wherever a view redecorated
+  it.** 0.84.9 wired `Card` and `Grid` to a view's own `presentation.style`; it never read G1's
+  table-level decorations (`custom.table_decorations` / `client.tableDecorations`) at all, so a
+  table whose colors are a `color_by` and a set of rules stored on the TABLE — never on any one
+  view — drew nothing on the default grid, the kanban, the calendar or the gallery alike (Arman's
+  Coding Accounts table: colored by Account Type, with a MAXED/NEAR rule, no view has ever set its
+  own look). New `styleFromDecorations` (`presentation.ts`) translates G1's Field-id-addressed
+  decorations into the Field-key-addressed `TableStyle` every reader already understands; new
+  `resolveTableStyle` is the ONE presentation resolver — it layers the view's own style over the
+  table's decorations piece by piece (a view that set only a manual highlight still inherits the
+  table's `colorBy`/`rules`; a view that set its own `colorBy` AND `rules` is not haunted by the
+  table's). `Grid` and `ViewSwitcher`'s `Board` (feeding `Kanban`/`Calendar`/`Gallery`/`Card`) both
+  fetch the table's decorations once (new `useTableDecorations` hook,
+  `tableDecorations.ts`) and both call the same resolver — no second color logic anywhere in this
+  package. A table with no decorations and no view style resolves to nothing, exactly as before.
+* Corrects the 0.84.9 changelog entry above, which overclaimed "the table's own colors" when it
+  had only wired the view's.
+
+### Folded from source version 0.84.10
+
+**Lane FORMS-FIX-1 — two screens that lied about forms (UI-BENCH-FORMS gap 1 and its cheapest correctness win).**
+
+* **A public form branches the way its owner set it.** `FormRunner`'s public arm had no evaluator,
+  so every "ask this only when …" question was shown to every stranger. It now takes a
+  `whichAsked` port — the host's server asks the STORE (`custom.form_public_asks`, the same Rule
+  through the same `custom.rule_eval`) with the answers so far — and hides exactly what the store
+  says to hide, a quarter-second after typing stops. Undecided shows; a condition the store could
+  not work out shows WITH the store's sentence. A public mount with no port still says out loud
+  that it cannot branch. New exported type `FormAsked`.
+* **"Tell me when somebody answers" is on the form builder.** `notifyRuleId` round-tripped and
+  `custom.form_notify` delivered through it, but nothing on the builder could set it. `FormBuilder`
+  now mounts `NotifyRuleEditor` beside the link, in a new CHOOSE MODE (`chosenRuleId` /
+  `onChoose`): pick a subscription or make one and the form is re-declared with it at once — the
+  whole form, so its accept Rule rides back. A table with no saved view offers "Watch every
+  record" through the store's own `custom.view_declare`.
+* `NotifyRuleEditor` reads saved views from the store's own `custom.views` door when the host binds
+  no `savedViews` port, instead of printing a dead end.
+* **The owner's preview branches too.** The signed-in arm of `FormRunner` (the builder's live
+  preview) used to call `custom.rule_eval` from the browser — an internal evaluator no client may
+  call — so it printed "You do not have access to this" and never hid a question. It now builds its
+  `whichAsked` port from `client.formPreviewAsks` (`custom.form_preview_asks`: the same store loop
+  as the public door, behind the organization wall and the person's own rung on the Table), over
+  the DRAFT's own questions. The `evaluate` path is gone: one port, one store loop, both arms.
+  `FormAsked`'s refusal may carry the store's own `error`. **Needs `@ai-matrx/records` with
+  `formPreviewAsks`** (FORMS-FIX-1); until the door is regenerated into `STORE_DOORS` the preview
+  shows every question with the store's `door_absent` sentence.
+
+**Consumer action:** matrx-frontend's `PublicFormRunner` already hands `whichAsked` through a spread
+so it compiled on 0.84.8; on adopting this version, import `FormAsked` and pass `whichAsked` by
+name.
+
+### Folded from source version 0.84.9
+
+**Lane UI-QUICK-1 — two gaps from the CALENDAR-GALLERY bench, both cheap wins by design.**
+
+* **Every kanban, calendar and gallery card now paints its VIEW's own colors.** `Grid` has
+  colored rows (`presentation.style`'s `color_by`, ordered rules, hand highlights) since this
+  package's own view-presentation work; the shared `Card` component that draws all three other
+  layouts never called the resolver. `Card` now takes an optional `style: TableStyle` and resolves
+  it through `resolveRowColor` + `ROW_TINT_CLASS` — the SAME primitive and the SAME class map the
+  grid uses, not a second color scheme. `ViewSwitcher` threads `view.presentation?.style` down to
+  `Kanban`, `Calendar` and `Gallery`. A table nobody has ever colored, or a `Card` given no `style`
+  at all, looks exactly as it did before this version. **Correction (see Unreleased, lane UI-QUICK-1):** this line
+  overclaimed — it wired the VIEW's own look only; a table colored at the TABLE level through G1's
+  `custom.table_decorations`, with no view ever setting its own `presentation.style` (Arman's
+  Coding Accounts table is exactly this shape), still drew nothing here. The Unreleased entry above closes that.
+* **Gallery gets lazy images, a real placeholder, a card-size control and configurable fields.**
+  Cover images now carry `loading="lazy"` inside a fixed-height placeholder (`GALLERY_SIZE`), so a
+  gallery of hundreds only fetches what scrolls into view and mixed image/no-image records no
+  longer jump the grid. A small/medium/large size control is saved on the view as
+  `presentation.gallerySize`, the same pattern as the grid's own `rowHeight`. Fields shown are no
+  longer hardcoded to the first four — they read `presentation.hiddenFields`, the SAME hidden-
+  column set the grid's own column picker holds, so hiding a column anywhere hides it everywhere.
+* `GridPresentation` gains `hiddenFields?: string[]` and `gallerySize?: "small" | "medium" |
+  "large"`, parsed and round-tripped the same tolerant way as every other field in
+  `parseGridPresentation`/`presentationDocument`.
+
+## 0.84.8
+
+(lane GRID-PORT `5cb9bcbd99`; published by PUBLISH-SWEEP-4.)
+
+**A host can draw a layout beside the package's own four, on the one table page.**
+`RecordsUiHost.layouts?: HostLayout[]` — `{ id, label, render({ tableId, filter }) }`. Each
+appears as a button in `ViewSwitcher`'s layout row after Grid / Kanban / Calendar / Gallery, and
+`?view=<id>` opens it (`openingHostLayout`); `TablePage.onViewChanged` is called with the id.
+Page-level, never written onto the view record (the store's layout words stay the four). A host
+id equal to one of `PAGE_VIEWS` (or a spelling of one) is ignored, so `?view=grid` is always the
+package's Grid. Why: the owner's ruling (2026-09-23) — AI Matrx's ported /data grid is the
+"Sheet" layout of `/data-v2/<table>`, not a second page for the same table.
+
+Consumer action: `onViewChanged` now receives `PageView | string`; widen a handler typed
+`(view: PageView) => void`.
+
+## 0.84.7 (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
@@ -1638,9 +1995,6 @@ A table that is not a pipeline draws the plain kanban exactly as before; the
 decision is the Table's own `stage_field`, asked once, never guessed from the shape
 of a Choice column.
 
-
-
-
 ## 0.38.0 — 2026-09-20
 
 **0.37.0's gate went red on the tarball, not on this package.** The packed
@@ -1650,7 +2004,6 @@ call. That is the tarball canary doing exactly its job: green in the monorepo,
 absent for an npm consumer. `@ai-matrx/records` 0.26.0 carries it, and this
 release is the first that can resolve against it.
 
-
 ## 0.37.0 — 2026-09-20
 
 **Three unhandled rejections were failing the release gate while every test
@@ -1662,7 +2015,6 @@ rejection, so vitest reported `12 passed / 79 passed` and exited non-zero, and
 0.36.0 never reached npm. The fixtures are re-recorded against the live store;
 the suite is now 12 files / 79 tests with no errors.
 
-
 ## 0.37.0 — 2026-09-20
 
 **The capture sheet, run on a phone, with or without a signal (PRODUCTS row 15).**
@@ -1712,7 +2064,6 @@ costs somebody a text and never robs the real Monday summary of a week of news.
 
 Needs `@ai-matrx/records` ≥ 0.26.0.
 
-
 ## 0.36.0 — 2026-09-20
 
 **0.35.0 never reached npm: the demo harness asked the store for ten thousand
@@ -1742,7 +2093,6 @@ Also in this release, from 0.34.0/0.35.0 and this lane:
   `FieldHistoryPanel`, so a screen that is green in the monorepo and absent from
   an npm consumer's tarball is caught at the gate.
 
-
 ## 0.35.0
 
 **Per-record AI enrichment: the badge on every agent-owned cell, and the panel behind it.**
@@ -1794,7 +2144,6 @@ question to ask, and `GridCell` takes `editing: GridEditing | null` — a null
 session means no editor, and nothing else. `src/who-changed.test.tsx` covers
 it; its load-bearing clause fails on the old gate.
 
-
 ## 0.32.0
 
 **The import wizard, rebuilt on the store's own import doors (SCR-10 / SCR-N-7).**
@@ -2182,7 +2531,6 @@ through the field panel.
 
 None. `presentation` is optional and its absence is today's behavior.
 
-
 ## 0.19.1
 
 **The progress bar and the count beside it said different things.** One question
@@ -2193,7 +2541,6 @@ form, not by reading it. Typeform's bar advances as you move through the form,
 and now so does this one. On a single page there is no position, so it keeps
 measuring what it can: how much is answered.
 
-
 ## 0.19.0
 
 **The choice picker reads a document from any era, and writes the contract.**
@@ -2210,7 +2557,6 @@ falls through and renders as itself.
 
 **Consumer action:** none beyond taking 0.19.0 with `@ai-matrx/records` 0.13.0.
 
-
 ## 0.18.0
 
 **A person can switch off a notification an agent switched on.** "Make me an
@@ -2231,7 +2577,6 @@ never say a subscription is off while it keeps firing.
 None — `TablePage` grew the rail. Needs `@ai-matrx/records` 0.12.0 or above for
 `client.subscriptions` and `client.subscriptionMute`.
 
-
 ## 0.17.0
 
 **There is one Form object, and it is the one with the link.** `FormBuilder` kept
@@ -2582,7 +2927,6 @@ import { recordStoreShare } from "@/features/sharing/components/RecordStoreShare
 Leave it out and nothing changes — the screens render exactly as they did in
 0.8.0, with no Share button.
 
-
 ## 0.8.0
 
 **The worst finding of the 19 September verdict: "Add field" opened a proper
@@ -2633,7 +2977,6 @@ A table made with the product's own button had exactly one column.
 drawing values outside `RecordsMount` should render `<RecordValue>` (or wrap in
 `RecordLabelProvider`) so ids resolve to names.
 
-
 ## 0.7.0
 
 What the first headless walk of 0.6.0 through a real browser found, in the same