@12-apps/prisma 6.1.1 → 6.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@12-apps/prisma",
-  "version": "6.1.1",
+  "version": "6.2.0",
   "description": "Prisma host: the multi-file schema folder, the plugin migration seam, and the shared PrismaClient singleton with its audit / append-only extensions",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -63,23 +63,23 @@
     "pglite-prisma-adapter": "0.7.2"
   },
   "devDependencies": {
-    "@12-apps/audit": "^5.0.1",
-    "@12-apps/auth": "^2.5.0",
-    "@12-apps/entitlements": "^3.1.0",
-    "@12-apps/entity-lifecycle": "^4.2.0",
-    "@12-apps/eslint-config": "^1.21.0",
-    "@12-apps/feature-flags": "^2.0.1",
-    "@12-apps/jobs": "^4.2.0",
-    "@12-apps/mcp": "^3.5.0",
-    "@12-apps/notifications": "^4.1.1",
-    "@12-apps/onboarding": "^2.0.1",
-    "@12-apps/payments-backend": "^4.14.0",
-    "@12-apps/product-research": "^2.0.0",
-    "@12-apps/rbac": "^4.1.0",
-    "@12-apps/realtime": "^2.0.0",
-    "@12-apps/report-builder": "^5.3.0",
-    "@12-apps/shift": "^3.0.1",
-    "@12-apps/typescript-config": "^1.20.0",
+    "@12-apps/audit": "^5.0.2",
+    "@12-apps/auth": "^2.7.0",
+    "@12-apps/entitlements": "^3.2.0",
+    "@12-apps/entity-lifecycle": "^4.4.0",
+    "@12-apps/eslint-config": "^1.21.1",
+    "@12-apps/feature-flags": "^2.1.1",
+    "@12-apps/jobs": "^4.3.1",
+    "@12-apps/mcp": "^3.5.1",
+    "@12-apps/notifications": "^4.2.0",
+    "@12-apps/onboarding": "^2.1.0",
+    "@12-apps/payments-backend": "^4.15.0",
+    "@12-apps/product-research": "^2.2.0",
+    "@12-apps/rbac": "^4.2.0",
+    "@12-apps/realtime": "^2.2.0",
+    "@12-apps/report-builder": "^5.4.1",
+    "@12-apps/shift": "^3.2.0",
+    "@12-apps/typescript-config": "^1.20.1",
     "@types/node": "^22.10.6",
     "@vitest/coverage-v8": "^3.2.4",
     "eslint": "^9.39.1",

package/prisma/migrations/20260821120000_shift_kind_host_vocabulary/migration.sql

@@ -0,0 +1,25 @@
+-- @12-apps/shift: `kind` carries HOST vocabulary, so the database stops naming it.
+--
+-- `shifts_kind_check` restricted every adopter's `shifts.kind` to two values
+-- taken from the staff structure of the application this package was extracted
+-- from. That is the most structural form this leak can take. A leaked string is
+-- cosmetic and a leaked type union is at least deletable in a major; a CHECK
+-- constraint is a fact recorded in the adopter's own database, and a host whose
+-- workers are not organised into those two groups could not insert a row at all
+-- — no configuration this package offered could reach it.
+--
+-- What replaces it is the guarantee the package genuinely owns: `kind` is
+-- present and not blank. WHICH kinds exist is now stated by the host and
+-- enforced at the open, by the service, against the vocabulary it was
+-- constructed with (`createShiftService(db, { kinds })`).
+--
+-- Deliberately NOT touched: `shifts_ended_reason_check`. Those three values are
+-- this package's own vocabulary — a shift ends because a worker said so, a
+-- supervisor said so, or the sweep did — and no adopter renames them.
+--
+-- Existing rows all satisfy the replacement, so this is safe to deploy against
+-- a live table with no backfill.
+ALTER TABLE "shifts" DROP CONSTRAINT IF EXISTS "shifts_kind_check";
+
+ALTER TABLE "shifts"
+  ADD CONSTRAINT "shifts_kind_present_check" CHECK (btrim("kind") <> '');

package/prisma/plugin-migrations.json

@@ -33,6 +33,7 @@
     "20260813140000_add_notification_tables",
     "20260813180000_add_realtime_outbox",
     "20260819230000_auth_email_password",
-    "20260820120000_add_user_feature_grants"
+    "20260820120000_add_user_feature_grants",
+    "20260821120000_shift_kind_host_vocabulary"
   ]
 }