@ai-matrx/records 0.58.2 → 0.58.6

package/CHANGELOG.md

@@ -1,12 +1,73 @@
 # Changelog — @ai-matrx/records
 
-## 0.58.2
+## 0.58.6 (2026-09-24 — published by PUBLISH-SWEEP-5)
+
+0.58.5 (the release run's automatic tag, run 36082256533) never reached npm: the live census found
+the store raising `XX000`, which STORE-TAILS-3 removed at the source (below). This release carries
+S5-PRIME's and S5-PRIME-2's inbox doors, which records-ui 0.85.7 needs, so it publishes first.
+
+### Lane STORE-TAILS-3 (2026-09-25)
+
+* **`42P17` is mapped to `refused_by_rule`**: the store refuses, by name, a formula / lookup /
+  rollup that would read itself round a circle (on declare and edit), and refuses a circle stored
+  before that rule when it is worked out (applied to production 2026-09-25 02:51 UTC).
+* **No door raises `XX000` any more**: `custom._view_key_value` judges `filters` and refuses a
+  store-written or unknown view setting as a named `22023` (applied 03:02 UTC). The live census
+  clause "maps every refusal class the store actually raises" is green again.
+* **The live suite's no-standing clause reads its stranger organization from the write target**:
+  a typed production id that the rehearsal branch does not hold made the FIXTURE answer 23503
+  (`knob_override_organization_id_fkey`) before the door ever ran; the door itself answers 42501
+  on every target (measured on the branch and read-only on production).
+* `src/store.generated.ts` regenerated against the live store (686 doors; new server-only helpers
+  `archive_event_of`, `far_value`, `record_value_one`, `field_cycle`,
+  `field_context_policy_floor`, `context_policy_rank`). No consumer action.
+
+### Lane S5-PRIME-2 (2026-09-24)
+
+* **Snooze and clear, as one person's own inbox state** (uichamp_s5b + uichamp_s5b2, applied to
+  production 2026-09-25 02:13 UTC): `inboxSnooze({ item_id, until })`, `inboxUnsnooze`,
+  `inboxClear` (a decision still owed is refused, SQLSTATE 55000, "This one needs a decision"),
+  `inboxUnclear`, and `inboxCounts({ everyOrganization })` — waiting / snoozed / cleared / overdue
+  per organization, counted by the same predicate the inbox lists with (the shell badge's number).
+  Types `WorkInboxView`, `InboxStateChange`, `InboxCounts`.
+* **`workInbox({ view })`**: `"inbox"` (default) hides what this person snoozed or cleared,
+  `"snoozed"` lists what they put off (soonest back first), `"done"` what they cleared.
+  `WorkInboxItem` gains `snoozed_until`, `cleared_at`, `snoozed_count`, `cleared_count`.
+* **`P0002` is mapped to `not_found`**: the inbox doors answer it for an id that is not in this
+  person's inbox (an invented id, somebody else's item and another organization's alike).
+* `src/store.generated.ts` regenerated against the live store (679 doors, knob
+  `inbox_reminder_after_days`).
+
+### Lane S5-PRIME (2026-09-24)
+
+* **`WorkInboxItem` carries the table and, when closed, who decided it and when**: `table_id`,
+  `table_name`, `decided_by`, `decided_by_name`, `decided_at`, `outcome` — the six columns
+  `custom.work_inbox` now answers (uichamp_s5, applied to production 2026-09-25 01:07 UTC).
+* **`WorkApprovalState`** = `pending | approved | declined | withdrawn`. `withdrawn` is the store's
+  own close: archiving a record or table withdraws the approvals waiting on it, with the reason.
+* **`WorkDecideVerdict` gains `archived`**: `work_decide_many` answers it when the thing an approval
+  would change is archived (SQLSTATE 55000 from `work_approval_decide`, sentence names it).
+* `src/store.generated.ts` regenerated against the live store (669 doors).
+
+## 0.58.5
 
 Automatic changed-only republish (docs/metadata drift since the last tag — see
-`git diff npm/records/v0.58.1..npm/records/v0.58.2 -- apps/shared/records`).
+`git diff npm/records/v0.58.4..npm/records/v0.58.5 -- apps/shared/records`).
 No source changes intended and no consumer action required.
 
-## Unreleased — lane SC-1-TAILS (2026-09-24)
+## 0.58.4 (2026-09-24 — published by PUBLISH-SWEEP-5)
+
+**`src/store.generated.ts` is the live main database's catalogue after the 2026-09-24 production
+applies** (666 doors; `a86b902c12`): `table_home` / `table_move`, `portal_form` / `portal_form_submit`,
+`record_aggregate(…, p_compare)`, `pipeline_board`, `plural_of` and the rest now answer instead of
+`door_absent`, and `entity_reference` is a declarable kind. 0.58.3 (the release run's automatic tag,
+run 36079091025) never reached npm: `real-doors` found `portal_form` claimed absent while live, and
+asked for `record_aggregate`'s old eight-argument signature. **`55000` is mapped** to
+`refused_by_rule`: `custom.table_move` raises it when a move the table's present state does not allow
+(a destination that cannot take it, something holding it, contents in a circle) is refused in the
+store's own words and nothing moves.
+
+### Lane SC-1-TAILS (2026-09-24)
 
 * **`client.tableHome({ table_id })` and `client.tableMove({ table_id, to_organization_id, expected_version })`** — the
   store utility for "which organization is this table in, and move it" (`custom.table_home` / `custom.table_move`,
@@ -18,6 +79,18 @@ No source changes intended and no consumer action required.
 * **Consumer action:** matrx-frontend swaps `features/unified-data/where-it-lives/` for `@ai-matrx/records-ui`'s
   `WhereItLives` once both are installed. `pnpm records:generate` after the chair applies the doors.
 
+## 0.58.3
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/records/v0.58.2..npm/records/v0.58.3 -- apps/shared/records`).
+No source changes intended and no consumer action required.
+
+## 0.58.2
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/records/v0.58.1..npm/records/v0.58.2 -- apps/shared/records`).
+No source changes intended and no consumer action required.
+
 ## 0.58.1
 
 Automatic changed-only republish (docs/metadata drift since the last tag — see
@@ -831,7 +904,6 @@ settings key itself is exempt, since that is where the classification belongs.
 Both patterns ship in `./use-cases`, so aidream's guard, matrx-frontend's guard and
 this library's own validator can never disagree about what junk means.
 
-
 ## 0.28.0
 
 **The owner's side of a booking page — the one method that was standing between
@@ -931,7 +1003,6 @@ what `results.ts` says in as many words), a failure with NO code at all is the
 network and waits, and everything the door named is a decision that stays.
 `isDecided` takes the error, not a code, so either spelling works.
 
-
 ## 0.25.0 — 2026-09-20
 
 **A crew out in the field, and a phone with no bars (PRODUCTS row 15, P13).**
@@ -953,7 +1024,6 @@ network and waits, and everything the door named is a decision that stays.
   until a person fixes it or throws it away. `sync()` answers with per-item
   outcomes, never a boolean.
 
-
 ## 0.24.0 — 2026-09-20
 
 **0.23.0 never reached npm.** Its release run died before any package could be
@@ -966,7 +1036,6 @@ a directory only, which is how a symlink of that name walked past it. This
 version is 0.23.0's contents from the repaired tree; a tag is never moved, so
 0.23.0 is simply absent from npm.
 
-
 ## 0.23.0
 
 **A column a model owns — seven doors, and the four states one cell can be in.**
@@ -1048,7 +1117,6 @@ main:
 > while a merge of main was still open, and a tag is never moved. `0.21.0` is
 > the first version that carries both. Nobody should sit on 0.20.0.
 
-
 ## 0.20.0
 
 **"Every new hire gets these twelve steps." — the checklist doors, PRODUCTS row 13.**
@@ -1077,7 +1145,6 @@ THE DEPENDENCY RULE LIVES IN THE STORE, not in these methods: a BEFORE trigger
 on `custom.record` refuses a step reaching Done while a step it waits for is
 open, so `workSetState` meets the same sentence `checklistStepComplete` does.
 
-
 ## 0.19.0
 
 **"Pull my spreadsheet in" — the import doors, and the address a Table can own.**
@@ -1343,7 +1410,6 @@ and the notifier does not: `muted`, and `i_may_mute`.
 client can call. Muting is honoured inside that one reader, so a screen can
 never say a subscription is off while it keeps firing.
 
-
 ## 0.11.0
 
 **The publish gate stops red-lighting on other lanes' migrations.** `the
@@ -1469,7 +1535,6 @@ nothing but the count: the door catalogue is asserted EQUAL to the live store's,
 and other lanes landed a door in the ten minutes between the regeneration and
 the publish. No source change and no consumer action.
 
-
 ## 0.6.1
 
 0.6.0's release gate caught four things the live store had changed since the
@@ -1493,7 +1558,6 @@ contract was generated, and this is all four.
 
 None.
 
-
 ## 0.6.0
 
 **A column can be added.** The store grew the three doors a Field always needed
@@ -1520,7 +1584,6 @@ and this package carries them.
 Nothing breaks. A host that writes Fields with `recordWrite` should move to
 `useFieldMutation().declare` — the old path is the defect, not a deprecation.
 
-
 ## 0.5.2
 
 Automatic changed-only republish (docs/metadata drift since the last tag — see