`8.0.0-rc.15` → `8.0.0-rc.16`

The peer dependency of `@prisma/orm-toolchain`, in
`packages/9-public/@prisma/orm-toolchain/package.json`:

```diff
-    "@prisma/cli-engine": "0.6.2",
+    "@prisma/cli-engine": "0.6.3",
```

## Why this release

Engine 0.6.3 fixes `prisma orm init` and `prisma contract emit` failing
on a valid contract with Bun. Engine 0.6.2 required ArkType `2.2.3`
exactly while the ORM packages accept `^2.2.2`, so an install could hold
two ArkType copies. Engine 0.6.3 accepts `^2.2.7`
([prisma/prisma-cli#332](https://github.com/prisma/prisma-cli/pull/332)).

The Prisma CLI can only ship engine 0.6.3 once every product it mounts
peers exactly 0.6.3: its conformance check refuses a mismatch. Composer
0.27.0 already peers 0.6.3. ORM rc.15 still peers 0.6.2, so the next
Composer and CLI releases wait on this one.

## What this PR holds

- Every `@prisma/cli-engine` pin in the repository moves from `0.6.2` to
`0.6.3`.
- The lockfile is deduplicated so the workspace resolves one ArkType
copy, `2.2.7`. With two copies, the config-loader declaration build
fails with `TS2742`. The dedupe also drops seven duplicate copies of
build tools whose other versions were already in the lockfile; it adds
no new package version. The size-limit report shows bundles about 0.2%
larger, from ArkType 2.2.7.
- [prisma/orm#30539](https://github.com/prisma/orm/pull/30539), merged
to `main` after this branch was cut, is merged in and released here: its
`@default` diagnostics change and its extension API renames.
- Upgrade guides for this hop, assembled from two fragments,
`engine-pin-moves-to-0-6-3` and `arguments-typed-by-data-type`:
[app](skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.15-to-8.0.0-rc.16/instructions.md)
and
[extension](skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.15-to-8.0.0-rc.16/instructions.md).
- The version bump, and the release notes in
[`docs/releases/v8.0.0-rc.16.md`](docs/releases/v8.0.0-rc.16.md).

## Checks run locally

- `pnpm build`, and the package tests of the CLI and the config loader.
- `pnpm test:packages`: one test timed out under machine load and passes
alone. Three tarball tests could not install on this machine because its
package manager refuses `@vercel/detect-agent@1.2.5`, which this PR does
not change; CI runs them.
- One CLI integration test, and `check:upgrade-coverage --mode publish`
against `v8.0.0-rc.15`.

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.16`
under `latest`, and a GitHub Release marked pre-release is created from
the notes file. See [`docs/oss/versioning.md`](docs/oss/versioning.md).
After it publishes, Composer and then the Prisma CLI release against it.

Agent: grendel-61

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


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

## Summary by CodeRabbit

* **New Features**
* Prisma 8.0.0-rc.16 updates extension APIs for working with data types
and tagged-literal text. Extension authors should review the migration
guidance for compatibility changes.
* **Bug Fixes**
* Bun commands that validate contracts now avoid failures caused by
multiple ArkType copies.
* **Improvements**
* `@default` diagnostics have updated locations and messages, including
more relevant suggestions for list elements.
* Prisma 8.0.0-rc.16 requires CLI engine 0.6.3; projects with a direct
engine pin should update it.

<!-- 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>