@ai-matrx/records 0.39.0 → 0.40.0

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog — @ai-matrx/records
 
+## 0.40.0
+
+**The parity floor this package types is asserted against the one the store ships.**
+
+`checkbox` landed as the fourteenth parity type and `store.generated.ts` picked it
+up — but nothing made that agreement a test. Everything that spelled the floor out
+by hand went stale in the same hour: three of the store's own refusal hints, the
+`FieldTypeWord` doc comment, `UseCaseField.parityType`'s doc comment and the
+use-case README's list, all still saying thirteen. A person who asked for a
+checkbox could be told by the store that checkboxes do not exist.
+
+* `src/__tests__/real-doors.test.ts` gains three cases, in the one suite that runs
+  against the live store: `PARITY_FIELD_TYPES` is exactly
+  `custom.parity_field_types()` name for name (a diff NAMES the missing type, it
+  never prints a count); every parity type and every behaviour the store ships is
+  a legal `parityType` word in `RESOLVABLE_FIELD_TYPE_WORDS`; and `checkbox` is
+  present with behaviour `boolean`, with a compile-time assertion that the
+  `ParityFieldType` union still admits it. Shown RED: with the `checkbox` row
+  removed from `store.generated.ts` all three fail and the first one says
+  "expected 'attachment, currency, …' to be 'attachment, checkbox, …'".
+* The four places that wrote the count or the list out by hand now point at the
+  derived set instead. No number is written down anywhere in this package.
+* `store.generated.ts` regenerated against the live store (542 doors, 1023 entity
+  tokens); `pnpm check:store-registry` was RED on that drift before this release.
+
+**Consumer action:** none.
+
+**Why 0.40.0 and not 0.38.0.** This work landed on `main` a few minutes after
+0.39.0 was tagged, so the published 0.39.0 does not contain it. The version number
+moves rather than the tag.
+
 ## 0.39.0
 
 **Two things a records screen could not know: that a table's shape had changed,
@@ -45,33 +76,6 @@ of the set, and nothing else. `src/__tests__/page-truth.test.ts` asserts the
 refusal against the live store, so the day it softens into a silent shrink the
 suite goes red and names the inference that has to change with it.
 
-## 0.38.0
-
-**The parity floor this package types is asserted against the one the store ships.**
-
-`checkbox` landed as the fourteenth parity type and `store.generated.ts` picked it
-up — but nothing made that agreement a test. Everything that spelled the floor out
-by hand went stale in the same hour: three of the store's own refusal hints, the
-`FieldTypeWord` doc comment, `UseCaseField.parityType`'s doc comment and the
-use-case README's list, all still saying thirteen. A person who asked for a
-checkbox could be told by the store that checkboxes do not exist.
-
-* `src/__tests__/real-doors.test.ts` gains three cases, in the one suite that runs
-  against the live store: `PARITY_FIELD_TYPES` is exactly
-  `custom.parity_field_types()` name for name (a diff NAMES the missing type, it
-  never prints a count); every parity type and every behaviour the store ships is
-  a legal `parityType` word in `RESOLVABLE_FIELD_TYPE_WORDS`; and `checkbox` is
-  present with behaviour `boolean`, with a compile-time assertion that the
-  `ParityFieldType` union still admits it. Shown RED: with the `checkbox` row
-  removed from `store.generated.ts` all three fail and the first one says
-  "expected 'attachment, currency, …' to be 'attachment, checkbox, …'".
-* The four places that wrote the count or the list out by hand now point at the
-  derived set instead. No number is written down anywhere in this package.
-* `store.generated.ts` regenerated against the live store (542 doors, 1023 entity
-  tokens); `pnpm check:store-registry` was RED on that drift before this release.
-
-**Consumer action:** none.
-
 ## 0.37.0
 
 **Three doors the store already had and this client could not reach.**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-matrx/records",
-  "version": "0.39.0",
+  "version": "0.40.0",
   "description": "The headless client of the AI Matrx record store: the Table / Field / Rule / Record / Relation / Home types, the closed vocabularies and refusal codes read from the store itself, the typed calls over the store's doors and nothing else, the merge-field declaration, a validation mirror that predicts only what the store's own triggers refuse, and the never-throw result envelope. Zero React, zero DOM in the root and /core.",
   "type": "module",
   "main": "./dist/index.cjs",