# saraswati-stage Prisma schema

This `schema.prisma` is a **contract artifact**, not a deployable database
schema. It is auto-generated by
[`libs/oshun/persistence/scripts/generate-v3-prisma-schemas.ts`](../../../oshun/persistence/scripts/generate-v3-prisma-schemas.ts)
from the V3 contract registry
([`libs/contracts/src/v3/registry.ts`](../../../contracts/src/v3/registry.ts))
and consumed by the shape-alignment test
[`libs/oshun/persistence/src/v3-contract-prisma-drift.test.ts`](../../../oshun/persistence/src/v3-contract-prisma-drift.test.ts)
to confirm every V3 Zod contract field has a corresponding Prisma model field.

## Why there is no `migrations/` directory

`prisma migrate` migrations are intentionally omitted here because no runtime
service deploys or queries this schema. The V3 platform persists
session/avatar/binding records through the V3 contract persistence layer
(`libs/oshun/persistence`), not via this schema. Adding migrations would imply a
deployment target that doesn't exist and would diverge from the generator output
on the next run.

## How to evolve this schema

Don't edit the file directly — it carries a `Do not edit by hand` banner. Change
the V3 contract definitions in
[`libs/contracts/src/v3/`](../../../contracts/src/v3/) and re-run
`pnpm tsx libs/oshun/persistence/scripts/generate-v3-prisma-schemas.ts`. The
drift test will fail in CI if you forget.
