@12-apps/prisma 4.0.0 → 5.0.0

package/dist/actor-context.js

@@ -27,7 +27,7 @@ const node_async_hooks_1 = require("node:async_hooks");
 // module) can't create a second store whose context is invisible to closures
 // captured against the first.
 const globalStore = globalThis;
-const store = () => (globalStore.__futurePayActorStore ??= new node_async_hooks_1.AsyncLocalStorage());
+const store = () => (globalStore.__12appsPrismaActorStore ??= new node_async_hooks_1.AsyncLocalStorage());
 /**
  * The REAL human behind `onBehalfOfUserId`, derived (never accepted) from the
  * stamp that declares the impersonation (FUT-458).

package/dist/index.js

@@ -182,25 +182,25 @@ const createPostgresClient = async () => {
  * module-load failure.
  */
 const getPrismaClient = async () => {
-    if (globalStore.__futurePayPrisma)
-        return globalStore.__futurePayPrisma;
-    if (globalStore.__futurePayPrismaInit)
-        return globalStore.__futurePayPrismaInit;
+    if (globalStore.__12appsPrisma)
+        return globalStore.__12appsPrisma;
+    if (globalStore.__12appsPrismaInit)
+        return globalStore.__12appsPrismaInit;
     const pglite = resolvePglite();
     const init = (pglite ? createPgliteClient(pglite.dataDir) : createPostgresClient())
         .then((client) => {
-        globalStore.__futurePayPrisma = client;
-        globalStore.__futurePayPrismaInit = undefined;
+        globalStore.__12appsPrisma = client;
+        globalStore.__12appsPrismaInit = undefined;
         return client;
     })
         .catch((error) => {
-        globalStore.__futurePayPrismaInit = undefined;
+        globalStore.__12appsPrismaInit = undefined;
         throw new Error(`Prisma client not available (${pglite ? 'PGlite' : 'PostgreSQL'} mode). ` +
             'Run "pnpm --filter @12-apps/prisma prisma generate" from the ' +
             'monorepo root, or "pnpm prisma generate" from packages/prisma. ' +
             `Cause: ${error instanceof Error ? error.message : String(error)}`, { cause: error });
     });
-    globalStore.__futurePayPrismaInit = init;
+    globalStore.__12appsPrismaInit = init;
     return init;
 };
 exports.getPrismaClient = getPrismaClient;
@@ -208,15 +208,15 @@ exports.getPrismaClient = getPrismaClient;
  * Set a custom Prisma client instance (for testing).
  */
 const setPrismaClient = (client) => {
-    globalStore.__futurePayPrisma = client;
-    globalStore.__futurePayPrismaInit = undefined;
+    globalStore.__12appsPrisma = client;
+    globalStore.__12appsPrismaInit = undefined;
 };
 exports.setPrismaClient = setPrismaClient;
 /**
  * Reset the Prisma client instance (for testing).
  */
 const resetPrismaClient = () => {
-    globalStore.__futurePayPrisma = undefined;
-    globalStore.__futurePayPrismaInit = undefined;
+    globalStore.__12appsPrisma = undefined;
+    globalStore.__12appsPrismaInit = undefined;
 };
 exports.resetPrismaClient = resetPrismaClient;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@12-apps/prisma",
-  "version": "4.0.0",
+  "version": "5.0.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",
@@ -59,20 +59,20 @@
     "pglite-prisma-adapter": "0.7.2"
   },
   "devDependencies": {
-    "@12-apps/audit": "^3.0.0",
-    "@12-apps/entitlements": "^2.0.0",
-    "@12-apps/entity-lifecycle": "^3.0.0",
+    "@12-apps/audit": "^4.0.0",
+    "@12-apps/entitlements": "^3.0.0",
+    "@12-apps/entity-lifecycle": "^4.0.0",
     "@12-apps/eslint-config": "^1.20.0",
-    "@12-apps/jobs": "^3.0.0",
-    "@12-apps/mcp": "^2.0.0",
-    "@12-apps/notifications": "^2.0.0",
-    "@12-apps/onboarding": "^1.20.0",
-    "@12-apps/payments-backend": "^3.0.0",
+    "@12-apps/jobs": "^4.0.0",
+    "@12-apps/mcp": "^3.0.0",
+    "@12-apps/notifications": "^4.0.0",
+    "@12-apps/onboarding": "^2.0.0",
+    "@12-apps/payments-backend": "^4.0.0",
     "@12-apps/product-research": "^2.0.0",
-    "@12-apps/rbac": "^3.0.0",
-    "@12-apps/realtime": "^1.19.0",
-    "@12-apps/report-builder": "^4.0.0",
-    "@12-apps/shift": "^2.0.0",
+    "@12-apps/rbac": "^4.0.0",
+    "@12-apps/realtime": "^2.0.0",
+    "@12-apps/report-builder": "^5.0.0",
+    "@12-apps/shift": "^3.0.0",
     "@12-apps/typescript-config": "^1.20.0",
     "@types/node": "^22.10.6",
     "@vitest/coverage-v8": "^3.2.4",

package/prisma/migrations/20260731210000_shift_delete_guard/migration.sql

@@ -5,7 +5,7 @@
 -- with no foreign key (that is what keeps the package host-agnostic), so a host
 -- that deletes its tenant row and then sweeps the remaining by-value tables by
 -- `client_id` could never remove a shift: the RAISE aborted the whole
--- transaction. Future Pay's demo-store reset does exactly that on EVERY deploy,
+-- transaction. The origin host's demo-store reset does exactly that on EVERY deploy,
 -- so a single shift row would have wedged the deploy step.
 --
 -- Deletability is host policy, not a package invariant. What the guard actually

package/prisma/migrations/20260812150000_add_mcp_oauth_tables/migration.sql

@@ -18,13 +18,13 @@
 -- Authorization codes are deliberately absent: they are STATELESS signed blobs,
 -- so there is no table to create and nothing to sweep.
 --
--- The columns, defaults, indexes and CHECK are future-pay's
+-- The columns, defaults, indexes and CHECK are the origin host's
 -- `20260713120000_add_oauth_client_refresh`,
 -- `20260715180000_add_onboarding_state_mcp_connection` (the mcp_connections half
 -- — the onboarding half belongs to @12-apps/onboarding) and
 -- `20260720120000_add_mcp_connection_host` verbatim, minus the FK to `users`:
 -- this package cannot know the name of a host's user table, and a host that has
--- one keeps its own constraint (future-pay's is ON DELETE CASCADE).
+-- one keeps its own constraint (the origin host's is ON DELETE CASCADE).
 --
 -- EVERY statement is guarded (`IF NOT EXISTS`, and a conrelid-scoped DO block for
 -- the CHECK, which has no IF NOT EXISTS form). That is what makes adoption by a
@@ -35,7 +35,7 @@
 -- the difference bites exactly the host this file is written for: `CREATE TABLE IF
 -- NOT EXISTS` skips the whole table, columns included, so a host holding an OLDER
 -- shape of one of these tables silently keeps it. Each table below is therefore
--- followed by a guarded `ADD COLUMN` for every column that reached future-pay in a
+-- followed by a guarded `ADD COLUMN` for every column that reached the origin host in a
 -- LATER migration than its own CREATE. The full audit: `oauth_refresh_tokens
 -- .user_sub` (`20260713150000_add_oauth_refresh_user_sub`) and `mcp_connections
 -- .host` (`20260720120000_add_mcp_connection_host`). `oauth_clients` needs none —
@@ -112,10 +112,10 @@ CREATE INDEX IF NOT EXISTS "oauth_refresh_tokens_user_email_client_id_idx"
 -- `CREATE TABLE IF NOT EXISTS` skips the WHOLE table, so a host that already holds
 -- `oauth_refresh_tokens` in an OLDER SHAPE gets none of the columns declared above
 -- — statement-level guarding is not the same as column-level guarding. That is
--- precisely how future-pay's own history ran: `user_sub` arrived in a SECOND
+-- precisely how the origin host's own history ran: `user_sub` arrived in a SECOND
 -- migration (FUT-105, `20260713150000_add_oauth_refresh_user_sub`), so a host
 -- frozen before it would adopt this file, skip the CREATE, never get the column,
--- and then fail on every refresh the package serves. Mirror future-pay's pair
+-- and then fail on every refresh the package serves. Mirror the origin host's pair
 -- verbatim — guarded add with a backfill default to satisfy NOT NULL, then drop
 -- the default so the column matches the Prisma schema (`String`, no default).
 -- Both statements are no-ops on a fresh host and on a replay.
@@ -147,6 +147,6 @@ CREATE INDEX IF NOT EXISTS "mcp_connections_last_active_at_idx"
   ON "mcp_connections"("last_active_at");
 
 -- A host adopting this migration where `mcp_connections` predates the `host`
--- column (future-pay added it in a later migration) gets it here; a fresh host
+-- column (the origin host added it in a later migration) gets it here; a fresh host
 -- already has it from the CREATE above, so the guard makes both cases a no-op.
 ALTER TABLE "mcp_connections" ADD COLUMN IF NOT EXISTS "host" TEXT;

package/prisma/migrations/20260812150000_add_onboarding_states/migration.sql

@@ -2,13 +2,13 @@
 -- the package and copied into a host's migrations folder by its
 -- plugin-migration sync.
 --
--- The columns, defaults, indexes and the status CHECK are future-pay's
+-- The columns, defaults, indexes and the status CHECK are the origin host's
 -- `20260715180000_add_onboarding_state_mcp_connection` verbatim, minus two
 -- things that are the HOST's vocabulary rather than the package's:
 --
 --   * the FKs to `users` / `clients` — this package cannot know the name of a
 --     host's user or tenant table. A host that has them keeps its own
---     constraints (future-pay's are ON DELETE CASCADE) and they stay
+--     constraints (the origin host's are ON DELETE CASCADE) and they stay
 --     compatible with everything the package writes;
 --   * the `mcp_connections` half of that migration, which belongs to
 --     @12-apps/mcp and ships in ITS folder.
@@ -16,7 +16,7 @@
 -- EVERY statement is guarded (`IF NOT EXISTS`, and a conrelid-scoped DO block
 -- for the CHECK, which has no IF NOT EXISTS form). That is what makes adoption
 -- by a host that ALREADY has the table a no-op instead of a failed deploy —
--- future-pay applies this and nothing changes, no `prisma migrate resolve`
+-- the origin host applies this and nothing changes, no `prisma migrate resolve`
 -- dance required. It is also what lets the PGlite provisioner replay it into an
 -- existing schema, which is how the harness and the integration suites run.
 

package/prisma/migrations/20260813140000_add_notification_tables/migration.sql

@@ -24,7 +24,7 @@
 --
 -- ============================ REPLAY SAFETY ================================
 -- Every statement is guarded, because the first adopters ALREADY HAVE these
--- tables: future-pay created them by hand before the package existed, so this
+-- tables: the origin host created them by hand before the package existed, so this
 -- migration must be a no-op there and correct on an empty database.
 --
 -- The guards are per COLUMN, not per table. `CREATE TABLE IF NOT EXISTS` alone

package/prisma/schema/mcp.prisma

@@ -11,7 +11,7 @@
 //
 // Host-agnostic by design (the entity-lifecycle / rbac doctrine): `user_id` is a
 // by-value scalar with NO relation, because this package cannot know the name of
-// the host's user model. The host's own migration may add the FK (future-pay's
+// the host's user model. The host's own migration may add the FK (the origin host's
 // is ON DELETE CASCADE). Note there is deliberately no `oauth_codes` table:
 // authorization codes are STATELESS signed blobs, so there is nothing to store
 // and nothing to sweep.

package/prisma/schema/notifications.prisma

@@ -22,7 +22,7 @@
 // and for a stronger reason: the category set is HOST vocabulary (`categories`
 // on the server config), so a closed set in the schema would be wrong for every
 // adopter but the first. A host that wants its own taxonomy enforced adds the
-// CHECK in a migration of its own — future-pay does. Only `channel` and `status`
+// CHECK in a migration of its own — the origin host does. Only `channel` and `status`
 // on the delivery row are closed here, because those two are the LIBRARY's.
 model Notification {
   id        String    @id @default(uuid())

package/prisma/schema/onboarding.prisma

@@ -12,7 +12,7 @@
 // Host-agnostic by design (the entity-lifecycle / report-builder doctrine):
 //   - `user_id` and `client_id` are by-value scalars, NOT relations — this
 //     package cannot know the name of the host's user or tenant model. The
-//     host's own migration may add the FK constraints (future-pay has both,
+//     host's own migration may add the FK constraints (the origin host has both,
 //     ON DELETE CASCADE).
 //   - `status` is a String with a DB CHECK rather than a Prisma enum (the
 //     house String+CHECK pattern); the four values are the package's own

package/src/actor-context.ts

@@ -93,11 +93,11 @@ export interface ActorContext extends ActorAttributionSnapshot {
 // module) can't create a second store whose context is invisible to closures
 // captured against the first.
 const globalStore = globalThis as unknown as {
-  __futurePayActorStore?: AsyncLocalStorage<ActorContext>;
+  __12appsPrismaActorStore?: AsyncLocalStorage<ActorContext>;
 };
 
 const store = (): AsyncLocalStorage<ActorContext> =>
-  (globalStore.__futurePayActorStore ??= new AsyncLocalStorage<ActorContext>());
+  (globalStore.__12appsPrismaActorStore ??= new AsyncLocalStorage<ActorContext>());
 
 /**
  * The REAL human behind `onBehalfOfUserId`, derived (never accepted) from the

package/src/index.ts

@@ -63,8 +63,8 @@ export { normalizeSearchText } from './search-normalize';
 // a second PGlite instance against the same dataDir — PGlite holds a single
 // exclusive connection, and a duplicate would deadlock or corrupt the store.
 const globalStore = globalThis as unknown as {
-  __futurePayPrisma?: PrismaClient;
-  __futurePayPrismaInit?: Promise<PrismaClient>;
+  __12appsPrisma?: PrismaClient;
+  __12appsPrismaInit?: Promise<PrismaClient>;
 };
 
 /**
@@ -196,20 +196,20 @@ const createPostgresClient = async (): Promise<PrismaClient> => {
  * module-load failure.
  */
 export const getPrismaClient = async (): Promise<PrismaClient> => {
-  if (globalStore.__futurePayPrisma) return globalStore.__futurePayPrisma;
-  if (globalStore.__futurePayPrismaInit) return globalStore.__futurePayPrismaInit;
+  if (globalStore.__12appsPrisma) return globalStore.__12appsPrisma;
+  if (globalStore.__12appsPrismaInit) return globalStore.__12appsPrismaInit;
 
   const pglite = resolvePglite();
   const init = (
     pglite ? createPgliteClient(pglite.dataDir) : createPostgresClient()
   )
     .then((client) => {
-      globalStore.__futurePayPrisma = client;
-      globalStore.__futurePayPrismaInit = undefined;
+      globalStore.__12appsPrisma = client;
+      globalStore.__12appsPrismaInit = undefined;
       return client;
     })
     .catch((error: unknown) => {
-      globalStore.__futurePayPrismaInit = undefined;
+      globalStore.__12appsPrismaInit = undefined;
       throw new Error(
         `Prisma client not available (${pglite ? 'PGlite' : 'PostgreSQL'} mode). ` +
           'Run "pnpm --filter @12-apps/prisma prisma generate" from the ' +
@@ -219,7 +219,7 @@ export const getPrismaClient = async (): Promise<PrismaClient> => {
       );
     });
 
-  globalStore.__futurePayPrismaInit = init;
+  globalStore.__12appsPrismaInit = init;
   return init;
 };
 
@@ -227,14 +227,14 @@ export const getPrismaClient = async (): Promise<PrismaClient> => {
  * Set a custom Prisma client instance (for testing).
  */
 export const setPrismaClient = (client: PrismaClient): void => {
-  globalStore.__futurePayPrisma = client;
-  globalStore.__futurePayPrismaInit = undefined;
+  globalStore.__12appsPrisma = client;
+  globalStore.__12appsPrismaInit = undefined;
 };
 
 /**
  * Reset the Prisma client instance (for testing).
  */
 export const resetPrismaClient = (): void => {
-  globalStore.__futurePayPrisma = undefined;
-  globalStore.__futurePayPrismaInit = undefined;
+  globalStore.__12appsPrisma = undefined;
+  globalStore.__12appsPrismaInit = undefined;
 };