@ai-matrx/records 0.4.1 → 0.5.1

package/CHANGELOG.md

@@ -1,5 +1,46 @@
 # Changelog — @ai-matrx/records
 
+## 0.5.1
+
+Refreshes the generated store contract to the live 240-door registry caught by
+the blocking release guard after 0.5.0 was tagged.
+
+### Consumer action
+
+None. The two new door entries are additive generated contract data.
+
+## 0.5.0
+
+**Two refusal classes the store really raises, which this package answered with
+"something this package does not recognise".** Both were found by walking the
+real product on 2026-09-19, and in both the screen showed the store's own
+sentence — honest, but the class was nameable and this package had not named it.
+
+- **`57014` — the store cancelled the statement at its own timeout.** Seen on an
+  organization whose Table kernel is large enough for `custom.read_records` to
+  run out of time. It is now `timed_out`, which is, with `stale_read`, one of
+  only two refusals in the vocabulary worth REPEATING: nothing was refused on
+  its merits and nothing was written, so a screen can offer "try again" honestly
+  instead of showing a failure a person cannot act on.
+- **`22P02` — a value that does not fit the type the store holds for it.** Seen
+  as `invalid input syntax for type uuid: "open"`, writing the text `open` into
+  an organization's copy of a package Table whose `status` Field was uuid-shaped.
+  It is `invalid_argument`, which is what it is: the CALL is wrong for the shape
+  the store holds, and the store's own message names the value and the type.
+
+Both are proved against the LIVE store in `src/__tests__/real-doors.test.ts`:
+the SQLSTATEs are raised by the real database inside the suite's own
+rolled-back transaction and read back out of psql's verbose report, and the only
+thing asserted about this package is what it makes of them. Each case is RED
+without its map entry (`expected 'internal' to be 'timed_out'`).
+
+### Consumer action
+
+`RecordsErrorCode` gains one member, `timed_out`. A host that switches
+exhaustively over the union must add an arm for it; every other host needs
+nothing beyond taking `latest`. A host that was special-casing `internal` to
+recognise a timeout by its message text should branch on `timed_out` instead.
+
 ## 0.4.1
 
 Carries the live Supabase adapter proof through the shared npm publishing lane

package/dist/core/index.cjs

@@ -282,6 +282,8 @@ var STORE_DOORS = [
   { name: "doc_unresolved_tokens", args: "p_organization_id uuid, p_table_id uuid, p_body text", returns: "TABLE(raw text, field_id uuid, why text)", security: "invoker" },
   { name: "doors_not_deciding_the_caller", args: "", returns: "TABLE(function_name text, identity_args text)", security: "invoker" },
   { name: "doors_not_deciding_the_record", args: "", returns: "TABLE(function_name text, identity_args text, why text)", security: "invoker" },
+  { name: "doors_not_on_one_ladder", args: "", returns: "TABLE(function_name text, identity_args text, why text)", security: "invoker" },
+  { name: "effective_level", args: "p_user_id uuid, p_organization_id uuid, p_id uuid, p_type text DEFAULT 'record'::text", returns: "permission_level", security: "definer" },
   { name: "export_records", args: "p_organization_id uuid, p_table_id uuid, p_limit integer DEFAULT 1000", returns: "TABLE(id uuid, document jsonb)", security: "invoker" },
   { name: "external_foreign_table_findings", args: "", returns: "SETOF text", security: "definer" },
   { name: "external_history_event", args: "p_organization_id uuid, p_link_id uuid, p_operation text", returns: "bigint", security: "definer" },
@@ -1713,6 +1715,13 @@ var BY_SQLSTATE = {
   "23514": "refused_by_rule",
   "22004": "invalid_argument",
   "22023": "invalid_argument",
+  // 22P02 — a value does not fit the type the store holds for it. The class is
+  // real and was hit live: an organization whose copy of a package table grew
+  // `status` as a uuid-valued Field was sent the text "open", and the store
+  // answered `invalid input syntax for type uuid: "open"`. It is the CALL that
+  // is wrong for the shape the store holds, which is what `invalid_argument`
+  // already means — the store's own sentence names the value and the type.
+  "22P02": "invalid_argument",
   "02000": "not_found",
   "23503": "missing_reference",
   "23505": "already_exists",
@@ -1724,6 +1733,13 @@ var BY_SQLSTATE = {
   // they just lost access to. It is retryable on a fresher connection, which is
   // a different instruction from every other refusal here.
   "40001": "stale_read",
+  // 57014 — the store cancelled the statement at its own timeout. Like
+  // `stale_read` and unlike every other refusal here, the call was never
+  // refused on its merits: the same call on a smaller page, or once the
+  // organization's kernel is not being rewritten, can succeed. It gets its own
+  // code so a screen can offer "try again" honestly instead of showing a
+  // failure sentence the caller cannot act on.
+  "57014": "timed_out",
   // PostgREST's own two: the store is not being SERVED, which is a different
   // thing from the store refusing. `custom` absent from `pgrst.db_schemas`, or
   // the grants not copied, land here.