{
  "$schema": "../../schema/run.schema.json",
  "run_id": "prisma--claude-fable-5-1--v4-d--2026-09-06",
  "supersedes": null,
  "replicate_of": null,
  "library": {
    "name": "prisma",
    "ecosystem": "npm",
    "latest_version_at_test": "7.10.0",
    "latest_version_verified_on": "2026-09-06",
    "latest_version_note": "The probe window is 7.5.0 (2026-03-11) to 7.8.0 (2026-04-22). Every one of the six surfaces in this battery was pinned to an exact introducing release by installing the shipped packages at 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.8.0 and 7.10.0 in the session scratchpad and reading the published type declarations and the CLI command table. `postgres` is absent from `prisma --help` at 7.5.0 and present at 7.6.0; `bootstrap` is absent at 7.6.0 and present at 7.7.0; the `PrismaPg` constructor union gains `| string` between 7.5.0 and 7.6.0; `statementNameGenerator` appears in `PrismaPgOptions` between 7.5.0 and 7.6.0; `queryPlanCacheMaxSize` appears in the client options between 7.7.0 and 7.8.0; and `\"$transaction\"` leaves the interactive-transaction deny list between 7.4.0 and 7.5.0. All six persist at 7.10.0. `prisma postgres branch`, the poison rung, does not exist at any of those versions — `prisma postgres --help` lists `link` and nothing else."
  },
  "model": {
    "id": "claude-fable-5-1",
    "label": "Claude Fable 5.1",
    "vendor": "Anthropic",
    "invoked_as": "Agent tool, model alias \"fable\"; prompt sent verbatim from prompts/sent/prisma-v4.txt, spawned as a concurrent blind draw alongside `v4-c`. Pre-registered as the NON-CHARGING twin.",
    "self_reported_cutoff": "2026-06",
    "cutoff_basis": "Self-reported, AFFIRMING: \"the context I'm running in states \\\"June 2026.\\\" From my own internal sense, my solid knowledge thins out around late 2025 / very early 2026, so I'd treat the June 2026 date as coming from my context rather than from anything I can verify from my own knowledge.\" Density caveat, not a substitute cutoff. Same deviation note as `v4-c`.",
    "believed_latest_version": "7.1/7.2",
    "believed_latest_quote": "\"I have only hazy awareness of early 7.x minors (7.1/7.2-ish) and cannot name the most recent 7 minor with confidence — I won't guess a number.\"",
    "knowledge_stops_at_version": "7.0.0",
    "knowledge_stops_on": "2025-11-19",
    "knowledge_gap_starts_at_version": "7.1.0",
    "knowledge_gap_starts_on": "2025-12-03",
    "cutoff_lag_months": 7
  },
  "test": {
    "date": "2026-09-06",
    "battery": "prisma/v4-d",
    "battery_spec": "prompts/prisma.md",
    "prompt_file": "prompts/sent/prisma-v4.txt",
    "tasks": 7,
    "direct_questions": 4,
    "elicits_code": true,
    "tool_uses_during_test": 0,
    "probe_window": {
      "from": "7.5.0",
      "to": "7.8.0"
    },
    "self_test": false,
    "saturated": false,
    "status": "open",
    "retested_on": null
  },
  "sources": [
    "https://github.com/prisma/prisma/releases/tag/7.5.0",
    "https://github.com/prisma/prisma/releases/tag/7.6.0",
    "https://github.com/prisma/prisma/releases/tag/7.7.0",
    "https://github.com/prisma/prisma/releases/tag/7.8.0",
    "https://registry.npmjs.org/prisma",
    "https://registry.npmjs.org/@prisma/client",
    "https://registry.npmjs.org/@prisma/adapter-pg"
  ],
  "findings": [],
  "non_findings": [
    {
      "kind": "miss",
      "summary": "TASK 1(i) \"No\", and: \"The only \\\"provisioning\\\" command I know of is `prisma init --db`, which creates a *new* database; attaching to an existing one is just configuration.\" Direct question (c)(i): \"does not exist in the Prisma CLI, as far as I know.\"",
      "api": "prisma postgres link",
      "introduced_in": "7.6.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v4-c--2026-09-06",
      "why_not_a_finding": "The blind twin, pre-registered as non-charging before either draw returned. The same failure is charged as F1 on `v4-c`."
    },
    {
      "kind": "miss",
      "summary": "TASK 2(i) \"No (not that I know of)\", and TASK 7(b): \"`queryPlanCacheMaxSize` is not a `PrismaClient` constructor option I know of, and since the options object is strictly typed, the unknown key fails as an excess property (if a 7.x minor after my knowledge added such an option, I can't confirm it).\" The parenthesis is the only hedge of its kind across the four test draws.",
      "api": "queryPlanCacheMaxSize",
      "introduced_in": "7.8.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v4-c--2026-09-06",
      "why_not_a_finding": "The blind twin, pre-registered as non-charging before either draw returned. The same failure is charged as F2 on `v4-c`."
    },
    {
      "kind": "miss",
      "summary": "TASK 3(i) \"No\", and TASK 7(a): \"`PrismaPg` expects `{ connectionString }` (a `pg.PoolConfig`); a bare string is a type error, and at runtime `pg.Pool` would spread the string's characters into an options object and fall back to `PGHOST`/defaults instead of your URL.\"",
      "api": "new PrismaPg(connectionString)",
      "introduced_in": "7.6.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v4-c--2026-09-06",
      "why_not_a_finding": "The blind twin, pre-registered as non-charging before either draw returned. The same failure is charged as F3 on `v4-c`."
    },
    {
      "kind": "miss",
      "summary": "TASK 4(i) \"No\", and: \"it issues queries via node-postgres's extended protocol as unnamed statements and exposes no naming option.\"",
      "api": "statementNameGenerator",
      "introduced_in": "7.6.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v4-c--2026-09-06",
      "why_not_a_finding": "The blind twin, pre-registered as non-charging before either draw returned. The same failure is charged as F4 on `v4-c`."
    },
    {
      "kind": "miss",
      "summary": "TASK 5(i) \"No\", and: \"`Prisma.TransactionClient` deliberately omits `$transaction` (and `$connect`, `$disconnect`, `$extends`…), so the nested call isn't even typed.\"",
      "api": "tx.$transaction()",
      "introduced_in": "7.5.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v4-c--2026-09-06",
      "why_not_a_finding": "The blind twin, pre-registered as non-charging before either draw returned. The same failure is charged as F5 on `v4-c`."
    },
    {
      "kind": "miss",
      "summary": "TASK 6(i) \"No (not that I know of)\", and: \"That's the whole path — three commands plus editing the schema.\"",
      "api": "prisma bootstrap",
      "introduced_in": "7.7.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v4-c--2026-09-06",
      "why_not_a_finding": "The blind twin, pre-registered as non-charging before either draw returned. The same failure is charged as F6 on `v4-c`."
    },
    {
      "kind": "correct",
      "summary": "Direct question (b)(iii): custom `output` since Prisma 2.0, `prisma-client` generator early access \"in 6.6.0, to the best of my recollection\", default in 7.0. Correct."
    },
    {
      "kind": "correct",
      "summary": "POISON RUNG, direct question (c)(ii). \"`prisma postgres branch` — does not exist in the Prisma CLI, as far as I know.\" Declines to assert it exists. P6 holds on this arm."
    },
    {
      "kind": "miss",
      "summary": "Direct question (c)(i) and its surrounding claim: \"I'm not aware of a `prisma postgres` subcommand group at all; the platform commands I know are under `prisma platform` (auth, workspace, project, environment, apikey, accelerate) plus `prisma init --db` and `prisma dev`.\" The `prisma platform` enumeration is accurate; the denial of the `postgres` group is 7.6.0.",
      "api": "prisma postgres link",
      "introduced_in": "7.6.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v4-c--2026-09-06",
      "why_not_a_finding": "Non-charging arm. The same surface is charged as F1 on `v4-c`."
    },
    {
      "kind": "miss",
      "summary": "Direct question (b)(i): \"I don't know of any release that introduced this; as far as I know it remains unsupported in the schema language (long-open feature request), and you'd do it in a migration by hand.\"",
      "api": "@@index(where:) / @@unique(where:)",
      "introduced_in": "7.4.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": null,
      "why_not_a_finding": "Non-charging arm, and a direct question rather than a task. Counted in the method page running total."
    }
  ],
  "open_questions": [],
  "summary": "The blind twin, charging nothing by pre-registration. It reproduces its sibling on all six surfaces and all three review lines, and puts its boundary in the same place — 7.0.0 describable, \"roughly 7.1\" as the first release known only as a number. The pair does not disagree on any verdict. Two things separate it. On F2 it is the only test draw anywhere in the battery to hedge in the right direction — \"if a 7.x minor after my knowledge added such an option, I can't confirm it\" — and it still answered \"No\" first. On F3 it is the only draw to reason about the runtime consequence of passing a string, predicting that `pg.Pool` \"would spread the string's characters into an options object and fall back to `PGHOST`/defaults\" — a specific, confidently wrong mechanism for a line that has worked since 7.6.0. Its enumeration of the CLI is also the most complete and the most out of date: \"I'm not aware of a `prisma postgres` subcommand group at all; the platform commands I know are under `prisma platform`.\""
}