/**
 * COMPILE-ONLY fixture — no runtime exports, nothing to import.
 *
 * The package's headline promise is that a client generated from
 * `prisma/schema.prisma` satisfies {@link AlfizPrismaDelegates}
 * structurally, with no cast. That promise once broke silently: our create
 * data used a Json type admitting bare `null`, which Prisma's generated
 * inputs reject (SQL NULL needs the `Prisma.JsonNull` sentinel), and every
 * adopter got `prismaDriver(db as unknown as AlfizPrismaDelegates)` — the
 * exact cast the README calls unnecessary.
 *
 * This file replicates the input/output types Prisma 7 generates for the v2
 * Alfiz models — the Json input plumbing verbatim (`JsonNullClass`,
 * `InputJsonValue` with nested nulls and `toJSON`), scalar unions
 * (`bigint | number`), create-input optionality, filter objects, and the
 * compound-`@@id` where-unique inputs the partition discriminator
 * introduces (`app_id`, `app_userId`, …) — and asserts assignability at the
 * type level. If a delegate-surface change breaks compatibility with what
 * `prisma generate` emits, `tsc` fails here, naming the model. Deliberately
 * simplified: `select`/`include`/`omit` plumbing and extension generics are
 * elided, because compatibility breaks live in the input types, not the
 * selection machinery.
 *
 * The v2 fixture also pins the discriminator posture itself: our where
 * types REQUIRE `app` while Prisma's generated where inputs leave every
 * field optional, so a driver query that forgot the partition fails to
 * compile against OUR types long before it could reach a database — see
 * the `_WhereRequiresApp` assertions at the bottom.
 */
export {};
//# sourceMappingURL=prisma-client-shape.d.ts.map