Version `8.0.0-rc.18` → `8.0.0-rc.19`. Merging this PR publishes the
release.

## What to review

- **Release notes:**
[`docs/releases/v8.0.0-rc.19.md`](https://github.com/prisma/orm/blob/release/8.0.0-rc.19/docs/releases/v8.0.0-rc.19.md).
This file becomes the GitHub Release body. It covers 51 merged PRs: 19
breaking changes, then features and fixes. `CHANGELOG.md` has the same
entry.
- **App upgrade guide:**
`skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/instructions.md`.
It has 82 changes and five scripts, and it opens with the order to run
the steps in.
- **Extension upgrade guide:**
`skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/instructions.md`.
It has 81 changes and two scripts.

## What the commits do

1. **Version bump.** It sets `8.0.0-rc.19` in every workspace
`package.json` and the `workspace:` pins in `pnpm-lock.yaml`. It also
changes the `library_version` stamp in `skills/prisma-8/SKILL.md` and
the Supabase extension version stamped in contract artefacts.
2. **Upgrade guides.** All 38 pending fragments are combined into the
two guides above. The originals are moved unchanged to
`upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/`. The
upgrade-instruction tests now read the published guides and scripts.
Tests that called live framework code were made to read committed
fixtures or were deleted, as in earlier releases.
3. **Release notes**, as above.

While combining the fragments, I made these changes:

- **Dropped `raw-columns-take-a-sql-literal`.** `Raw(...)` is new in
this release, so nobody upgrading from rc.18 has the quoted form it
tells you to change.
- **Dropped `print-generated-values-through-generator-functions`.** It
said not to add `printArguments`, which never shipped in rc.18.
- **Corrected a fragment:** an ORM call fails with
`ORM.ACTIVITY_SOURCE_MISSING` when its queryable has no activity source.
One fragment said the call just starts no activity.
- **Corrected a fragment:** a SQL `contract.d.ts` from rc.18 still
compiles. One fragment said it does not compile.

## Checks run locally

- `pnpm check:upgrade-coverage --mode publish --prev v8.0.0-rc.18 --head
HEAD` passes.
- `pnpm check:release-notes --mode pr` passes.
- The upgrade-instruction tests pass: 44 files, 744 tests.

## How the release ships

When this merges, the push to `main` carries the new root version. The
`Publish to npm` workflow then publishes `8.0.0-rc.19` under the
`latest` dist-tag and creates a pre-release GitHub Release from the
notes file. See
[`docs/oss/versioning.md`](https://github.com/prisma/orm/blob/main/docs/oss/versioning.md).

A docs PR for prisma/web follows. It must merge only after this release
is on npm.

Agent: rochester-20


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->

## Summary by CodeRabbit

* **New Features**
* Added typed contract values, raw columns, custom collections,
transaction query members, database-free plan execution, Prisma 7
`Unsupported` support, and improved type inference.
* **Bug Fixes**
* Improved migration verification, MongoDB field and validator handling,
recursive composites, enum behavior, sequence handling, and
language-server cleanup.
* **Documentation**
  * Added release notes and upgrade guidance for Prisma 8.0.0-rc.19.
* **Breaking Changes**
* Updated defaults, validation, migration metadata, ORM activity and
caching semantics, extension APIs, and removed `noCheck` support.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

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