@ai-matrx/records-ui 0.4.3 → 0.5.4

package/CHANGELOG.md

@@ -1,5 +1,84 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.5.4
+
+Makes the live FormBuilder certification wait for the editor state that follows
+the saved-form tab, instead of asserting synchronously between the two React
+effects.
+
+### Consumer action
+
+None. This changes only the live certification harness.
+
+## 0.5.3
+
+Makes the certification harness's raw record selector hide soft-deleted rows
+by default, matching the active-record behavior of the store's public read
+doors. An explicit `deleted_at` filter still allows a test to inspect
+tombstones intentionally.
+
+### Consumer action
+
+None. This changes only the live certification harness.
+
+## 0.5.2
+
+Resets records inside the test organization's harness-owned `records_ui_*`
+package Tables through the real delete door when certification starts. A view,
+form, or action edited by an earlier run can no longer override the next run's
+declared seed while product behavior continues to preserve real user edits.
+
+### Consumer action
+
+None. This changes only the live certification harness.
+
+## 0.5.1
+
+Builds the 0.5.0 system-table reconciliation against the refreshed 240-door
+`@ai-matrx/records` contract after the dependency's live release guard caught
+two newly registered store doors.
+
+### Consumer action
+
+None. The public API is unchanged.
+
+## 0.5.0
+
+**A package Table that changed SHAPE under an organization that already had a
+copy.** `ActionInbox` could not record an outcome in one organization: its copy
+of `records_ui_action` held `status` as a uuid-shaped Field while this package
+declares it `text`, so every outcome write was refused `22P02 invalid input
+syntax for type uuid: "open"`. The store was right; this package was the one out
+of date. `ensureSystemTable` reconciled a MISSING Field on every load and never
+looked at a Field it already had, so the organization that got its copy first
+was the one where the package quietly stopped working.
+
+Reconciliation is now two questions, not one — which Fields are missing, and
+which are there with the wrong shape. Shape means exactly the two properties
+that decide what a value is MADE OF, and therefore what the store will accept:
+the behaviour (FLD-1) and whether it is multi (FLD-2). Label, sort, required and
+config are deliberately left alone — they are presentation and policy, an
+organization may legitimately have moved them, and none of them can make a write
+fail. Nothing is ever renamed or removed.
+
+Also fixed alongside it: a refusal from the FIRST declaration of a package Table
+was both returned as this package's never-throw envelope and left as an
+unhandled promise rejection, so a refusal that had in fact been reported
+properly also produced a red console (and, under a test runner, a failed run).
+
+Proved against the LIVE store in `demo/system-table-shape.test.tsx`: the Table
+is declared with the old behaviour, the module is reloaded — which is what a
+page load is, and the only way an organization ever meets a newer package — and
+the new spec is ensured over it. RED without the fix: `expected 'range' to be
+'text'`.
+
+### Consumer action
+
+None. The public API is unchanged, and the reconciliation is automatic on the
+next load of any screen that opens a package-owned Table. An organization whose
+copy drifted is levelled the first time a person opens that screen — there is
+nothing to run and nothing to migrate.
+
 ## 0.4.3
 
 Resets the harness-owned demo table through the store's real read and delete

package/dist/index.cjs

@@ -980,17 +980,18 @@ async function ensureSystemTable(client, spec) {
   if (found) {
     const grown = await addMissingFields(client, spec, found.id);
     if (!grown.ok) return grown;
+    const levelled = await reconcileFieldShapes(client, spec, found.id);
+    if (!levelled.ok) return levelled;
     return { ok: true, data: found.id };
   }
   let settle = () => void 0;
   let fail = () => void 0;
-  inFlight.set(
-    cacheKey,
-    new Promise((resolve, reject) => {
-      settle = resolve;
-      fail = reject;
-    })
-  );
+  const pending = new Promise((resolve, reject) => {
+    settle = resolve;
+    fail = reject;
+  });
+  pending.catch(() => void 0);
+  inFlight.set(cacheKey, pending);
   const declared = await declare(client, spec);
   if (declared.ok) settle(declared.data);
   else {
@@ -1019,6 +1020,22 @@ async function addMissingFields(client, spec, tableId) {
   }
   return { ok: true, data: true };
 }
+async function reconcileFieldShapes(client, spec, tableId) {
+  const held = await client.fields({ table_id: tableId });
+  if (!held.ok) return held;
+  const byKey = new Map(held.data.map((f) => [f.key, f]));
+  for (const field of spec.fields) {
+    const have = byKey.get(field.key);
+    if (!have) continue;
+    const patch = {};
+    if (have.type !== field.type) patch.type = field.type;
+    if (have.multi !== (field.multi ?? false)) patch.multi = field.multi ?? false;
+    if (Object.keys(patch).length === 0) continue;
+    const written = await client.recordUpdate({ record_id: have.id, patch });
+    if (!written.ok) return written;
+  }
+  return { ok: true, data: true };
+}
 function fieldDocument(field, tableId) {
   return {
     key: field.key,