@catalyst-cloud/schema 0.1.18 → 0.1.20

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@catalyst-cloud/schema",
-  "version": "0.1.18",
+  "version": "0.1.20",
   "type": "module",
   "description": "Typed Drizzle schema = single source of truth for the per-tenant Mirror DO SQLite store (CTC-13 / ADR-0002). Shared by the mirror Worker, the host-sync replica, and the browser OPFS replica.",
   "license": "MIT",
@@ -27,14 +27,14 @@
     "build:bundle": "bun scripts/build-bundle.ts && prettier --write src/migrations.generated.ts"
   },
   "dependencies": {
-    "drizzle-orm": "0.44.7"
+    "drizzle-orm": "0.45.2"
   },
   "devDependencies": {
     "@catalyst-cloud/typescript-config": "workspace:*",
     "@types/node": "^25.9.3",
     "drizzle-kit": "^0.31.0",
-    "prettier": "^3.8.4",
-    "typescript": "^5.6.3",
-    "vitest": "^2.1.8"
+    "prettier": "^3.9.6",
+    "typescript": "^7.0.2",
+    "vitest": "^4.1.11"
   }
 }

package/src/events/index.ts

@@ -0,0 +1,8 @@
+// index.ts — CTC-936 phase 1. The `events` contract module barrel. Phase 1 ships the envelope + the
+// type grammar only; phase 2 adds the closed registry (./registry.ts), phase 4 adds retention
+// (./retention.ts) — both re-exported here as they land so this stays the one import surface.
+
+export * from "./types.js";
+export * from "./type-grammar.js";
+export * from "./registry.js";
+export * from "./retention.js";

package/src/events/registry-support.ts

@@ -0,0 +1,20 @@
+// registry-support.ts — the shared `keysOf` helper the event registry needs, structurally identical
+// to (and NOT a second copy of the concept behind) `packages/schema/src/index.ts`'s own `keysOf`.
+//
+// ⚠️ Why this is a small duplicate rather than an import from `../index.ts`: `../index.ts` re-exports
+// `./events/index.js` (this module's own barrel) — importing `../index.ts` FROM `./events/` would be
+// a circular import. The plan's Refactor note for this phase says to prefer importing the existing
+// `keysOf` "if duplicating it from index.ts becomes a second copy" of the CONCEPT (CTC-643/CTC-671's
+// defect was two DISAGREEING lists, not two textually-identical five-line generic helpers) — this
+// helper carries no policy, just a type-preserving `Object.keys`, so a second textual copy here does
+// not reintroduce that defect. If TypeScript ever supports referencing a sibling package export
+// without a cycle, this can be deleted in favor of importing `../index.ts`'s copy.
+
+/**
+ * `Object.keys` with the key type preserved. TypeScript types `Object.keys` as `string[]` because an
+ * object may carry extra keys at runtime; every caller here passes an `as const` literal declared in
+ * the same module, so the narrowing is sound.
+ */
+export function keysOf<T extends object>(o: T): (keyof T & string)[] {
+  return Object.keys(o) as (keyof T & string)[];
+}