Prisma Next gap (e): beta/GA channel promotion off Early Access

[rickylabs]

Gap (e): Beta/GA channel promotion (off Early Access)

Parent epic: #313 — Migrate NetScript DB layer to Prisma Next (Postgres-first pilot).

Upstream status (verified 2026-07-03, prisma/prisma-next @ v0.14.0)

Early Access. README says not for production; breaking API changes every minor (v0.12 → v0.13 →
v0.14). Postgres GA was targeted Jun–Jul 2026 but not confirmed shipped as of today. Every blog
post repeats "Prisma 7 is still the right choice for production today."

Why NetScript needs it

NetScript must not take a production dependency on an EA surface. The pilot stays opt-in and
CI-guarded while Prisma Next is EA. Flipping the default scaffold off classic Prisma 7 requires a
stable channel.

When this lands → we can do

On confirmed Postgres GA + a beta/stable channel: (1) consider flipping the default Postgres
scaffold to Prisma Next (subject to user default-flip policy, epic OQ1); (2) trigger Wave B of the
delete-list (remove the classic Zod generator lane) once no engine depends on it; (3) relax the
opt-in flag gate.

Re-check mechanism

Monthly / on any .llm/tools/deps/ pass: check deps:latest (stable channel authority) + the repo
README stability line + changelog for a beta/GA/latest dist-tag. Any version bump past v0.14.0
also re-runs the Phase-1 Deno-compat spike before further pilot work (namespace + migration API churn
each minor). On beta/GA, flip this checkbox and open the default-flip decision with the user.

Labels: area:database, area:deps, wave:defer, status:triage.

Part of #313