{
  "$schema": "../../schema/run.schema.json",
  "run_id": "prisma--claude-haiku-4-5--v5-g--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.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-haiku-4-5",
    "label": "Claude Haiku 4.5",
    "vendor": "Anthropic",
    "invoked_as": "Agent tool, model alias \"haiku\"; prompt sent verbatim from prompts/sent/prisma-v5.txt. The below-floor derivability control, declared NON-CHARGING in the spec before spawning.",
    "self_reported_cutoff": "2025-02",
    "cutoff_basis": "Self-reported: \"Training cutoff: February 2025.\" Ten months below 7.2.0 and eleven below 7.3.0, so every probe in this battery is outside its window by design. Stable across every battery this subject has run in.",
    "believed_latest_version": null,
    "believed_latest_quote": "\"The latest version I'm aware of is in the 5.x line, possibly 5.13 or 5.14, but I'm not certain of the exact patch.\"",
    "knowledge_stops_at_version": null,
    "knowledge_stops_on": null,
    "knowledge_gap_starts_at_version": null,
    "knowledge_gap_starts_on": null,
    "cutoff_lag_months": null
  },
  "test": {
    "date": "2026-09-06",
    "battery": "prisma/v5-g",
    "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 the push and migrate commands — and this is the result that falsifies prediction P1.",
      "api": "prisma db push --url",
      "introduced_in": "7.2.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": null,
      "why_not_a_finding": "Reproduced but not charged: this is the below-floor derivability control, declared non-charging in the spec before spawning. Claude Haiku 4.5 states a 2025-02 cutoff, ten months before 7.2.0, so a denial here is fair and expected — its value is that it says whether the probe was guessable, not whether the subject is stale."
    },
    {
      "kind": "miss",
      "summary": "Denies the first-party SQLCommenter plugin and is unsure whether Prisma middleware can reach the SQL at all.",
      "api": "@prisma/sqlcommenter-query-insights",
      "introduced_in": "7.2.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": null,
      "why_not_a_finding": "Reproduced but not charged: this is the below-floor derivability control, declared non-charging in the spec before spawning. Claude Haiku 4.5 states a 2025-02 cutoff, ten months before 7.2.0, so a denial here is fair and expected — its value is that it says whether the probe was guessable, not whether the subject is stale."
    },
    {
      "kind": "miss",
      "summary": "Denies `compilerBuild` and rejects both options in TASK 4 as \"aspirational rather than real\".",
      "api": "compilerBuild",
      "introduced_in": "7.3.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": null,
      "why_not_a_finding": "Reproduced but not charged: this is the below-floor derivability control, declared non-charging in the spec before spawning. Claude Haiku 4.5 states a 2025-02 cutoff, ten months before 7.2.0, so a denial here is fair and expected — its value is that it says whether the probe was guessable, not whether the subject is stale."
    },
    {
      "kind": "context",
      "summary": "The control produced no boundary this Index can record: it names 5.13/5.14 as the latest it knows of, then names \"anything in the 5.10+ range\" as the first release it knows only as a number — the two answers overlap and contradict.",
      "chargeable_miss": false,
      "why_not_a_finding": "Not a claim about a release. Recorded because BACKLOG 11k-b asked for this subject's prisma boundary and this instrument cannot supply it: the answers are mutually inconsistent and both fall below `data/prisma/releases.json`'s coverage floor of 5.15.0. The `?` in the sweep's prisma column for Claude Haiku 4.5 stays a `?`."
    }
  ],
  "open_questions": [],
  "summary": "The below-floor derivability control, and it did the one job a control exists for: it said no. Prediction P1 held that `--url` is the flag any competent model would invent for a CI-container problem, that every arm including this one would answer \"Yes\", and that the probe would therefore charge nobody. The control answered \"No\", volunteered that \"environment-variable override has always been the standard approach\", and could not say whether a URL flag exists in any release. Four of the seven arms denied the same thing. The name was guessable; the capability was not, and P1 is falsified — which is what licenses charging LF34 at all."
}