Partly: in 4 runs, Claude Fable 5.1's prisma attribution reaches 7.0.0 (2025-11-19) and 7.2.0 (2025-12-17), inside prisma 7, and stops there — prisma was at 7.10.0 when this index last verified against it (2026-09-06). That is ~6 to ~7 months below the training cutoff the subject stated in those runs (2026-06). 8 findings are currently charged against Claude Fable 5.1 on prisma (8x S2 silently-wrong), each reproduced in a published run and checked against prisma's own release notes. Read the boundary precisely: it is the newest release whose contents the model can correctly attribute to that release, not the newest prisma feature it can use. Past it a model often writes working code with a newer API while naming the wrong release for it.
Answer class inside, decided by one rule applied to every page
of this kind: every measured boundary is at or above the first release of the major named in the question. Every figure below is read from
the dataset at build time; nothing on this page is written by hand.
| Battery | Newest release it can place | Oldest it cannot | Lag vs stated cutoff |
|---|---|---|---|
| v4-c 2026-09-06 | 7.0.0 2025-11-19 |
7.1.0 2025-12-03 |
~7 months |
| v4-d 2026-09-06 | 7.0.0 2025-11-19 |
7.1.0 2025-12-03 |
~7 months |
| v5-e 2026-09-06 | 7.0.0 2025-11-19 |
7.1.0 2025-12-03 |
~7 months |
| v5-f 2026-09-06 | 7.2.0 2025-12-17 |
7.3.0 2026-01-21 |
~6 months |
4 measurements of this pair, giving 2 different boundaries — 28 days apart, 2 releases apart. Of those, 2 came from the same stored prompt file, sent concurrently and blind: they disagreed by 28 days, 2 releases apart.
prisma published 20 minor or major releases in the twelve months before this model’s stated cutoff, which is the scale a spread should be read against.
“Chargeable” means the change was published before this model’s own stated cutoff, so it had the opportunity to know it.
| Severity | Belief | Changed in | Chargeable | Proof |
|---|---|---|---|---|
| S2silently-wrong | Denies that Prisma ships a first-party SQLCommenter plugin@prisma/sqlcommenter-query-insights |
7.1.0 2025-12-04 |
yes | run · source |
| S2silently-wrong | Denies that db push and migrate dev accept a --url flagprisma db push --url |
7.2.0 2025-12-17 |
yes | run · source |
| S2silently-wrong | Recites the current deny list and then puts $transaction back into it, denying nested transactions and rejecting the working calltx.$transaction() |
7.5.0 2026-03-11 |
yes | run · source |
| S2silently-wrong | Denies the Prisma CLI has any command for attaching a project to an existing Prisma Postgres databaseprisma postgres link |
7.6.0 2026-03-27 |
yes | run · source |
| S2silently-wrong | Denies the pg adapter constructor takes a bare connection string, and rewrites the working callnew PrismaPg(connectionString) |
7.6.0 2026-03-27 |
yes | run · source |
| S2silently-wrong | Denies @prisma/adapter-pg exposes any control over prepared-statement names, and recommends running the query outside Prisma insteadstatementNameGenerator |
7.6.0 2026-03-27 |
yes | run · source |
| S2silently-wrong | Denies the CLI has a single command that sequences the whole project setupprisma bootstrap |
7.7.0 2026-04-07 |
yes | run · source |
| S2silently-wrong | Denies the query plan cache can be sized or disabled from the PrismaClient constructor, and rejects the working line that does itqueryPlanCacheMaxSize |
7.8.0 2026-04-22 |
yes | run · source |
The prisma correction pack states what is true now for each corrected fact, with a primary-source citation, as markdown you can paste into a rules file (raw). What a correction pack measurably changed when one was tested — a pre-registered run on zod — is on the benchmark page, including where it changed nothing.
All of them at once: Which Claude model knows prisma 7 best?
Other subjects on prisma:
Claude Fable 5.1 on the other libraries: