@12-apps/prisma 6.4.0 → 6.6.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@12-apps/prisma",
-  "version": "6.4.0",
+  "version": "6.6.0",
   "sideEffects": false,
   "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",
@@ -13,7 +13,7 @@
     }
   },
   "scripts": {
-    "build": "node scripts/sync-lifecycle-schema.mjs && node scripts/sync-research-schema.mjs && node scripts/sync-shift-schema.mjs --check && node scripts/sync-jobs-schema.mjs --check && node scripts/sync-entitlements-schema.mjs --check && node scripts/sync-payments-schema.mjs --check && node scripts/sync-report-builder-schema.mjs --check && node scripts/sync-feature-flags-schema.mjs --check && node scripts/sync-rbac-schema.mjs --check && node scripts/sync-notifications-schema.mjs --check && node scripts/sync-onboarding-schema.mjs --check && node scripts/sync-mcp-schema.mjs --check && node scripts/sync-realtime-schema.mjs --check && node scripts/sync-audit-schema.mjs --check && node scripts/sync-discounts-schema.mjs --check && node scripts/sync-prisma-plugins.mjs --check && prisma generate && tsc",
+    "build": "node scripts/sync-lifecycle-schema.mjs && node scripts/sync-research-schema.mjs && node scripts/sync-shift-schema.mjs --check && node scripts/sync-jobs-schema.mjs --check && node scripts/sync-entitlements-schema.mjs --check && node scripts/sync-payments-schema.mjs --check && node scripts/sync-report-builder-schema.mjs --check && node scripts/sync-feature-flags-schema.mjs --check && node scripts/sync-rbac-schema.mjs --check && node scripts/sync-notifications-schema.mjs --check && node scripts/sync-onboarding-schema.mjs --check && node scripts/sync-mcp-schema.mjs --check && node scripts/sync-realtime-schema.mjs --check && node scripts/sync-audit-schema.mjs --check && node scripts/sync-i18n-schema.mjs --check && node scripts/sync-discounts-schema.mjs --check && node scripts/sync-prisma-plugins.mjs --check && prisma generate && tsc",
     "clean": "rm -rf dist node_modules coverage",
     "test": "node ../../scripts/vitest-with-teardown.mjs run",
     "test:watch": "vitest watch",
@@ -21,7 +21,7 @@
     "lint": "pnpm run lint:files .",
     "lint:fix": "bash -c 'eslint \"${@:-.}\" --max-warnings 0 --fix' _",
     "typecheck": "tsc --noEmit",
-    "prisma:generate": "node scripts/sync-lifecycle-schema.mjs && node scripts/sync-research-schema.mjs && node scripts/sync-shift-schema.mjs --check && node scripts/sync-jobs-schema.mjs --check && node scripts/sync-entitlements-schema.mjs --check && node scripts/sync-payments-schema.mjs --check && node scripts/sync-auth-schema.mjs --check && node scripts/sync-report-builder-schema.mjs --check && node scripts/sync-feature-flags-schema.mjs --check && node scripts/sync-rbac-schema.mjs --check && node scripts/sync-notifications-schema.mjs --check && node scripts/sync-onboarding-schema.mjs --check && node scripts/sync-mcp-schema.mjs --check && node scripts/sync-realtime-schema.mjs --check && node scripts/sync-audit-schema.mjs --check && node scripts/sync-discounts-schema.mjs --check && node scripts/sync-prisma-plugins.mjs --check && prisma generate",
+    "prisma:generate": "node scripts/sync-lifecycle-schema.mjs && node scripts/sync-research-schema.mjs && node scripts/sync-shift-schema.mjs --check && node scripts/sync-jobs-schema.mjs --check && node scripts/sync-entitlements-schema.mjs --check && node scripts/sync-payments-schema.mjs --check && node scripts/sync-auth-schema.mjs --check && node scripts/sync-report-builder-schema.mjs --check && node scripts/sync-feature-flags-schema.mjs --check && node scripts/sync-rbac-schema.mjs --check && node scripts/sync-notifications-schema.mjs --check && node scripts/sync-onboarding-schema.mjs --check && node scripts/sync-mcp-schema.mjs --check && node scripts/sync-realtime-schema.mjs --check && node scripts/sync-audit-schema.mjs --check && node scripts/sync-i18n-schema.mjs --check && node scripts/sync-discounts-schema.mjs --check && node scripts/sync-prisma-plugins.mjs --check && prisma generate",
     "prisma:migrate": "prisma migrate dev",
     "prisma:push": "prisma db push",
     "prisma:studio": "prisma studio",
@@ -56,7 +56,8 @@
     "prisma:sync-auth": "node scripts/sync-auth-schema.mjs",
     "prisma:sync-auth:check": "node scripts/sync-auth-schema.mjs --check",
     "prisma:sync-discounts": "node scripts/sync-discounts-schema.mjs",
-    "prisma:sync-discounts:check": "node scripts/sync-discounts-schema.mjs --check"
+    "prisma:sync-discounts:check": "node scripts/sync-discounts-schema.mjs --check",
+    "prisma:sync-i18n": "node scripts/sync-i18n-schema.mjs"
   },
   "dependencies": {
     "@electric-sql/pglite": "0.2.17",
@@ -66,20 +67,21 @@
     "pglite-prisma-adapter": "0.7.2"
   },
   "devDependencies": {
-    "@12-apps/audit": "^5.4.0",
-    "@12-apps/auth": "^2.14.0",
-    "@12-apps/discounts": "^1.11.0",
-    "@12-apps/entitlements": "^3.9.0",
+    "@12-apps/audit": "^5.7.1",
+    "@12-apps/auth": "^2.19.0",
+    "@12-apps/discounts": "^1.13.0",
+    "@12-apps/entitlements": "^3.10.0",
     "@12-apps/entity-lifecycle": "^4.13.0",
     "@12-apps/eslint-config": "^1.22.0",
-    "@12-apps/feature-flags": "^2.4.0",
+    "@12-apps/feature-flags": "^2.4.1",
+    "@12-apps/i18n": "^1.3.0",
     "@12-apps/jobs": "^4.5.0",
-    "@12-apps/mcp": "^3.14.0",
-    "@12-apps/notifications": "^4.6.0",
+    "@12-apps/mcp": "^3.16.0",
+    "@12-apps/notifications": "^4.9.0",
     "@12-apps/onboarding": "^2.7.0",
-    "@12-apps/payments-backend": "^4.21.0",
-    "@12-apps/product-research": "^2.8.0",
-    "@12-apps/rbac": "^4.10.0",
+    "@12-apps/payments-backend": "^4.26.0",
+    "@12-apps/product-research": "^2.10.0",
+    "@12-apps/rbac": "^4.14.0",
     "@12-apps/realtime": "^2.6.0",
     "@12-apps/report-builder": "^5.14.0",
     "@12-apps/shift": "^3.4.0",

package/prisma/migrations/20260826170000_locale_preferences/migration.sql

@@ -0,0 +1,29 @@
+-- Which language a person reads, as a table this package owns.
+--
+-- The copy resolvers shipped first and nothing could answer them: a
+-- notification blueprint and the four auth mails both ask for the recipient's
+-- tag at the moment they render, and the only place a host kept a language was
+-- the browser's localStorage plus a cookie. That is THIS DEVICE's preference —
+-- it does not follow the person to their phone, and it is not in the room at
+-- all when a background job writes to them. So every notice resolved to the
+-- default: the mechanism was complete and the fact was missing.
+--
+-- A TABLE and not a column on the host's users, for the reason auth.prisma
+-- already states about its three credential columns: a package cannot add a
+-- column to a table it does not own, and `user_id` carries NO foreign key, so
+-- this applies to a repo whose user table is named something else, lives in
+-- another database, or does not exist yet at migrate time.
+--
+-- A row EXISTS only once somebody has chosen. There is no default and no
+-- backfill: absence is how "has not chosen" is said, and it is a different fact
+-- from "reads pt-BR". Collapsing them would make a guess indistinguishable from
+-- a choice — and since a reader's own setting outranks the tenant's, that guess
+-- would then beat a store language nobody had a chance to lose to.
+CREATE TABLE "locale_preferences" (
+    "user_id"    TEXT NOT NULL,
+    "locale"     TEXT NOT NULL,
+    "created_at" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updated_at" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "locale_preferences_pkey" PRIMARY KEY ("user_id")
+);

package/prisma/migrations/20260830120000_discount_weekly_schedule/migration.sql

@@ -0,0 +1,40 @@
+-- @12-apps/discounts: the WEEKLY schedule (FUT-996).
+--
+-- "Toda sexta, das 16:00 às 20:00" — a recurring window INSIDE the campaign
+-- `[starts_at, ends_at)`, which until now was the only scheduling a rule had.
+--
+-- ── PURELY ADDITIVE, AND THAT IS THE POINT ────────────────────────────────
+-- One nullable column, no backfill, no CHECK to widen, nothing dropped. NULL
+-- means "always, within the campaign window", which is exactly what every
+-- existing row already means — so this migration cannot change the price of
+-- anything, and the release carrying it needs none of the expand/contract
+-- ceremony a destructive DDL would (see the host's CLAUDE.md on why a
+-- `DROP COLUMN` takes production down for the length of a healthcheck).
+--
+-- Replay-safe like its predecessor: `IF NOT EXISTS` throughout.
+--
+-- ── WHY JSON RATHER THAN A FOURTH TABLE ───────────────────────────────────
+-- The recurrence is not SQL-queryable in any useful way. The admin grid's
+-- vigência filter already punts on comparing two nullable timestamps against
+-- `now()` and rides as a separate parameter the store resolves, so a schedule
+-- table would buy queryability that nothing asks for — while adding a third
+-- `include` to `loadDiscountRules`, which is on the storefront's hottest read
+-- (a whole menu page's badge preview walks it once per request).
+--
+-- The trade is stated plainly: the database cannot check this column's SHAPE.
+-- `assertSchedule` in `src/server/validate.ts` is the only gate in front of it,
+-- and the evaluator is deliberately tolerant of a row that got past it — a
+-- malformed window covers NOTHING rather than everything, so the failure mode
+-- of a bad blob is a promotion that does not fire, never a cart priced at zero.
+--
+-- Shape, for a reader with only the database in front of them:
+--
+--   {"windows":[{"days":[4],"from":"16:00","to":"20:00"}]}
+--
+--   * `days`  — Monday-first, 0..6. NOT `Date#getDay()`'s Sunday-first axis.
+--   * `from`/`to` — "HH:MM", 24-hour, in the STORE's timezone, half-open
+--     [from, to) exactly as [starts_at, ends_at) is.
+--   * `to` < `from` means the window runs past midnight (a bar shutting at
+--     02:00), which is the most common happy hour there is.
+
+ALTER TABLE "discounts" ADD COLUMN IF NOT EXISTS "schedule" JSONB;

package/prisma/plugin-migrations.json

@@ -36,6 +36,8 @@
     "20260820120000_add_user_feature_grants",
     "20260821120000_shift_kind_host_vocabulary",
     "20260821140000_discounts_package_owned",
-    "20260824120000_payments_pending_verification"
+    "20260824120000_payments_pending_verification",
+    "20260826170000_locale_preferences",
+    "20260830120000_discount_weekly_schedule"
   ]
 }

package/prisma/schema/discounts.prisma

@@ -79,6 +79,29 @@ model Discount {
   // either side = open-ended.
   startsAt             DateTime? @map("starts_at")
   endsAt               DateTime? @map("ends_at")
+  // The WEEKLY schedule INSIDE that window (FUT-996) — "toda sexta, das 16:00
+  // às 20:00", "segunda e terça à tarde". NULL = always, within
+  // [starts_at, ends_at), which is what every row predating the feature means.
+  //
+  //   {"windows":[{"days":[4],"from":"16:00","to":"20:00"}]}
+  //
+  // `days` is Monday-first 0..6 — the axis every hours surface uses, and NOT
+  // `Date#getDay()`'s Sunday-first one. `from`/`to` are "HH:MM" in the STORE's
+  // timezone, half-open [from, to) exactly as the campaign window is, and a
+  // `to` earlier than `from` runs past midnight rather than being invalid.
+  //
+  // JSON rather than a fourth table because the recurrence is not usefully
+  // SQL-queryable (the grid's vigência filter already cannot express the
+  // campaign window either), and a fourth table would put a third `include` on
+  // the storefront's hottest read. The cost is that the DATABASE cannot check
+  // this shape: `assertSchedule` is the only gate, and the evaluator treats a
+  // malformed window as covering NOTHING, so a bad blob is a promotion that
+  // does not fire rather than a cart priced wrong.
+  //
+  // A recurring window is a WALL-CLOCK fact, so it is only meaningful against
+  // the store's own timezone. The engine never reads one: a host resolves the
+  // instant into a weekday and a minute-of-day and passes those in.
+  schedule             Json?     @map("schedule")
   // Minimum PRE-DISCOUNT cart subtotal, in cents. Always compared against the
   // untouched subtotal, never a running total — which is what makes the result
   // independent of the order the discounts are applied in.

package/prisma/schema/i18n.prisma

@@ -0,0 +1,49 @@
+// ─────────────────────────────────────────────────────────────────────────────
+// OWNED BY @12-apps/i18n — the host's multi-file schema folder holds a COPY of
+// this file, written by the partials assembler from this package's `wiring.db`
+// declaration. Never edit the copy.
+//
+// COPIED, never symlinked (the entity-lifecycle doctrine): `npm pack` silently
+// drops symlinked entries, `turbo prune` dangles a link whose owner is not a
+// declared dependency, and Prisma silently SKIPS a symlinked migration
+// directory — a green deploy that applied no schema.
+//
+// Self-contained, the same rule `auth.prisma` states: the user reference is a
+// `user_id` String column with NO foreign key into any host table, so this
+// model works in a repo whose user table is called something else, is in
+// another database, or does not exist yet at migrate time.
+//
+// That constraint is why this is a TABLE rather than a `locale` column on the
+// host's `users` — which is exactly where it started, and where the first
+// implementation put it. A package cannot add a column to a table it does not
+// own, and a host should not have to hand-edit its own model to install a
+// language preference. The auth package learned this with the three credential
+// columns; this is the same lesson, not a new one.
+// ─────────────────────────────────────────────────────────────────────────────
+
+/// Which language one person reads, keyed by the host's user id as an OPAQUE
+/// scalar.
+///
+/// A row EXISTS only once somebody has chosen. That absence is the design, not
+/// an omission: "has not chosen" and "reads pt-BR" are different facts, and a
+/// row-per-user with a default would collapse them — which matters because a
+/// reader's own setting outranks the tenant's, so a default written here would
+/// beat a store language nobody had a chance to lose to.
+///
+/// Storing it at all is what lets a notice follow its READER. A browser's
+/// `localStorage` and cookie answer for a screen, where the reader is present;
+/// they answer nothing for a notification stored as rendered text, or a mail
+/// sent by a background job, because neither has that browser in the room.
+model LocalePreference {
+  /// The host's user id. No relation by design: a stale id simply matches no
+  /// row, which is the same answer a deleted user should produce.
+  userId    String   @id @map("user_id")
+  /// A canonical tag from this package's own list, validated on the way in AND
+  /// on the way out — a value written by an older release or a hand-run SQL fix
+  /// must not become the one thing in the system that never passed `matchLocale`.
+  locale    String
+  createdAt DateTime @default(now()) @map("created_at")
+  updatedAt DateTime @updatedAt @map("updated_at")
+
+  @@map("locale_preferences")
+}