Established applications no longer have to choose between blindly copying package schema fragments and discarding their existing data model.
Read-only compatibility reporting
playstack database compatibility compares selected Prisma artifacts with application-owned schema files. Reports cover logical and physical names, fields, mappings, relations, constraints, enums, native database types, and unsafe additional columns.
Named database targets can list existingArtifacts. The CLI skips one only after the application schema fully satisfies its physical contract. Failures include actionable field-level findings and remain non-mutating.
An honest fallback
Semantic resemblance is not presented as storage compatibility. When a mature schema differs physically, the application omits the managed artifact and implements the package persistence interface at its composition root. That boundary can own translations, coexistence reads, shadow writes, and record migration without teaching the CLI product-specific semantics.
