@ultimat3/entity 5.0.0 → 6.0.0

package/CLAUDE.md

@@ -4,7 +4,7 @@ Columns + invariants; the row type is derived from the columns. Tier 2.
 
 ## Boundary
 
-- May import `@ultimat3/core`, `@ultimat3/schema` and `@ultimat3/db`. Nothing else — `http`,
+- May import `@ultimat3/core`, `@ultimat3/schema`, `@ultimat3/db` and `@ultimat3/time` (tier 1 — `columns.ts` and `columns-data.ts` read its `isValidTimeZone`, so a zone this package accepts is one `@ultimat3/time` can do arithmetic in). Nothing else — `http`,
   `policy` and `auth` are the same tier.
 - `db` is tier 1 (it imports only `core`), which is what lets the Postgres driver live **here**
   rather than in a tier-3 package: `Driver` and its production implementation stay in one place.
@@ -564,7 +564,7 @@ Columns + invariants; the row type is derived from the columns. Tier 2.
   hole open on exactly the unauthenticated path. **Outside every request context there is no actor
   to derive from** — a script, a seed, a test harness — so the caller names the tenant itself and
   `X_TENANCY_UNSCOPED` still refuses a plan that names none. There is no build-time tenancy step in
-  `x verify` (its 17 steps check none) and the old comment in `tenancy.ts` claiming one was wrong:
+  `x verify` (its 19 steps check none) and the old comment in `tenancy.ts` claiming one was wrong:
   the tenant is a request-time value, so the seam is the enforcement.
 - **`crossTenant(reason, fn)` (`cross-tenant.ts`) is the ONE way to read across tenants**, for the
   three cases that have no single one: an admin surface over every org, background reconciliation,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/entity",
-  "version": "5.0.0",
+  "version": "6.0.0",
   "description": "A table + its domain type + invariants the database also enforces",
   "license": "MIT",
   "type": "module",
@@ -31,9 +31,9 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/core": "5.0.0",
-    "@ultimat3/db": "5.0.0",
-    "@ultimat3/schema": "5.0.0",
-    "@ultimat3/time": "5.0.0"
+    "@ultimat3/core": "6.0.0",
+    "@ultimat3/db": "6.0.0",
+    "@ultimat3/schema": "6.0.0",
+    "@ultimat3/time": "6.0.0"
   }
 }

package/src/columns.ts

@@ -10,6 +10,7 @@ import {
   isMoneyScale,
   MAX_MONEY_SCALE,
 } from '@ultimat3/schema';
+import { isValidTimeZone } from '@ultimat3/time';
 import {
   assertColumnName,
   BARE,
@@ -176,22 +177,22 @@ export const url = (): Column<string> =>
     { check: (name) => `${name} ~ '^https?://'` },
   );
 
-const isIanaZone = (value: string): boolean => {
-  try {
-    new Intl.DateTimeFormat('en', { timeZone: value }).format(0);
-    return true;
-  } catch {
-    return false;
-  }
-};
-
 /**
- * IANA identifiers, checked against `Intl` when the column is declared — a typo or a UTC offset
- * is a startup error rather than a row nobody can format. An offset is wrong twice a year.
+ * IANA identifiers, checked when the column is declared — a typo, an abbreviation or a UTC offset
+ * is a startup error rather than a row nobody can format.
+ *
+ * The check is `@ultimat3/time`'s own `isValidTimeZone`, imported and never restated: `time` is
+ * tier 1 and this package is tier 2, so the one rule is a downward import away. A local
+ * `new Intl.DateTimeFormat(…)` probe was the second answer to that question, and the two stopped
+ * agreeing — `Intl` answers "can I format this", never "is this IANA", and ICU 78 (Bun 1.4)
+ * resolves `CET`, `EST`, `GMT`, `Zulu` and `Japan`, so `tz(['CET'])` declared a column every
+ * `format` call above it then refused with `X_TIMEZONE_INVALID`. A leading-sign offset (`+01:00`)
+ * resolved under every runtime this framework has shipped on, and carries no DST rule at all, so
+ * it is wrong twice a year on top of being unformattable.
  */
 export const tz = <const Z extends readonly string[]>(zones: Z): Column<Z[number]> => {
   for (const zone of zones) {
-    if (!isIanaZone(zone)) reject('iana-tz', `${zone} is not an IANA time zone`);
+    if (!isValidTimeZone(zone)) reject('iana-tz', `${zone} is not an IANA time zone`);
   }
   const allowed = new Set<string>(zones);
   return column<Z[number]>(