@ai-matrx/records 0.80.8 → 0.81.1

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog — @ai-matrx/records
 
+## 0.81.1
+### lane SORT-REACTS
+
+- A live page no longer patches a changed row in place when the change decides its place: `useRecordPage` / `useRecords` read the page again when a realtime notice or this page's own write changed a value the page is sorted by (the group key included), or any value on a filtered or searched page. A date edited to the top now moves to the top, and a row edited out of the filter leaves the page, without a reload. An edit that places nothing still patches in place and reads no page (`react/pageOrder.ts`).
+
+**Consumer action:** none.
+
+## 0.81.0
+### SSR-ROWS: a page's first answers, asked on the server, drawn in the server's HTML
+
+- NEW `/core`: `recordingDataSource(source)` — ask through it as the person, then `.seed()` is a `RecordsSeed` (`{ at, answers: [{ door, args, data }] }`): every door answer that came back, a bundle's (`table_page_bundle`, `record_page_bundle`) parts spread into answers of their own doors. Errors and refusing parts are never seeded. Also `seededDataSource`, `seedIndex`, `seedKey`; `canonicalArgs` is exported from the client.
+- NEW `/react`: `<RecordsSeedProvider seed>` — under it every records hook runs its own door call against the seed in the FIRST pass (on the server, and while hydrating in the browser), suspending on that microtask-only run, so the answer is in the server's HTML and the browser hydrates onto the same answer and asks nothing. A hook whose call asks one door the seed does not hold is not seeded (loading in both passes, asked after hydration as before). The seed answers only until the provider's first commit; a seed older than `SEED_FRESH_MS` is drawn and re-asked. In the browser the seed's bundles are also primed (`primeTablePageBundle`), so effects after hydration open the table from them.
+- NEW `/react`: `useSeededAnswer(key, run)` — the same, for a screen that holds a read in its own state: start from it, skip the first effect read.
+
+**Consumer action:** none (additive). A server-rendering host: ask a seed as the person and mount `<RecordsSeedProvider>` above the screen.
+
+## 0.80.9
+### `@ai-matrx/records/templates` — the 20% governance quota is a gallery card's bar, not a one-off's
+
+- `validateTemplate(spec, { profile: "describe" })` (and so `describeCheck`) no longer refuses a spec because fewer than 20% of its own fields are public, confidential or restricted. That quota teaches governance on a published gallery card and stays in the gallery bar; a person's one-off setup owes only the floor, which the describe autofix already raises (`sensitivityFloorOf`). The owner's /make "creator post tracker" answer (2026-10-08) was refused at "Only 2 of 27 fields say anything but internal"; it now passes the describe check with zero problems (`describe/governance-quota.test.ts`, real answer). "Every field says internal" is unchanged.
+
+**Consumer action:** none.
+
 ## 0.80.8
 
 Automatic changed-only republish (docs/metadata drift since the last tag — see