chore(prisma-example): upgrade the example app to Prisma Next 0.14

- deps: every @prisma-next/* pinned at 0.14.0
- prisma-next.config.ts: prismaContract takes the target PACK ref
  (@prisma-next/target-postgres/pack, carrying defaultNamespaceId)
  instead of the control descriptor
- contract re-emitted in the 0.14 shape (public namespace, entries
  envelope, domain plane); migrations regenerated from scratch —
  fresh app initial migration + the cipherstash extension space
  re-materialised from the upgraded workspace package (head
  sha256:1e86a016…)
- ORM/builder access namespace-qualified: db.orm.public.User,
  db.sql.public.users (src/index.ts + every e2e suite)
- the CLI renamed 'migration apply' to 'migrate': package.json script,
  e2e global-setup, and READMEs updated (--yes for non-interactive
  runs)
- e2e walkthrough test (e2e/tests/prisma-example-readme.e2e.test.ts):
  snapshot/restore examples/prisma/.env instead of deleting it in
  teardown — the old teardown destroyed a developer's real
  credentials file

Full example e2e suite green against the docker harness: 36 passed,
1 skipped (known jsonbPathExists limitation).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: calvinbrewer

e2e/tests/prisma-example-readme.e2e.test.ts

@@ -62,10 +62,15 @@ function runStep(commandLine: string, timeoutMs: number): StepResult {
   }
 }
 
+// `.env` is included so a developer's real credentials file survives the
+// walkthrough: the README's `cp .env.example .env` step overwrites it, and
+// without the snapshot the teardown would delete it outright. The snapshot
+// captures it before the run and the restore puts the original back.
 const TRANSIENT_PATHS = [
   'migrations/app',
   'src/prisma/contract.json',
   'src/prisma/contract.d.ts',
+  '.env',
 ] as const
 
 async function snapshotTransientOutputs(): Promise<string> {
@@ -170,10 +175,11 @@ describe.skipIf(!authConfigured)(
     afterAll(async () => {
       // Teardown the bundled Postgres container regardless of outcome.
       runStep('docker compose down -v', 60_000)
-      // Restore the transient outputs from snapshot so the working tree is clean.
+      // Restore the transient outputs from snapshot so the working tree is
+      // clean. `.env` is part of the snapshot: the walkthrough's
+      // `cp .env.example .env` overwrote it, and the restore brings back the
+      // developer's original (or removes the copy when none existed before).
       await restoreTransientOutputs(snapDir)
-      // Remove the .env we copied in the walkthrough (not tracked anyway).
-      rmSync(join(EXAMPLE_DIR, '.env'), { force: true })
     }, 120_000)
 
     // Per-step exit-zero assertion, registered once per non-skipped README line.

examples/prisma/README.md

@@ -33,7 +33,7 @@ docker compose up -d
 pnpm install
 pnpm emit                  # PSL → contract.{json,d.ts}
 pnpm migration:plan --name initial
-pnpm migration:apply       # installs EQL bundle + your app schema in one sweep
+pnpm migration:apply       # installs EQL bundle + your app schema in one sweep (runs `prisma-next migrate`)
 pnpm start                 # runs the demo
 ```