`8.0.0-rc.14` → `8.0.0-rc.15`

A project on rc.14 upgrades in this order: upgrade the packages, run the
`data-type-in-contract` script from the app recipe in the project root,
run `prisma db sign` against every database, make the code changes the
recipe lists, then run `prisma contract emit` once.

```sh
curl -O https://raw.githubusercontent.com/prisma/orm/v8.0.0-rc.15/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.14-to-8.0.0-rc.15/scripts/data-type-in-contract/data-type-in-contract.ts
node data-type-in-contract.ts
prisma db sign
```

## What this PR holds

- The version bump in every workspace `package.json`, `pnpm-lock.yaml`,
the `library_version` stamp in `skills/prisma-8/SKILL.md`, and the
restamped Supabase contract artefacts.
- The assembled upgrade guides for this hop:
[`skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.14-to-8.0.0-rc.15/`](skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.14-to-8.0.0-rc.15/instructions.md)
(54 changes) and
[`skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.14-to-8.0.0-rc.15/`](skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.14-to-8.0.0-rc.15/instructions.md)
(78 changes), each with its copy of the `data-type-in-contract` script.
The 26 pending fragments are archived unchanged under
`upgrade-instructions/releases/8.0.0-rc.14-to-8.0.0-rc.15/sources/`.
- The `data-type-in-contract` tests now run the published script copies.
The fixture generator and the hash test that called live framework code
are deleted, and one live-verifier assertion is frozen to the hash it
accepted, so the tests check the script against committed
before-and-after fixtures only.
- The release notes,
[`docs/releases/v8.0.0-rc.15.md`](docs/releases/v8.0.0-rc.15.md),
mirrored into `CHANGELOG.md`. Review the notes as the user-facing
surface of this release: 16 breaking-change entries, each naming its
change ids in the recipes.

## What to check

- `pnpm check:upgrade-coverage --mode publish --prev v8.0.0-rc.14 --head
HEAD` and `pnpm check:release-notes --mode pr` pass on the tip.
- The recipe links in the notes point at the `v8.0.0-rc.15` tag, which
the publish creates, so they resolve only after the release.
- [prisma/prisma#30539](https://github.com/prisma/prisma/pull/30539) is
open and adds one new pending fragment and edits four fragments this PR
archives. Merge this release first; that PR then needs its fragment
changes reconciled against the published rc.15 guides.

The docs site PR for this release is
[prisma/web#8400](https://github.com/prisma/web/pull/8400). Merge it
after this release is on npm.

Merging this PR ships the release: the push to `main` carries the bumped
root `version`, the `Publish to npm` workflow publishes `8.0.0-rc.15`
under `latest`, and a GitHub Release marked pre-release is created from
the notes file. See [`docs/oss/versioning.md`](docs/oss/versioning.md).

Agent: grendel-61

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>