docs(docs): update the Prisma ORM 8 pages for 8.0.0-rc.10 - #8261

…pes section through the rewrite

#8261 added "Model and result types" to the old page. Rebased onto main and rewrote that section against this page's schema and wording: the page's own contract import, the example User's fields, no SQLite, and the rc.10 note that a contract emitted earlier has no Models until you emit again. Facts unchanged from the rc.10 release notes and shape.ts.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
Signed-off-by: willbot <[email protected]>
Signed-off-by: Will Madden <[email protected]>

…d the Supabase fixture re-emit (prisma#30271)

## At a glance

Cutting rc.10 took two extra commits and a docs-site PR that the release
skill did not mention. The skill now describes all three, so the next
release cut produces them without rediscovery:

```text
1. chore(release): bump to <version>
2. chore(release): re-emit the Supabase fixtures + upgrade-recipe declaration   ← CI fails without this
3. docs(release): release notes                                                  ← already covered
4. prisma/web PR: docs(docs): update the Prisma ORM 8 pages for <version>       ← new step 10
```

## What changed in the skill

- **Step 5 (sanity-check)** now says that the Supabase extension stamps
its version into eight emitted fixture files, that the `Fixtures` job
diffs them, and that `check:upgrade-coverage` then requires the bump PR
to declare the re-emit in the app upgrade recipe. The rc.9 and rc.10
bumps both needed exactly this.
- **New step 10** prepares the prisma/web docs PR from the release
notes: clone into a gitignored path in the release worktree, move the
version numbers on the three pages that carry them, walk the notes entry
by entry to find the pages that state old behaviour (with the usual home
for each kind of change), run the three docs linters, and open the PR
with a body that says it merges only after the publish. This is the
process rc.10 followed in prisma/web#8261.
- **Step 11 (report)** reports both PRs. It also records the merge order
if the maintainer asks the agent to merge, and two merge-queue facts
that cost time on rc.10: the queue refuses a PR with any unresolved
review thread even when checks are green, and CodeRabbit flags the
tag-pinned recipe links as dead every time, which is expected because
the publish creates the tag.
- The frontmatter description mentions the docs-site PR so the skill
triggers with that expectation.

## Validation

`pnpm lint:skills` passes.

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


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

## Summary by CodeRabbit

- **Documentation**
- Updated the npm release workflow to include required version updates
across Supabase contract and fixture files.
- Added upgrade-coverage instructions for re-emitting the Supabase
extension version.
- Added steps to prepare a matching Prisma documentation-site pull
request with updated version tables and release notes.
- Clarified reporting, pull request linking, worktree details, and the
required release-first merge order.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: willbot <[email protected]>
Signed-off-by: Will Madden <[email protected]>
Co-authored-by: Claude Fable 5.1 <[email protected]>