@ai-matrx/records-ui 0.93.67 → 0.93.70

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,32 @@
1
1
  # Changelog — @ai-matrx/records-ui
2
2
 
3
+ ## 0.93.70
4
+
5
+ Automatic changed-only republish (docs/metadata drift since the last tag — see
6
+ `git diff npm/records-ui/v0.93.69..npm/records-ui/v0.93.70 -- apps/shared/records-ui`).
7
+ No source changes intended and no consumer action required.
8
+
9
+ ## 0.93.69
10
+ ### Unreleased
11
+
12
+ - **Save to a table — one screen for every shape** (lane SAVE-AS-TABLE-EVERYWHERE, 2026-09-29): `SaveToTable` saves what a person is looking at — a markdown table, a list or a few bullet points (one column, or split at a shared delimiter), `Key: value` lines (one record, or one per block), a CSV or TSV paste, a kind value or JSON rows — as a new table (each column's type proposed by `guessColumn` and editable; made through `declareTable`; rows through the store's import doors, the rows' sha-256 as the run's identity) or as rows added to a table the person can change (`ImportWizard` with the new `source` prop). The one reader of those shapes is `readTableShapes` / `shapeOfValue` / `shapeOfGrid` / `hasTableShape` (pure, exported). `ImportWizard` also gains the **enum ask**: a word going into a choice column that names none of its choices is listed before the write with "Add to <Column>", obeying the organization's `choice_nudge` (a file import gains it too). Proof: `a-shape-a-person-can-see-becomes-rows.test.tsx`, `save-to-table-makes-a-table-or-adds-rows.test.tsx`. **Consumer action:** open `SaveToTable` from every "save as a table" entry point instead of a host-built dialog.
13
+ - **A booking page that exists opens with its own questions and hours** (lane HANDOVER, 2026-09-29): "Change it" opened the builder with the page's title and clock only, so saving was refused ("A booking page has to ask the person something") and would otherwise have replaced the page's real hours with the opening guess. The builder now starts from the page's own presentation (questions, windows, gap, lead, per-day, days), read through the forms door, and a page kept in UTC opens in the owner's own zone. Proof: `a-booking-page-that-exists-can-be-changed.test.tsx`, red on the old builder.
14
+
15
+ ## 0.93.68
16
+ ### Unreleased
17
+
18
+ - **The merged grid drills through the store** (lane DRILL-TABLE-PRIMITIVE, D3): grouping is the
19
+ server's now — `custom.record_aggregate` over the whole table, so a group's count is never one
20
+ page's count. Dimensions (choice, yes/no, short text, date by day…year) and Measures (count;
21
+ sum, average, lowest, highest, median of every number column) are inferred from the Fields
22
+ (`gridDrill.tsx`); the table's group-by control groups up to three levels and pivots one across
23
+ the top, "Show" picks what to display, a click on a group drills into the next Dimension with its
24
+ value as a filter, and the trail zooms back out. The question lives in the address
25
+ (`?by=&across=&show=&f.<field>=`) and on the view's grouping (`across`, `show`, `trail`, `grain`
26
+ beside `field`/`then`), so Save keeps the exploration as a Saved view; the drill trail also
27
+ narrows the page the grid reads ("See these records"). Proof:
28
+ `a-grid-drills-through-the-store.test.tsx`, red 4/5 on the HEAD grid.
29
+
3
30
  ## 0.93.67
4
31
 
5
32
  Automatic changed-only republish (docs/metadata drift since the last tag — see