The Unsafe surface: rename, builders, executors, ORM proxy and transaction-bound shape

[borisno2]

Parent

#1122 — build spec 2 of the Prisma 8 architecture spec. Lands on the prisma-8 integration branch, not main.

What to build

context.prisma is replaced by the Unsafe surface under a name stating the bypass: Prisma's sql and raw builders untouched, query(plan) returning Prisma's streaming result and execute(plan) returning statistics, both entering the unsafe origin (the streaming result through the scope-preserving wrapper), an orm lane that is a transparent proxy entering the unsafe origin on every call and re-proxying returned collections, no bare client, no prepare, no runtime, and a transaction-bound shape on the transaction context that closes over the client's raw lane and executes through tx.

Acceptance criteria

• Under the tripwire in throw mode, the sixteen statement shapes the spike measured execute covered: single-statement reads and creates, two-statement update/delete, three-statement nested connect through the proxy, two terminals in one transaction, a DSL plan and a raw plan through the executors
• A foreign query throws; a plan built inside a scope and run outside throws; a lazy result held across an await is covered
• Interleaved engine, unsafe and foreign calls over a saturated pool see exactly their own origin
• prepare and runtime are not reachable from the surface's type or runtime value
• Errors from the surface are raw driver errors

Blocked by

• The generated context constructs the Prisma 8 client from contract.json #1142
• createTestContext on @opensaas/stack-core/testing #1143

---

Generated by Claude Code

[borisno2]

Delivered by #1204, merged to prisma-8. The surface is context.unsafe.

Review found and fixed an atomicity defect the PR introduced: context.transaction opened a real interactive transaction while the child context's db stayed bound to the outer ORM handle, so tx.db.* writes auto-committed outside it (or deadlocked on a single-connection pool). The child handle is now resolved off the transaction's own orm root, with guard rails at both ends.

Also closed a proxy containment hole (markResult did not wrap returned functions, so a method returning a callable escaped the mark) and softened the prepare/runtime claim to what is actually established — not among the surface's own members, which is not the same as unreachable through the ORM lane.