Prisma Next gap (c): MySQL engine (planned, no date)

[rickylabs]

Gap (c): MySQL engine in Prisma Next

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)

PLANNED, no date. MySQL is named as a planned engine but is not shipped in Early Access.

Why NetScript needs it

NetScript ships MySQL on the classic path via the custom @netscript/prisma-adapter-mysql (one of the
two engines in the standing scaffold.runtime E2E axes). Under Option A, MySQL stays classic until
this gap closes — a precondition to widen the pilot, not a support change.

When this lands → we can do

Add a MySQL pilot axis: a MySQL defineContract workspace, a PrismaNextMysqlAdapter behind the
shared port, and a MySQL scaffold.runtime axis. Requires gap (b) already closed.

Re-check mechanism

Monthly / on any .llm/tools/deps/ pass: fetch releases + roadmap; look for a shipped MySQL adapter /
target. On ship, flip this checkbox and schedule the MySQL pilot slice.

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

Part of #313