@ai-matrx/records-ui 0.3.1 → 0.4.3

package/CHANGELOG.md

@@ -1,5 +1,94 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.4.3
+
+Resets the harness-owned demo table through the store's real read and delete
+doors before a certification run. Repeated releases can no longer push the
+three canonical Grid rows beyond the first page. The demo port is also
+configurable for isolated local proof while remaining `3005` by default.
+
+### Consumer action
+
+None. The public package API is unchanged.
+
+## 0.4.2
+
+Uses the same bounded live-store wait as `@ai-matrx/records`, so a legitimate
+overlapping rollback-only verification cannot make the demo proof fail after
+twenty seconds.
+
+### Consumer action
+
+None beyond taking `latest`; the public API is unchanged.
+
+## 0.4.1
+
+Restores monotonic versioning after a concurrent release plan overwrote the
+already-staged 0.4.0 version, and shares the serialized record-store release
+lane with `@ai-matrx/records`.
+
+### Consumer action
+
+None beyond taking `latest`; the 0.4.0 API remains intact.
+
+## 0.3.2
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/records-ui/v0.3.1..npm/records-ui/v0.3.2 -- apps/shared/records-ui`).
+No source changes intended and no consumer action required.
+
+## 0.4.0
+
+**`recordsDataSource` honours the schema the CALLER named, and the two page
+assemblies get their first headless proof.**
+
+0.3.1's adapter routes every `rpc` to one fixed schema (`custom` by default).
+That is right for the store's own doors and wrong for the trust doors:
+`@ai-matrx/records`' `trustDoor` says `iam` out loud — the external principal and
+the publish binding live there — and a fixed-schema adapter sends them to
+`custom`, where PostgREST answers PGRST202 naming a schema the caller never
+asked for. The adapter now reads `options.schema` per call and falls back to the
+second argument (still `custom`) only when a call says nothing, which no caller
+in `@ai-matrx/records` does. The port already specified this: "A host binding
+supabase-js routes this to `client.schema(options.schema).rpc(fn, args)`".
+
+`TablesHome` and `TablePage` shipped in 0.3.1 with no assertion of their own.
+Three now run against the live store in `demo/smoke.test.tsx`: the four lanes
+drawn by name with a real table in one of them and `New table` offered; the
+table page's records plus its five admin rails, with the settings rail really
+opening the panel; and the same page giving a plain member the records and NONE
+of the administering controls — absent, not disabled.
+
+**THE WALK, and the three defects walking it found.** `demo/walk.test.tsx` runs
+the whole product against the live store in one file — declare a table with three
+field types, write a record through the generated form, open the table page and
+peek the record, save a view, file an agent's field proposal and accept it,
+export the CSV, then walk the same table as a plain member and be offered nothing
+to administer. Seven cases, green, and the table it makes is soft-deleted after.
+It found:
+
+· **A table nobody had saved a view for showed NO RECORDS.** A view is a record,
+  so a brand-new table has none, and `TablePage` then rendered its own honest
+  "Waiting for this table's views" and nothing else — a dead end on the first
+  table anybody makes. The page now seeds `DEFAULT_VIEW_NAME` ("All records",
+  grid), an ordinary saved-view record a person can rename or delete, never a
+  hidden built-in mode. A host with its own idea passes `seedViews`.
+
+· **`ProposedChange.table` was required for all three acts and unfillable for
+  two.** `update` and `remove` name a record and ignore `table`, so a proposer
+  wanting to change an existing record had to supply the id of the kernel Table
+  that record lives in — a fact the client has no door to ask for. It is optional
+  now, and an `add` without it is refused by name instead of writing nowhere.
+
+· **The demo harness's pages were dead in a browser while `pnpm test` was
+  green.** Two copies of React in one vite graph (the demo's own dependency tree
+  plus the workspace's, through design-system and alchemy): React reported
+  "Invalid hook call … more than one copy of React" and the page rendered
+  nothing. `demo/vite.config.ts` now dedupes react and react-dom.
+
+**Consumer action:** none. `recordsDataSource(client)` is unchanged at the call
+site; a host that deliberately wants a different fallback passes it second.
+
 ## 0.3.1
 
 Ships the canonical `TablesHome`, `TablePage`, `RecordsMount`, and table-creation helpers

package/dist/index.cjs

@@ -2190,6 +2190,12 @@ function ProposalRow({
   const [confirming, setConfirming] = (0, import_react32.useState)(false);
   async function applyThroughTheStore() {
     if (change.act === "add") {
+      if (!change.table) {
+        return {
+          settled: "refused",
+          sentence: "This proposal asks to add a record but does not name the table it goes in, so nothing was written."
+        };
+      }
       const written = await client.recordWrite({ table_id: change.table, data: change.data ?? {} });
       return written.ok ? { settled: "accepted", sentence: "Written." } : { settled: "refused", sentence: written.error.message };
     }
@@ -5677,11 +5683,16 @@ function RecordsMount({
 function personActor(userId) {
   return userId ? { actor: "user", user_id: userId } : { actor: "user" };
 }
-function recordsDataSource(client, schema = "custom") {
+function recordsDataSource(client, fallbackSchema = "custom") {
   const supabase = client;
   return {
-    rpc: (fn, args) => supabase.schema(schema).rpc(fn, args),
-    schema: (name) => supabase.schema(name)
+    rpc(fn, args, options) {
+      const on = supabase.schema(options?.schema ?? fallbackSchema);
+      return on.rpc(fn, args);
+    },
+    schema(name) {
+      return supabase.schema(name);
+    }
   };
 }
 
@@ -5890,7 +5901,11 @@ var import_react77 = require("react");
 var import_react78 = require("@ai-matrx/records/react");
 var import_design_system36 = require("@ai-matrx/design-system");
 var import_jsx_runtime38 = require("react/jsx-runtime");
-function TablePage({ tableId, pageSize = 100, className }) {
+var DEFAULT_VIEW_NAME = "All records";
+function defaultView(tableId) {
+  return { name: DEFAULT_VIEW_NAME, subject: tableId, layout: "grid", isDefault: true };
+}
+function TablePage({ tableId, pageSize = 100, seedViews, className }) {
   const table = (0, import_react78.useTable)(tableId);
   const rights = useTableRights(table.data);
   const [view, setView] = (0, import_react77.useState)(null);
@@ -5902,7 +5917,15 @@ function TablePage({ tableId, pageSize = 100, className }) {
   return /* @__PURE__ */ (0, import_jsx_runtime38.jsxs)("div", { className: (0, import_design_system36.cn)("flex min-h-0 gap-4", className), children: [
     /* @__PURE__ */ (0, import_jsx_runtime38.jsxs)("div", { className: "flex min-w-0 flex-1 flex-col gap-2", children: [
       /* @__PURE__ */ (0, import_jsx_runtime38.jsxs)("div", { className: "flex flex-wrap items-center gap-1.5", children: [
-        /* @__PURE__ */ (0, import_jsx_runtime38.jsx)(ViewBar, { tableId, onActiveView: setView, className: "min-w-0 flex-1" }),
+        /* @__PURE__ */ (0, import_jsx_runtime38.jsx)(
+          ViewBar,
+          {
+            tableId,
+            onActiveView: setView,
+            seed: seedViews ?? [defaultView(tableId)],
+            className: "min-w-0 flex-1"
+          }
+        ),
         rights.write ? /* @__PURE__ */ (0, import_jsx_runtime38.jsx)(import_design_system36.Button, { size: "sm", onClick: () => show("new-record"), children: "New record" }) : null,
         rights.admin ? /* @__PURE__ */ (0, import_jsx_runtime38.jsxs)(import_jsx_runtime38.Fragment, { children: [
           /* @__PURE__ */ (0, import_jsx_runtime38.jsx)(import_design_system36.Button, { size: "sm", variant: "outline", onClick: () => show("field"), children: "Add field" }),