Prisma Next gap (a): MSSQL support (absent & unplanned)

[rickylabs]

Gap (a): MSSQL support 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)

ABSENT and UNPLANNED. No mention of SQL Server / MSSQL in the roadmap, blog series, repo source,
open issues, or changelog. (Classic Prisma has MSSQL GA, but nothing ties it to Prisma Next — do NOT
treat as "coming soon".)

Why NetScript needs it

NetScript ships an MSSQL engine on the classic path (@prisma/adapter-mssql; real boot proven in
scaffold.runtime, #216). Under Option A, MSSQL stays on the classic path — this gap is a
precondition to widen Prisma Next to MSSQL, not a support removal. MSSQL is never dropped.

When this lands → we can do

Build an MSSQL pilot axis mirroring the Postgres pilot: an MSSQL defineContract workspace shape, a
PrismaNextMssqlAdapter behind the shared DatabaseAdapter port, and an MSSQL scaffold.runtime
axis. Requires gap (b) (validator consumer) already closed.

Re-check mechanism

Monthly / on any .llm/tools/deps/ pass: fetch
api.github.com/repos/prisma/prisma-next/releases + roadmap/changelog; grep for mssql / sqlserver
/ sql server. On first credible plan or driver, flip this checkbox on the epic and schedule the
MSSQL pilot slice.

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

Part of #313