@prisma/orm-toolchain 8.0.0-rc.1-dev.45 → 8.0.0-rc.10

package/dist/{output-DP3woAjV-BxCr9nHA.mjs → output-D83nTTpC-XlvN30yS.mjs}

@@ -1,5 +1,5 @@
 import { type } from "arktype";
-//#region ../../../1-framework/3-tooling/cli/dist/output-DP3woAjV.mjs
+//#region ../../../1-framework/3-tooling/cli/dist/output-D83nTTpC.mjs
 /**
 * arktype schema for the structured success document `init --json` writes
 * to stdout (FR1.5). The same shape backs the human-readable outro
@@ -44,48 +44,6 @@ const InitOutputSchema = type({
 	warnings: "string[]"
 });
 /**
-* Serialises the output document for `--json`. Sorted keys are not enforced
-* — `JSON.stringify` preserves insertion order, and the schema field order
-* is the documented order, which matches what users will see when they
-* `jq .` the result.
-*/
-function formatInitJson(output) {
-	return JSON.stringify(output, null, 2);
-}
-/**
-* Renders the human-readable outro on stderr (FR10.1). Re-uses the same
-* data structure as the JSON output so the two stay in lock-step.
-*
-* Warnings come before "Next steps" because they describe state the user
-* needs to be aware of before acting on the next-steps list.
-*/
-function renderInitOutro(ui, output, flags) {
-	if (flags.quiet || flags.json) return;
-	for (const warning of output.warnings) ui.warn(warning);
-	const lines = [];
-	lines.push(`Target:    ${output.target}`);
-	lines.push(`Authoring: ${output.authoring}`);
-	lines.push(`Schema:    ${output.schemaPath}`);
-	lines.push("");
-	lines.push("Files written:");
-	for (const file of output.filesWritten) lines.push(`  • ${file}`);
-	if (output.filesDeleted.length > 0) {
-		lines.push("");
-		lines.push("Removed (stale artifacts and retired skill directories):");
-		for (const file of output.filesDeleted) lines.push(`  • ${file}`);
-	}
-	if (output.packagesInstalled.status === "installed") {
-		lines.push("");
-		lines.push("Packages installed:");
-		for (const dep of output.packagesInstalled.deps) lines.push(`  • ${dep}`);
-		for (const dep of output.packagesInstalled.devDeps) lines.push(`  • ${dep} (dev)`);
-	}
-	lines.push("");
-	lines.push("Next steps:");
-	for (const step of output.nextSteps) lines.push(`  ${step}`);
-	ui.note(lines.join("\n"), "Done");
-}
-/**
 * Builds the `nextSteps` array from the resolved scaffold state. Steps are
 * ordered by the workflow a user needs to follow: install what is missing →
 * configure connection → (emit if not yet done) → run a starter query →
@@ -109,11 +67,11 @@ function buildNextSteps(options) {
 		push(`Emit the contract: \`${options.emitCommand}\``);
 		push(`Edit your schema at ${options.schemaPath}, then re-run the emit command.`);
 	} else push(`Edit your schema at ${options.schemaPath}, then re-run \`${options.emitCommand}\`.`);
-	push("Open prisma-next.md for a quick reference on how to write your first typed query.");
-	if (options.skillRegistered) push("Prisma Next skills are registered with your agent runtime — open the project in your IDE and ask the agent to add a model, run a query, or plan a migration.");
+	push("Open prisma-8.md for a quick reference on how to write your first typed query.");
+	push("Working with a coding agent? Run `prisma init` in this project to set up the Prisma agent skills.");
 	return steps;
 }
 //#endregion
-export { renderInitOutro as i, buildNextSteps as n, formatInitJson as r, InitOutputSchema as t };
+export { buildNextSteps as n, InitOutputSchema as t };
 
-//# sourceMappingURL=output-DP3woAjV-BxCr9nHA.mjs.map
+//# sourceMappingURL=output-D83nTTpC-XlvN30yS.mjs.map

package/dist/output-D83nTTpC-XlvN30yS.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"output-D83nTTpC-XlvN30yS.mjs","names":[],"sources":["../../../../1-framework/3-tooling/cli/dist/output-D83nTTpC.mjs"],"sourcesContent":["import { type } from \"arktype\";\n//#region src/commands/init/output.ts\n/**\n* arktype schema for the structured success document `init --json` writes\n* to stdout (FR1.5). The same shape backs the human-readable outro\n* renderer (FR10), so the two output modes carry identical information.\n*\n* `target` is normalised to the user-facing flag value (`mongodb` rather\n* than the internal `mongo`) so consumers can round-trip the document\n* straight into a follow-up `--target` invocation.\n*\n* The `ok: true` literal is the documented success/error discriminator —\n* see [Style Guide § JSON Semantics](../../../../../../../docs/CLI%20Style%20Guide.md#json-semantics).\n* Error envelopes (`CliErrorEnvelope`) carry `ok: false` so consumers can\n* branch with `if (doc.ok)` without inspecting the rest of the structure.\n*/\nconst InitOutputSchema = type({\n\tok: \"true\",\n\ttarget: \"'postgres'|'mongodb'\",\n\tauthoring: \"'psl'|'typescript'\",\n\tschemaPath: \"string\",\n\tfilesWritten: \"string[]\",\n\t/**\n\t* FR9.1 — paths removed from disk during this run: contract artifacts\n\t* (`contract.json`, `contract.d.ts`, `ops.json`, `migration.json`) an\n\t* earlier run left behind, which only a re-init has, and the retired\n\t* agent-skill directories, which every run removes when it finds them.\n\t*/\n\tfilesDeleted: \"string[]\",\n\t/**\n\t* What became of the dependency install. `skipped` is the deliberate\n\t* `--skip-install`; `failed` is an install that ran and did not succeed,\n\t* which leaves a scaffolded project that cannot run yet. `deps` and\n\t* `devDeps` list what was installed, so both non-`installed` states\n\t* carry them empty.\n\t*/\n\tpackagesInstalled: {\n\t\tstatus: \"'installed'|'skipped'|'failed'\",\n\t\tdeps: \"string[]\",\n\t\tdevDeps: \"string[]\"\n\t},\n\tcontractEmitted: \"boolean\",\n\tnextSteps: \"string[]\",\n\twarnings: \"string[]\"\n});\n/**\n* Builds the `nextSteps` array from the resolved scaffold state. Steps are\n* ordered by the workflow a user needs to follow: install what is missing →\n* configure connection → (emit if not yet done) → run a starter query →\n* docs / agent skill.\n*\n* The strings are stable and human-readable; agents wanting to act on them\n* should match on substrings (e.g. \"DATABASE_URL\") rather than exact text,\n* since copy may evolve.\n*/\nfunction buildNextSteps(options) {\n\tconst steps = [];\n\tlet stepNumber = 1;\n\tconst push = (text) => {\n\t\tsteps.push(`${stepNumber}. ${text}`);\n\t\tstepNumber += 1;\n\t};\n\tif (options.packagesInstalled === \"failed\") push(\"Install the project dependencies with your package manager — the install this run attempted failed, so nothing else here will work yet.\");\n\tif (options.packagesInstalled === \"skipped\") push(\"Install the project dependencies with your package manager (this run skipped them).\");\n\tpush(\"Set DATABASE_URL in your environment (export it or add it to .env).\");\n\tif (!options.contractEmitted) {\n\t\tpush(`Emit the contract: \\`${options.emitCommand}\\``);\n\t\tpush(`Edit your schema at ${options.schemaPath}, then re-run the emit command.`);\n\t} else push(`Edit your schema at ${options.schemaPath}, then re-run \\`${options.emitCommand}\\`.`);\n\tpush(\"Open prisma-8.md for a quick reference on how to write your first typed query.\");\n\tpush(\"Working with a coding agent? Run `prisma init` in this project to set up the Prisma agent skills.\");\n\treturn steps;\n}\n//#endregion\nexport { buildNextSteps as n, InitOutputSchema as t };\n\n//# sourceMappingURL=output-D83nTTpC.mjs.map"],"mappings":";;;;;;;;;;;;;;;;AAgBA,MAAM,mBAAmB,KAAK;CAC7B,IAAI;CACJ,QAAQ;CACR,WAAW;CACX,YAAY;CACZ,cAAc;;;;;;;CAOd,cAAc;;;;;;;;CAQd,mBAAmB;EAClB,QAAQ;EACR,MAAM;EACN,SAAS;CACV;CACA,iBAAiB;CACjB,WAAW;CACX,UAAU;AACX,CAAC;;;;;;;;;;;AAWD,SAAS,eAAe,SAAS;CAChC,MAAM,QAAQ,CAAC;CACf,IAAI,aAAa;CACjB,MAAM,QAAQ,SAAS;EACtB,MAAM,KAAK,GAAG,WAAW,IAAI,MAAM;EACnC,cAAc;CACf;CACA,IAAI,QAAQ,sBAAsB,UAAU,KAAK,yIAAyI;CAC1L,IAAI,QAAQ,sBAAsB,WAAW,KAAK,qFAAqF;CACvI,KAAK,qEAAqE;CAC1E,IAAI,CAAC,QAAQ,iBAAiB;EAC7B,KAAK,wBAAwB,QAAQ,YAAY,GAAG;EACpD,KAAK,uBAAuB,QAAQ,WAAW,gCAAgC;CAChF,OAAO,KAAK,uBAAuB,QAAQ,WAAW,kBAAkB,QAAQ,YAAY,IAAI;CAChG,KAAK,gFAAgF;CACrF,KAAK,mGAAmG;CACxG,OAAO;AACR"}

package/dist/publish-surface.d.mts

@@ -1,3 +1,3 @@
-import { a as ShellReexportMapping, i as ShellPackageMapping, n as ShellKind, o as excludedSubpaths, r as ShellName, s as publicShells, t as ShellDefinition } from "./shells-COHV_Ozf.mjs";
-import { a as ScaffoldImportRoot, c as createScaffoldSpecifierResolver, d as importedSpecifiers, f as internalImportRoot, h as transitiveImports, i as ImportSpecifierResolver, l as directDependencyShells, m as resolveImportSpecifier, n as ImportRootError, o as buildOwnerIndex, p as platformEntrypointOf, r as ImportRootMode, s as createImportSpecifierResolver, t as ImportRoot, u as importRootForDependencies } from "./import-roots-B6CtsWXb.mjs";
+import { a as ShellReexportMapping, i as ShellPackageMapping, n as ShellKind, o as excludedSubpaths, r as ShellName, s as publicShells, t as ShellDefinition } from "./shells-CIUmT4u4.mjs";
+import { a as ScaffoldImportRoot, c as createScaffoldSpecifierResolver, d as importedSpecifiers, f as internalImportRoot, h as transitiveImports, i as ImportSpecifierResolver, l as directDependencyShells, m as resolveImportSpecifier, n as ImportRootError, o as buildOwnerIndex, p as platformEntrypointOf, r as ImportRootMode, s as createImportSpecifierResolver, t as ImportRoot, u as importRootForDependencies } from "./import-roots-ARK1wjzc.mjs";
 export { ImportRoot, ImportRootError, ImportRootMode, ImportSpecifierResolver, ScaffoldImportRoot, ShellDefinition, ShellKind, ShellName, ShellPackageMapping, ShellReexportMapping, buildOwnerIndex, createImportSpecifierResolver, createScaffoldSpecifierResolver, directDependencyShells, excludedSubpaths, importRootForDependencies, importedSpecifiers, internalImportRoot, platformEntrypointOf, publicShells, resolveImportSpecifier, transitiveImports };

package/dist/publish-surface.mjs

@@ -1,3 +1,3 @@
-import { n as publicShells, t as excludedSubpaths } from "./shells-BenrJHp2.mjs";
-import { a as directDependencyShells, c as internalImportRoot, d as transitiveImports, i as createScaffoldSpecifierResolver, l as platformEntrypointOf, n as buildOwnerIndex, o as importRootForDependencies, r as createImportSpecifierResolver, s as importedSpecifiers, t as ImportRootError, u as resolveImportSpecifier } from "./import-roots-NDOIEDVj.mjs";
+import { n as publicShells, t as excludedSubpaths } from "./shells-BIdFZwUY.mjs";
+import { a as directDependencyShells, c as internalImportRoot, d as transitiveImports, i as createScaffoldSpecifierResolver, l as platformEntrypointOf, n as buildOwnerIndex, o as importRootForDependencies, r as createImportSpecifierResolver, s as importedSpecifiers, t as ImportRootError, u as resolveImportSpecifier } from "./import-roots-BHOrDJbI.mjs";
 export { ImportRootError, buildOwnerIndex, createImportSpecifierResolver, createScaffoldSpecifierResolver, directDependencyShells, excludedSubpaths, importRootForDependencies, importedSpecifiers, internalImportRoot, platformEntrypointOf, publicShells, resolveImportSpecifier, transitiveImports };

package/dist/publish-surface__import-roots.d.mts

@@ -1,2 +1,2 @@
-import { a as ScaffoldImportRoot, c as createScaffoldSpecifierResolver, d as importedSpecifiers, f as internalImportRoot, h as transitiveImports, i as ImportSpecifierResolver, l as directDependencyShells, m as resolveImportSpecifier, n as ImportRootError, o as buildOwnerIndex, p as platformEntrypointOf, r as ImportRootMode, s as createImportSpecifierResolver, t as ImportRoot, u as importRootForDependencies } from "./import-roots-B6CtsWXb.mjs";
+import { a as ScaffoldImportRoot, c as createScaffoldSpecifierResolver, d as importedSpecifiers, f as internalImportRoot, h as transitiveImports, i as ImportSpecifierResolver, l as directDependencyShells, m as resolveImportSpecifier, n as ImportRootError, o as buildOwnerIndex, p as platformEntrypointOf, r as ImportRootMode, s as createImportSpecifierResolver, t as ImportRoot, u as importRootForDependencies } from "./import-roots-ARK1wjzc.mjs";
 export { ImportRoot, ImportRootError, ImportRootMode, ImportSpecifierResolver, ScaffoldImportRoot, buildOwnerIndex, createImportSpecifierResolver, createScaffoldSpecifierResolver, directDependencyShells, importRootForDependencies, importedSpecifiers, internalImportRoot, platformEntrypointOf, resolveImportSpecifier, transitiveImports };

package/dist/publish-surface__import-roots.mjs

@@ -1,2 +1,2 @@
-import { a as directDependencyShells, c as internalImportRoot, d as transitiveImports, i as createScaffoldSpecifierResolver, l as platformEntrypointOf, n as buildOwnerIndex, o as importRootForDependencies, r as createImportSpecifierResolver, s as importedSpecifiers, t as ImportRootError, u as resolveImportSpecifier } from "./import-roots-NDOIEDVj.mjs";
+import { a as directDependencyShells, c as internalImportRoot, d as transitiveImports, i as createScaffoldSpecifierResolver, l as platformEntrypointOf, n as buildOwnerIndex, o as importRootForDependencies, r as createImportSpecifierResolver, s as importedSpecifiers, t as ImportRootError, u as resolveImportSpecifier } from "./import-roots-BHOrDJbI.mjs";
 export { ImportRootError, buildOwnerIndex, createImportSpecifierResolver, createScaffoldSpecifierResolver, directDependencyShells, importRootForDependencies, importedSpecifiers, internalImportRoot, platformEntrypointOf, resolveImportSpecifier, transitiveImports };

package/dist/publish-surface__shells.d.mts

@@ -1,2 +1,2 @@
-import { a as ShellReexportMapping, i as ShellPackageMapping, n as ShellKind, o as excludedSubpaths, r as ShellName, s as publicShells, t as ShellDefinition } from "./shells-COHV_Ozf.mjs";
+import { a as ShellReexportMapping, i as ShellPackageMapping, n as ShellKind, o as excludedSubpaths, r as ShellName, s as publicShells, t as ShellDefinition } from "./shells-CIUmT4u4.mjs";
 export { ShellDefinition, ShellKind, ShellName, ShellPackageMapping, ShellReexportMapping, excludedSubpaths, publicShells };

package/dist/publish-surface__shells.mjs

@@ -1,2 +1,2 @@
-import { n as publicShells, t as excludedSubpaths } from "./shells-BenrJHp2.mjs";
+import { n as publicShells, t as excludedSubpaths } from "./shells-BIdFZwUY.mjs";
 export { excludedSubpaths, publicShells };

package/dist/quick-reference-mongo.md

@@ -1,8 +1,8 @@
-# Welcome to Prisma Next!
+# Welcome to Prisma ORM!
 
-Prisma Next lets you query your database in simple, easy-to-read TypeScript. Define what your data looks like, and Prisma Next gives you a fully typed client — with autocomplete for every collection, field, and relation.
+Prisma ORM lets you query your database in simple, easy-to-read TypeScript. Define what your data looks like, and Prisma ORM gives you a fully typed client — with autocomplete for every collection, field, and relation.
 
-This project is set up for MongoDB. Prisma Next also supports other databases.
+This project is set up for MongoDB. Prisma ORM also supports other databases.
 
 {{requirements}}
 
@@ -34,21 +34,24 @@ Your contract has two companion files in the same directory:
 
 Commit both files to git. When you change your contract, run `{{pkgRun}} contract emit` to update them.
 
-If you use a framework like Next.js or Vite, the Prisma Next plugin will do this for you automatically.
+If you use a framework like Next.js or Vite, the Prisma ORM plugin will do this for you automatically.
 
 ## Configuration
 
-[`prisma-next.config.ts`](prisma-next.config.ts) tells the CLI where your contract lives and how to connect to your database. It loads environment variables from `.env` automatically:
+[`prisma.config.ts`](prisma.config.ts) tells the CLI where your contract lives and how to connect to your database. It loads environment variables from `.env` automatically:
 
 ```typescript
 import 'dotenv/config';
-import { defineConfig } from '{{configEntrypoint}}';
-
-export default defineConfig({
-  contract: './{{schemaPath}}',
-  db: {
-    connection: process.env['DATABASE_URL']!,
-  },
+import { definePrismaConfig } from '@prisma/cli-engine';
+import { defineConfig as ormConfig } from '{{configEntrypoint}}';
+
+export default definePrismaConfig({
+  orm: ormConfig({
+    contract: './{{schemaPath}}',
+    db: {
+      connection: process.env['DATABASE_URL']!,
+    },
+  }),
 });
 ```
 
@@ -75,7 +78,7 @@ You can customize how your environment variables are loaded by changing or remov
 | File | Purpose |
 |---|---|
 | [`{{schemaPath}}`]({{schemaPath}}) | Your data contract — define your models here |
-| [`prisma-next.config.ts`](prisma-next.config.ts) | CLI configuration |
+| [`prisma.config.ts`](prisma.config.ts) | CLI configuration |
 | [`{{schemaDir}}/db.ts`]({{schemaDir}}/db.ts) | Database client — `import { db } from '{{dbImportPath}}'` |
 | `{{schemaDir}}/contract.json` | Compiled contract (generated) |
 | `{{schemaDir}}/contract.d.ts` | Contract types (generated) |
@@ -94,14 +97,14 @@ Multi-document transactions and change streams require MongoDB to run as a **rep
 - **`mongodb-memory-server`:** use `MongoMemoryReplSet` instead of `MongoMemoryServer` in tests.
 - **MongoDB Atlas:** every Atlas cluster is already a replica set.
 
-The transaction API (`db.transaction(...)`) is on the roadmap and tracked under [TML-2313](https://linear.app/prisma-company/issue/TML-2313/mongo-dev-replica-set-story-is-missing-transactions-change-streams). Prisma Next's Mongo facade does not expose it yet — until that ticket lands, drive transactions yourself with a raw `MongoClient` using the escape hatch in the next section.
+The transaction API (`db.transaction(...)`) is on the roadmap and tracked under [TML-2313](https://linear.app/prisma-company/issue/TML-2313/mongo-dev-replica-set-story-is-missing-transactions-change-streams). Prisma ORM's Mongo facade does not expose it yet — until that ticket lands, drive transactions yourself with a raw `MongoClient` using the escape hatch in the next section.
 
 ## Escape hatches
 
 The ORM covers the common cases. For the rest, two escape hatches are designed in:
 
 - **Typed raw aggregations — `db.query`.** The facade exposes `db.query`, a typed builder for aggregation pipelines that runs through the same runtime + middleware + codec stack as `db.orm`. Reach for it when the ORM can't express a `$lookup`/`$facet`/`$graphLookup`/window-function pipeline.
-- **Direct `mongodb` driver control — `mongoClient` binding.** Construct your own `MongoClient` and pass it to `mongo({ mongoClient, dbName, contractJson })`. Your code keeps the `MongoClient` reference and uses it directly (transactions, change streams, sessions, anything Prisma Next doesn't surface yet); the same `db` object continues to give you the typed ORM.
+- **Direct `mongodb` driver control — `mongoClient` binding.** Construct your own `MongoClient` and pass it to `mongo({ mongoClient, dbName, contractJson })`. Your code keeps the `MongoClient` reference and uses it directly (transactions, change streams, sessions, anything Prisma ORM doesn't surface yet); the same `db` object continues to give you the typed ORM.
 
 `db.runtime()` is **not** the escape hatch — it returns the internal executor (`MongoRuntime`), not a `mongodb` `MongoClient` or `Db`. Use `db.query` for raw aggregations and the `mongoClient` binding for direct driver control.
 
@@ -109,6 +112,6 @@ The ORM covers the common cases. For the rest, two escape hatches are designed i
 
 If this project lives inside a pnpm workspace, a few things are worth knowing:
 
-- **Catalogs.** When the workspace's `pnpm-workspace.yaml` defines a `catalogs` entry for `prisma-next` or `{{pkg}}`, pnpm uses the catalog version everywhere — `init` does too. If you wanted the published `latest` instead, update or remove the catalog entry, then re-run `pnpm install`.
-- **`pnpm dlx`.** `pnpm dlx prisma-next@latest init …` works in any directory. Inside a workspace, pnpm still resolves dependencies through the workspace's catalog/overrides rather than the registry; expect the installed Prisma Next packages to reflect the workspace's catalog rather than `latest`.
-- **`pnpm` → `npm` fallback.** If `pnpm` ever fails to install Prisma Next with a `workspace:*` or `catalog:` resolution error (a leak in a published artefact), `init` falls back to `npm install` and surfaces a warning. Once the offending package republishes a clean version you can switch back with `pnpm install`.
+- **Catalogs.** When the workspace's `pnpm-workspace.yaml` defines a `catalogs` entry for `prisma` or `{{pkg}}`, pnpm uses the catalog version everywhere — `init` does too. If you wanted the published `latest` instead, update or remove the catalog entry, then re-run `pnpm install`.
+- **`pnpm dlx`.** `pnpm dlx prisma@latest orm init …` works in any directory. Inside a workspace, pnpm still resolves dependencies through the workspace's catalog/overrides rather than the registry; expect the installed Prisma ORM packages to reflect the workspace's catalog rather than `latest`.
+- **`pnpm` → `npm` fallback.** If `pnpm` ever fails to install Prisma ORM with a `workspace:*` or `catalog:` resolution error (a leak in a published artefact), `init` falls back to `npm install` and surfaces a warning. Once the offending package republishes a clean version you can switch back with `pnpm install`.

package/dist/quick-reference-postgres.md

@@ -1,8 +1,8 @@
-# Welcome to Prisma Next!
+# Welcome to Prisma ORM!
 
-Prisma Next lets you query your database in simple, easy-to-read TypeScript. Define what your data looks like, and Prisma Next gives you a fully typed client — with autocomplete for every table, column, and relation.
+Prisma ORM lets you query your database in simple, easy-to-read TypeScript. Define what your data looks like, and Prisma ORM gives you a fully typed client — with autocomplete for every table, column, and relation.
 
-This project is set up for PostgreSQL. Prisma Next also supports other databases.
+This project is set up for PostgreSQL. Prisma ORM also supports other databases.
 
 {{requirements}}
 
@@ -17,7 +17,7 @@ Every model you define in your contract can be queried from your app. Your edito
 ```typescript
 import { db } from '{{dbImportPath}}';
 
-const user = await db.orm.User
+const user = await db.orm.public.User
   .where({ email: 'alice@example.com' })
   .first();
 
@@ -32,21 +32,24 @@ Your contract has two companion files in the same directory:
 
 Commit both files to git. When you change your contract, run `{{pkgRun}} contract emit` to update them.
 
-If you use a framework like Next.js or Vite, the Prisma Next plugin will do this for you automatically.
+If you use a framework like Next.js or Vite, the Prisma ORM plugin will do this for you automatically.
 
 ## Configuration
 
-[`prisma-next.config.ts`](prisma-next.config.ts) tells the CLI where your contract lives and how to connect to your database. It loads environment variables from `.env` automatically:
+[`prisma.config.ts`](prisma.config.ts) tells the CLI where your contract lives and how to connect to your database. It loads environment variables from `.env` automatically:
 
 ```typescript
 import 'dotenv/config';
-import { defineConfig } from '{{configEntrypoint}}';
-
-export default defineConfig({
-  contract: './{{schemaPath}}',
-  db: {
-    connection: process.env['DATABASE_URL']!,
-  },
+import { definePrismaConfig } from '@prisma/cli-engine';
+import { defineConfig as ormConfig } from '{{configEntrypoint}}';
+
+export default definePrismaConfig({
+  orm: ormConfig({
+    contract: './{{schemaPath}}',
+    db: {
+      connection: process.env['DATABASE_URL']!,
+    },
+  }),
 });
 ```
 
@@ -73,7 +76,7 @@ You can customize how your environment variables are loaded by changing or remov
 | File | Purpose |
 |---|---|
 | [`{{schemaPath}}`]({{schemaPath}}) | Your data contract — define your models here |
-| [`prisma-next.config.ts`](prisma-next.config.ts) | CLI configuration |
+| [`prisma.config.ts`](prisma.config.ts) | CLI configuration |
 | [`{{schemaDir}}/db.ts`]({{schemaDir}}/db.ts) | Database client — `import { db } from '{{dbImportPath}}'` |
 | `{{schemaDir}}/contract.json` | Compiled contract (generated) |
 | `{{schemaDir}}/contract.d.ts` | Contract types (generated) |
@@ -88,6 +91,6 @@ You can customize how your environment variables are loaded by changing or remov
 
 If this project lives inside a pnpm workspace, a few things are worth knowing:
 
-- **Catalogs.** When the workspace's `pnpm-workspace.yaml` defines a `catalogs` entry for `prisma-next` or `{{pkg}}`, pnpm uses the catalog version everywhere — `init` does too. If you wanted the published `latest` instead, update or remove the catalog entry, then re-run `pnpm install`.
-- **`pnpm dlx`.** `pnpm dlx prisma-next@latest init …` works in any directory. Inside a workspace, pnpm still resolves dependencies through the workspace's catalog/overrides rather than the registry; expect the installed Prisma Next packages to reflect the workspace's catalog rather than `latest`.
-- **`pnpm` → `npm` fallback.** If `pnpm` ever fails to install Prisma Next with a `workspace:*` or `catalog:` resolution error (a leak in a published artefact), `init` falls back to `npm install` and surfaces a warning. Once the offending package republishes a clean version you can switch back with `pnpm install`.
+- **Catalogs.** When the workspace's `pnpm-workspace.yaml` defines a `catalogs` entry for `prisma` or `{{pkg}}`, pnpm uses the catalog version everywhere — `init` does too. If you wanted the published `latest` instead, update or remove the catalog entry, then re-run `pnpm install`.
+- **`pnpm dlx`.** `pnpm dlx prisma@latest orm init …` works in any directory. Inside a workspace, pnpm still resolves dependencies through the workspace's catalog/overrides rather than the registry; expect the installed Prisma ORM packages to reflect the workspace's catalog rather than `latest`.
+- **`pnpm` → `npm` fallback.** If `pnpm` ever fails to install Prisma ORM with a `workspace:*` or `catalog:` resolution error (a leak in a published artefact), `init` falls back to `npm install` and surfaces a warning. Once the offending package republishes a clean version you can switch back with `pnpm install`.

package/dist/readme-mongo.md

@@ -1,6 +1,6 @@
 # {{projectName}}
 
-Generated by `prisma-next init` with the Minimal template.
+Generated by `prisma orm init` with the Minimal template.
 
 ## First run
 
@@ -9,7 +9,7 @@ Generated by `prisma-next init` with the Minimal template.
 
 ## Available scripts
 
-- `{{runDev}}` — run the Prisma Next sample script
+- `{{runDev}}` — run the Prisma ORM sample script
 
 ### Database and migrations
 
@@ -21,15 +21,15 @@ Generated by `prisma-next init` with the Minimal template.
 - `{{runMigrate}}` — apply the planned MongoDB migration
 - `{{runDbSeed}}` — insert sample users manually
 
-## Prisma Next
+## Prisma ORM
 
-Prisma Next setup is scaffolded in:
+Prisma ORM setup is scaffolded in:
 
 - `{{contractPath}}`
-- `prisma-next.config.ts`
+- `prisma.config.ts`
 - `prisma/db.ts`
 - `src/lib/prisma.ts`
 
-For provider-specific Prisma Next reference docs, see `prisma-next.md`. Prisma Next skills live in the upstream `skills/` directory: https://github.com/prisma/prisma/tree/main/skills.
+For provider-specific Prisma ORM reference docs, see `prisma-8.md`. Prisma ORM skills live in the upstream `skills/` directory: https://github.com/prisma/prisma/tree/main/skills.
 
-Node-based Prisma Next projects expect Node.js 24 LTS or newer.
+Node-based Prisma ORM projects expect Node.js 24 LTS or newer.

package/dist/readme-postgres.md

@@ -1,6 +1,6 @@
 # {{projectName}}
 
-Generated by `prisma-next init` with the Minimal template.
+Generated by `prisma orm init` with the Minimal template.
 
 ## First run
 
@@ -9,7 +9,7 @@ Generated by `prisma-next init` with the Minimal template.
 
 ## Available scripts
 
-- `{{runDev}}` — run the Prisma Next sample script
+- `{{runDev}}` — run the Prisma ORM sample script
 
 ### Database and migrations
 
@@ -20,15 +20,15 @@ Generated by `prisma-next init` with the Minimal template.
 - `{{runMigrate}}` — apply a planned migration
 - `{{runDbSeed}}` — insert sample users manually (run after `db:init`)
 
-## Prisma Next
+## Prisma ORM
 
-Prisma Next setup is scaffolded in:
+Prisma ORM setup is scaffolded in:
 
 - `{{contractPath}}`
-- `prisma-next.config.ts`
+- `prisma.config.ts`
 - `prisma/db.ts`
 - `src/lib/prisma.ts`
 
-For provider-specific Prisma Next reference docs, see `prisma-next.md`. Prisma Next skills live in the upstream `skills/` directory: https://github.com/prisma/prisma/tree/main/skills.
+For provider-specific Prisma ORM reference docs, see `prisma-8.md`. Prisma ORM skills live in the upstream `skills/` directory: https://github.com/prisma/prisma/tree/main/skills.
 
-Node-based Prisma Next projects expect Node.js 24 LTS or newer.
+Node-based Prisma ORM projects expect Node.js 24 LTS or newer.