Brief: S5-D1 — probe prisma-next's MongoDB surface

Task

Establish, with citations, what prisma-next actually supports for MongoDB today — the fact base the prisma-mongodb-upgrade skill will be authored from. Read-only investigation; no prisma/skills changes yet.

Method

• Clone (or gh api-read) prisma/prisma-next at current main; record the commit SHA all citations pin to.
• Investigate: does the contract/config surface accept a MongoDB provider? What does the query runtime support for Mongo (CRUD? raw escape hatches? transactions)? What is the migrations story for Mongo (does emit/verify/sign/migrate apply, or a push-style flow)? What do prisma-next's own shipped skills (skills/ dir: quickstart, contract, migrations, queries, runtime, upgrade cluster) say about MongoDB? Any roadmap/issue signals on maturity?
• Also assemble the v6-side fact list the skill will cite (from released v6 docs): mongodb provider basics, @db.ObjectId, composite/embedded types, db push-only migrations, $runCommandRaw/findRaw/aggregateRaw, replica-set requirement for transactions. One citation per claim (docs URL or repo file).

Completed when

• A verdict, stated plainly: Next's MongoDB support is (a) usable now for real apps, (b) present but partial (enumerate the gaps), or (c) absent. If (c): HALT — I12 (the slice's premise is operator-stated; the operator decides).
• A fact table: claim → citation (repo file at the pinned SHA, or docs URL), covering both the Next side and the v6 side — consumable verbatim by the authoring dispatch.
• A recommended lead for the skill (migrate-now vs stay-on-v6-first) derived from the verdict, with one paragraph of reasoning.

Constraints (terse)

Read-only everywhere; no commits, no pushes. Heartbeats as usual.

• Time-box: 35 minutes.
• Halt conditions: verdict (c); prisma-next unreachable.

Same return shape. Begin.