{
  "$schema": "../../schema/run.schema.json",
  "run_id": "prisma--claude-fable-5--v1--2026-08-31",
  "supersedes": null,
  "library": {
    "name": "prisma",
    "ecosystem": "npm",
    "latest_version_at_test": "7.10.0",
    "latest_version_verified_on": "2026-08-31",
    "latest_version_note": "Latest stable. The `prisma` package's npm `latest` dist-tag resolved to the prerelease 8.0.0-rc.12 on the same date; no stable 8.0.0 exists."
  },
  "model": {
    "id": "claude-fable-5",
    "label": "Claude Fable 5",
    "vendor": "Anthropic",
    "invoked_as": "Agent tool, model alias \"fable\"",
    "self_reported_cutoff": "2026-01",
    "cutoff_basis": "Self-reported: \"My stated training cutoff is January 2026, but my reliable, detailed knowledge of Prisma release contents tapers off around mid-2025.\"",
    "believed_latest_version": "6.13–6.16",
    "believed_latest_quote": "\"The latest version I'm confident exists is in the Prisma 6.x line — I have awareness of version numbers into roughly 6.13–6.16 (second half of 2025), but only as numbers. The most recent release whose contents I can actually describe with confidence is roughly 6.7 (around May 2025) — the queryCompiler + driverAdapters engine-less client preview era ... First release I know essentially only as a version number: around 6.8 onward.\"",
    "knowledge_stops_at_version": "6.7.0",
    "knowledge_stops_on": "2025-04-29",
    "knowledge_gap_starts_at_version": "6.8.0",
    "knowledge_gap_starts_on": "2025-05-15",
    "cutoff_lag_months": 8
  },
  "test": {
    "date": "2026-08-31",
    "battery": "prisma/v1",
    "battery_spec": "prompts/prisma.md",
    "prompt_file": null,
    "tasks": 10,
    "direct_questions": 4,
    "tool_uses_during_test": 0,
    "probe_window": { "from": "6.18.0", "to": "7.0.0" },
    "self_test": false,
    "saturated": false,
    "status": "open",
    "retested_on": null
  },
  "sources": [
    "https://github.com/prisma/prisma/releases/tag/7.0.0",
    "https://github.com/prisma/prisma/releases/tag/6.7.0",
    "https://github.com/prisma/prisma/releases/tag/6.6.0",
    "https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7",
    "https://registry.npmjs.org/prisma"
  ],
  "findings": [
    {
      "id": "F1",
      "severity": "S1",
      "severity_label": "breaks-build",
      "title": "Constructs the client with no arguments in every runnable artefact",
      "api": "new PrismaClient()",
      "change_kind": "removed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "\"const prisma = new PrismaClient()\" in tasks 1, 2, 3 and 5, with the mechanism stated: \"the client picks it up automatically, so nothing about the URL appears in this file.\"",
      "wrong_code": "const prisma = new PrismaClient()",
      "correct_code": "const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\nconst prisma = new PrismaClient({ adapter })",
      "impact": "Throws at construction on Prisma 7 before any query runs.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Prisma Client changes",
          "published_on": "2025-11-19",
          "quote": "new PrismaClient() support has been removed"
        }
      ]
    },
    {
      "id": "F2",
      "severity": "S1",
      "severity_label": "breaks-build",
      "title": "Generator block with no output path",
      "api": "generator client { output }",
      "change_kind": "requirement",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "`generator client { provider = \"prisma-client-js\" }` in all three schemas; in (d), \"with the classic prisma-client-js generator, into node_modules/.prisma/client\".",
      "wrong_code": "generator client {\n  provider = \"prisma-client-js\"\n}",
      "correct_code": "generator client {\n  provider = \"prisma-client\"\n  output   = \"../src/generated/prisma\"\n}",
      "impact": "`prisma generate` refuses.",
      "citations": [
        {
          "url": "https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7",
          "title": "Upgrade to Prisma ORM 7 — Schema changes",
          "quote": "the output field is now required in the generator block."
        }
      ]
    },
    {
      "id": "F3",
      "severity": "S3",
      "severity_label": "deprecated",
      "title": "Uses the superseded generator provider in every schema",
      "api": "provider = \"prisma-client-js\"",
      "change_kind": "deprecated",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "`prisma-client-js` throughout the tasks, while question (d) and the serverless answer both describe the newer `prisma-client` generator accurately — it is simply never the one written.",
      "wrong_code": "generator client {\n  provider = \"prisma-client-js\"\n}",
      "correct_code": "generator client {\n  provider = \"prisma-client\"\n  output   = \"../src/generated/prisma\"\n}",
      "impact": "Works today, stated to be removed in a future release, and requires the extra `@prisma/client-runtime-utils` package once `output` is set.",
      "citations": [
        {
          "url": "https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7",
          "title": "Upgrade to Prisma ORM 7 — Schema changes",
          "quote": "The older prisma-client-js provider will be removed in future releases of Prisma ORM."
        }
      ]
    },
    {
      "id": "F4",
      "severity": "S1",
      "severity_label": "breaks-build",
      "title": "Imports PrismaClient from @prisma/client",
      "api": "import { PrismaClient } from '@prisma/client'",
      "change_kind": "behavior-changed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "\"import { PrismaClient } from '@prisma/client'\" in every file shown.",
      "wrong_code": "import { PrismaClient } from '@prisma/client'",
      "correct_code": "import { PrismaClient } from './generated/prisma/client'",
      "impact": "The package no longer resolves to a generated client.",
      "citations": [
        {
          "url": "https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7",
          "title": "Upgrade to Prisma ORM 7 — Schema changes",
          "quote": "// After import { PrismaClient } from \"./generated/prisma/client\" ;"
        }
      ]
    },
    {
      "id": "F5",
      "severity": "S1",
      "severity_label": "breaks-build",
      "title": "No config file in the project it sets up; the datasource URL stays in the schema",
      "api": "prisma.config.ts",
      "change_kind": "requirement",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "Task 4 lists the files after `migrate dev` as `.env`, `prisma/schema.prisma`, the migration SQL and `migration_lock.toml`. No config file appears in any of the ten tasks, though question (d) describes one.",
      "wrong_code": "datasource db {\n  provider = \"postgresql\"\n  url      = env(\"DATABASE_URL\")\n}",
      "correct_code": "// prisma.config.ts\nexport default defineConfig({\n  schema: 'prisma/schema.prisma',\n  datasource: { url: env('DATABASE_URL') },\n})",
      "impact": "The migration commands the answer prescribes require the config file on 7.x.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Schema and config file updates",
          "published_on": "2025-11-19",
          "quote": "prisma.config.ts is now required for projects looking to perform introspection and migration."
        }
      ]
    },
    {
      "id": "F6",
      "severity": "S2",
      "severity_label": "silently-wrong",
      "title": "States the CLI loads .env itself — then contradicts it in the belief probe",
      "api": "automatic .env loading",
      "change_kind": "behavior-changed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "Task 4: \"The connection string lives in .env at the project root ... the Prisma CLI loads it automatically — this is the CLI's own dotenv handling.\" Question (d): \"when prisma.config.ts is in play, the CLI no longer auto-loads .env for you — you load env yourself.\"",
      "wrong_code": "# .env — loaded automatically by the CLI\nDATABASE_URL=\"postgresql://...\"",
      "correct_code": "import 'dotenv/config'\nimport { defineConfig, env } from 'prisma/config'",
      "impact": "The variable is unset when the CLI runs. Charged under the code-vs-claim rule: the working instructions assert the auto-load, and the correction appears only in the leading belief probe, four answers later.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Explicit loading of environment variables",
          "published_on": "2025-11-19",
          "quote": "we're no longer automatically loading environment variables when invoking the Prisma CLI"
        }
      ]
    },
    {
      "id": "F7",
      "severity": "S1",
      "severity_label": "breaks-build",
      "title": "Seed command in package.json, with the implicit-run promise",
      "api": "package.json prisma key",
      "change_kind": "removed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "\"With that \\\"prisma\\\".seed key wired up, seeding runs automatically as part of the normal workflow: prisma migrate dev triggers it ... prisma migrate reset always runs it\" — followed by \"(Note: in newer Prisma versions that use prisma.config.ts, the seed command moves into the config file's migrations.seed field instead of package.json — see (d).)\"",
      "wrong_code": "{\n  \"prisma\": {\n    \"seed\": \"tsx prisma/seed.ts\"\n  }\n}",
      "correct_code": "// prisma.config.ts\nexport default defineConfig({\n  migrations: { seed: 'tsx prisma/seed.ts' },\n})",
      "impact": "Neither half works on 7.x: the key is not read, and migrate no longer runs the seed.",
      "scope_note": "The hedge names the correct destination — `migrations.seed` in the config file — and is the most nearly-exempt claim in the run. Charged because the artefact it shipped is the package.json form and the parenthetical treats the config file as an alternative for \"newer versions\" rather than the current one.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Removed support for prisma keyword in package.json",
          "published_on": "2025-11-19",
          "quote": "With the move to prisma.config.ts, this no longer makes sense and has been removed."
        },
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Removal of implicit Prisma commands",
          "published_on": "2025-11-19",
          "quote": "prisma migrate would run prisma generate and prisma seed. This behaviour has been removed"
        }
      ]
    },
    {
      "id": "F8",
      "severity": "S1",
      "severity_label": "breaks-build",
      "title": "Recommends prisma generate --no-engine",
      "api": "prisma generate --no-engine",
      "change_kind": "removed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "\"Or use Accelerate / --no-engine. prisma generate --no-engine produces a client with no engine binary that talks to Prisma Accelerate over HTTP.\"",
      "wrong_code": "npx prisma generate --no-engine",
      "correct_code": "npx prisma generate",
      "impact": "Unknown flag; the build step fails.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Removal of prisma generate flags",
          "published_on": "2025-11-19",
          "quote": "prisma generate --no-engine"
        }
      ]
    },
    {
      "id": "F9",
      "severity": "S2",
      "severity_label": "silently-wrong",
      "title": "Deployment advice organised around matching engine binaries to the container's libc",
      "api": "engineType",
      "change_kind": "removed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "\"its query engine binary must match the container's OS\", with `binaryTargets = [\"native\", \"linux-musl-openssl-3.0.x\"]` and \"the generated client lives in node_modules/.prisma/client with the engine binary inside\".",
      "wrong_code": "generator client {\n  provider      = \"prisma-client-js\"\n  binaryTargets = [\"native\", \"linux-musl-openssl-3.0.x\"]\n}",
      "correct_code": "generator client {\n  provider = \"prisma-client\"\n  output   = \"../src/generated/prisma\"\n}",
      "impact": "Time spent on a class of deployment failure that 7.0.0 deleted, and a runtime layout that no longer exists.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Removed Client Engines",
          "published_on": "2025-11-19",
          "quote": "We've removed the following client engines: LibraryEngine (engineType = \"library\", the Node-API Client)"
        }
      ]
    },
    {
      "id": "F10",
      "severity": "S1",
      "severity_label": "breaks-build",
      "title": "migrate diff with the removed --from-url / --to-schema-datamodel flags",
      "api": "prisma migrate diff",
      "change_kind": "renamed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "\"npx prisma migrate diff --from-url \\\"$DATABASE_URL\\\" --to-schema-datamodel prisma/schema.prisma --script\", with `--to-migrations` and `--shadow-database-url` offered as variants.",
      "wrong_code": "npx prisma migrate diff \\\n  --from-url \"$DATABASE_URL\" \\\n  --to-schema-datamodel prisma/schema.prisma \\\n  --script",
      "correct_code": "npx prisma migrate diff \\\n  --from-config-datasource \\\n  --to-schema prisma/schema.prisma \\\n  --script",
      "impact": "Unknown-flag error.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Removal of prisma migrate flags",
          "published_on": "2025-11-19",
          "quote": "This is now replaced with just --[from/to]-schema. The usage is otherwise the same."
        }
      ]
    },
    {
      "id": "F11",
      "severity": "S2",
      "severity_label": "silently-wrong",
      "title": "Says the mapped value is invisible to application code",
      "api": "generated enum values",
      "change_kind": "behavior-changed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "\"The generated TypeScript uses the Prisma-level names — the @map is invisible in your app code ... If you need the raw DB string at the edge of your system, keep a small explicit mapping table; the generated client doesn't expose the @map values.\"",
      "wrong_code": "export const PaymentProvider = {\n  MIXPLAT_SMS: 'MIXPLAT_SMS',\n  INTERNAL_TOKEN: 'INTERNAL_TOKEN'\n} as const",
      "correct_code": "export const PaymentProvider: {\n  MixplatSMS: 'mixplat/sms'\n  InternalToken: 'internal/token'\n}",
      "impact": "Prescribes a hand-maintained lookup table for values the client now hands you directly, and any string comparison against the member name silently fails.",
      "withdrawn": {
        "on": "2026-09-03",
        "reason": "The subject was right and this Index was wrong. Prisma reverted the 7.0.0 mapped-enum change in 7.3.0 (2026-01-21), so at every release from 7.3.0 onward — including the 7.10.0 that was current when this run was scored — the generated enum object maps each member name to itself, which is what the subject wrote. The charge rested on the 7.0.0 release note and was never verified against a generated client.",
        "journal": "JOURNAL/048"
      },
      "scope_note": "Charged against the generated shape 7.0.0 documents; the pre-7 shape is not separately verified here.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — Mapped enums",
          "published_on": "2025-11-19",
          "quote": "We now support the @map attribute for enum members, which can be used to set their expected runtime values"
        }
      ]
    },
    {
      "id": "F12",
      "severity": "S4",
      "severity_label": "wrong-metadata",
      "title": "Sets a MongoDB team up on the current major, which dropped MongoDB",
      "api": "MongoDB support",
      "change_kind": "removed",
      "introduced_in": "7.0.0",
      "introduced_on": "2025-11-19",
      "chargeable": true,
      "model_belief": "A full MongoDB setup with eight caveats — none of them the version. Its closing advice was to \"evaluate Mongoose or the raw driver honestly\" if greenfield, on the grounds that Mongo support \"gets features later or not at all\".",
      "wrong_code": "datasource db {\n  provider = \"mongodb\"\n  url      = env(\"DATABASE_URL\")\n}",
      "correct_code": "// MongoDB: stay on Prisma 6\n//   npm i -D prisma@6 && npm i @prisma/client@6",
      "impact": "Directionally right about the neglect, wrong about the consequence: the current major does not support the database at all.",
      "citations": [
        {
          "url": "https://github.com/prisma/prisma/releases/tag/7.0.0",
          "title": "Prisma 7.0.0 release notes — MongoDB support in Prisma 7",
          "published_on": "2025-11-19",
          "quote": "Currently, MongoDB is not supported in Prisma 7. For folks using MongoDB, please stay on Prisma v6."
        }
      ]
    },
    {
      "id": "F13",
      "severity": "S4",
      "severity_label": "wrong-metadata",
      "title": "Knowledge stops at 6.7.0 — eight months before its own stated cutoff, and six months earlier than the same model's boundary on four other libraries",
      "api": null,
      "change_kind": "version-fact",
      "introduced_in": "6.8.0",
      "introduced_on": "2025-05-15",
      "chargeable": true,
      "chargeable_note": "Anchored to 6.8.0 (2025-05-15), the first release the subject says it knows only as a number. Twenty-five further releases up to 7.2.0 (2025-12-17) precede the stated 2026-01 cutoff.",
      "model_belief": "\"The most recent release whose contents I can actually describe with confidence is roughly 6.7 (around May 2025) ... First release I know essentially only as a version number, with no real idea of its contents: around 6.8 onward. I believe 6.8-6.16 exist, but I can't describe them individually with any confidence.\"",
      "impact": "This is the finding that breaks the Index's own four-library result. On zod, Next.js, Tailwind and LangChain this model's boundary fell inside 2025-10-22 to 2025-11-24; on Prisma it falls six months earlier, so no single date explains all five libraries for this subject. See JOURNAL/015.",
      "citations": [
        {
          "url": "https://registry.npmjs.org/prisma",
          "title": "npm registry metadata for `prisma` (time map)",
          "quote": "6.8.0: 2025-05-15"
        },
        {
          "url": "https://github.com/prisma/prisma/releases/tag/6.7.0",
          "title": "Prisma 6.7.0 release notes — Prisma ORM without Rust engines (Early Access)",
          "published_on": "2025-04-29",
          "quote": "we're currently working on moving the core of Prisma from Rust to TypeScript"
        }
      ]
    }
  ],
  "non_findings": [
    {
      "kind": "correct",
      "summary": "Its release history is accurate where it claims confidence: 6.7 as the Rust-free/queryCompiler preview (published 2025-04-29), 6.6 as the ESM `prisma-client` generator plus D1 and MCP work (2025-04-08), 6.2 as `omit` going GA (2025-01-07), 6.1 as tracing (2024-12-17). Four correct attributions, dated within days.",
      "api": null
    },
    {
      "kind": "correct",
      "summary": "The Dockerfile runs `npx prisma generate` explicitly rather than trusting the postinstall hook, and says why: \"if you prune or re-install prod deps in the runtime stage, you must re-run prisma generate\". The removal of implicit generation does not break this artefact.",
      "api": "postinstall prisma generate",
      "introduced_in": "7.0.0",
      "why_not_a_finding": "Correct on 7.x by construction, though for a v6 reason."
    },
    {
      "kind": "miss",
      "summary": "The serverless answer names the `prisma-client` generator with a required `output` outside `node_modules` as the modern path, and question (d) describes `prisma.config.ts`, `defineConfig` from `prisma/config`, the seed moving out of `package.json`, and the loss of automatic `.env` loading — every one of which is a 7.0.0 fact.",
      "api": "prisma.config.ts",
      "chargeable_miss": false,
      "why_not_a_finding": "All of it is reachable from 6.6/6.7, where these landed as early access — the subject frames them as previews rather than defaults, which is exactly right for 6.7 and exactly wrong for today. The boundary shows as an unfinished trajectory rather than an absence."
    }
  ],
  "open_questions": [],
  "summary": "Thirteen findings, and the result that matters is the last one. Fable 5's Prisma knowledge stops at 6.7.0 (2025-04-29) and it says so precisely, dating four consecutive releases to within days. That is six months earlier than the same model's boundary on zod, Next.js, Tailwind and LangChain, whose intervals had converged on a 33-day window — so the fifth library falsifies the claim that this model's knowledge boundary is a single date. The code it wrote is a coherent 6.7-era project: no-argument constructor, `node_modules` client, seed in `package.json`, engine binaries matched to the container's libc. It knows the Rust-free client, the `prisma-client` generator and `prisma.config.ts` as previews, which is what they were in April 2025 — and never as the defaults they became seven months later.",
  "markdown": "data/prisma/fable-5.md"
}