prisma-next: move migration contracts into the snapshots/ store layout

[wmadden]

In progress - do not merge

Adopts prisma-next's content-addressed contract-snapshot layout for packages/prisma-next/migrations, ahead of upgrading @prisma-next/* to the release that ships it (prisma/prisma-next#1018).

Only install_eql_v3_bundle carries a contract; its end-contract.{json,d.ts} move byte-for-byte into migrations/snapshots/<hex>/contract.{json,d.ts} (<hex> = the storage hash, sha256: stripped). migration.json, migration.ts, ops.json, and refs/head.json are untouched — the migrations don't import the contract and the runtime-recomputed EQL migrationHash is unaffected.

⚠️ Merge together with the @prisma-next 0.14→0.16 upgrade: the new tooling reads the store, and on current 0.14 tooling the old sibling files are still expected. migration apply is runner-independent either way (reads only migration.json + ops.json).

Rationale: prisma-next ADR 239. (prisma-next's one-shot migrator can't run this tree unmodified — the EQL bundle recomputes its hash from runtime ops, tripping the migrator's committed-ops integrity check — so this was done by hand.)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1a40257

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

💤 Files selected but had no reviewable changes (2)

• packages/prisma-next/migrations/snapshots/efd408cf8924b4d1805bf5acced8898114aa03cd46b465720179c82a4431d51e/contract.d.ts
• packages/prisma-next/migrations/snapshots/efd408cf8924b4d1805bf5acced8898114aa03cd46b465720179c82a4431d51e/contract.json

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8eeac4ee-1d92-454a-8f9e-0df8059ee475

📥 Commits

Reviewing files that changed from the base of the PR and between 98a9c09 and 1a40257.

📒 Files selected for processing (2)

• packages/prisma-next/migrations/snapshots/efd408cf8924b4d1805bf5acced8898114aa03cd46b465720179c82a4431d51e/contract.d.ts
• packages/prisma-next/migrations/snapshots/efd408cf8924b4d1805bf5acced8898114aa03cd46b465720179c82a4431d51e/contract.json

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderdan]

Thanks for this @wmadden! I see that Prisma Next 0.16 has just been published - should we update that in this PR, or would you suggest doing it separately?