{
  "$schema": "../../schema/run.schema.json",
  "run_id": "prisma--claude-fable-5-1--v5-f--2026-09-06",
  "supersedes": null,
  "replicate_of": "prisma--claude-fable-5-1--v5-e--2026-09-06",
  "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.2.0 (2025-12-17) with one 7.3.0 (2026-01-21) surface folded in. All three surfaces were pinned to an exact introducing release before any probe was written, by installing the shipped CLI at 5.22.0, 6.19.0, 7.0.0, 7.1.0, 7.2.0 and 7.3.0 in the session scratchpad and reading the help tables and the bundle. `--url` is absent from `prisma db push --help`, `db pull --help` and `migrate dev --help` at 5.22.0, 6.19.0, 7.0.0 and 7.1.0, and present on all three at 7.2.0. `@prisma/sqlcommenter-query-insights` has 7.2.0 (2025-12-17) as its first stable registry release. The string `compilerBuild` is absent from prisma@7.2.0 build/index.js and present in prisma@7.3.0. `clientCompression`, the invented sibling in TASK 4, exists at no version. One 7.2.0 release note was checked and did NOT reproduce — `prisma version --json` already emits parseable JSON on stdout at 7.1.0 — so no fact was written from it."
  },
  "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-v5.txt. The replicate of the Fable 5.1 pair, declared non-charging in the spec before spawning. Same alias and same identity probe as `v5-e`.",
    "self_reported_cutoff": "2026-06",
    "cutoff_basis": "Self-reported and AFFIRMING: \"My training cutoff is stated to me as June 2026, but my detailed knowledge of Prisma releases thins out noticeably after about early 2026.\" Same value and frame as `v5-e`.",
    "believed_latest_version": "7.2",
    "believed_latest_quote": "\"The latest line I know of is Prisma 7.x. The most recent release whose contents I can genuinely describe is roughly Prisma 7.2, from around January 2026.\"",
    "knowledge_stops_at_version": "7.2.0",
    "knowledge_stops_on": "2025-12-17",
    "knowledge_gap_starts_at_version": "7.3.0",
    "knowledge_gap_starts_on": "2026-01-21",
    "cutoff_lag_months": 6
  },
  "test": {
    "date": "2026-09-06",
    "battery": "prisma/v5-f",
    "battery_spec": "prompts/prisma.md",
    "prompt_file": "prompts/sent/prisma-v5.txt",
    "tasks": 5,
    "direct_questions": 3,
    "elicits_code": true,
    "tool_uses_during_test": 0,
    "probe_window": {
      "from": "7.2.0",
      "to": "7.3.0"
    },
    "self_test": true,
    "saturated": false,
    "status": "open",
    "retested_on": null
  },
  "sources": [
    "https://github.com/prisma/prisma/releases/tag/7.2.0",
    "https://github.com/prisma/prisma/releases/tag/7.3.0",
    "https://registry.npmjs.org/@prisma/sqlcommenter-query-insights",
    "https://registry.npmjs.org/prisma/-/prisma-5.22.0.tgz",
    "https://registry.npmjs.org/prisma/-/prisma-6.19.0.tgz",
    "https://registry.npmjs.org/prisma/-/prisma-7.0.0.tgz",
    "https://registry.npmjs.org/prisma/-/prisma-7.1.0.tgz",
    "https://registry.npmjs.org/prisma/-/prisma-7.2.0.tgz",
    "https://registry.npmjs.org/prisma/-/prisma-7.3.0.tgz"
  ],
  "findings": [],
  "non_findings": [
    {
      "kind": "miss",
      "summary": "Denies `--url` on `db push` and the `migrate` commands, at \"moderate confidence\", and names `db pull --url`, `db execute --url` and `migrate diff --from-url` as the real ones.",
      "api": "prisma db push --url",
      "introduced_in": "7.2.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v5-e--2026-09-06",
      "why_not_a_finding": "Reproduced but not charged: this is the replicate arm of its pair, and only the arm nominated in `prompts/prisma.md` § v5 before spawning may charge."
    },
    {
      "kind": "miss",
      "summary": "Denies the first-party SQLCommenter plugin: \"Prisma ships no SQLCommenter package or plugin ... Google's sqlcommenter project has adapters for Knex, Sequelize and pg, but nothing for Prisma.\"",
      "api": "@prisma/sqlcommenter-query-insights",
      "introduced_in": "7.2.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-fable-5-1--v5-e--2026-09-06",
      "why_not_a_finding": "Reproduced but not charged: this is the replicate arm of its pair, and only the arm nominated in `prompts/prisma.md` § v5 before spawning may charge."
    },
    {
      "kind": "correct",
      "summary": "Answered TASK 3 \"Yes\" and described `compilerBuild` correctly — two builds of the WASM query compiler, values \"fast\" (default) and \"small\", associated with the serverless/edge bundle-size story — then used it in the generator block it shipped.",
      "api": "compilerBuild",
      "introduced_in": "7.3.0",
      "chargeable_miss": false,
      "why_not_a_finding": "Correct, and stronger than its twin: an unhedged \"Yes\" with the default value identified. Both Fable 5.1 arms independently produced this option, which rules out a single lucky draw and makes the pass a property of the subject rather than of the sample."
    }
  ],
  "open_questions": [],
  "summary": "The Fable 5.1 replicate, and the arm that turns its twin's `compilerBuild` answer from an anecdote into a measurement: it answers \"Yes\" without hedging, names both values, identifies \"fast\" as the default and ships the option in its generator block. Two independent draws of one subject producing a 7.3.0 option is not a lucky guess. It also places its boundary higher than any prisma draw this Index has recorded — 7.2.0 describable, 7.3.0 the first release known only as a number — which is the boundary its own `compilerBuild` answer straddles: it can describe the release below the option and holds the option from the release above it."
}