{
  "$schema": "../../schema/run.schema.json",
  "run_id": "prisma--claude-sonnet-5--v6-b--2026-09-12",
  "supersedes": null,
  "replicate_of": "prisma--claude-sonnet-5--v6-a--2026-09-12",
  "library": {
    "name": "prisma",
    "ecosystem": "npm",
    "latest_version_at_test": "7.10.0",
    "latest_version_verified_on": "2026-09-12",
    "latest_version_note": "The battery targets prisma LF39 — `generator client { engineType }`, filed the same day (JOURNAL/164) with nothing charged against it. Its window is [6.16.0, 7.0.0) and its charge is at 7.0.0. Every surface the tasks touch was re-driven this session before the prompt was written, on the bisector's 31-rung ladder (one release per directory, resolved alone): `engineType = \"client\"` builds a client differing from the default only on 6.16.0-6.19.0, and from 7.0.0 emits the identical file set to omitting the key; the whole of TASK 3's block generates on 7.10.0 (exit 0, nine files, the same nine the default writes) with one warning, `Preview feature \"queryCompiler\" is deprecated. The functionality can be used without specifying it as a preview feature.`; and `engineMode` — TASK 3's same-scheme invented sibling — is a key prisma ships at no release, accepted silently and emitting the default file set at every rung where the generator exists. That last measurement is new and is now LF39h, INVARIANT on all 31 rungs by the committed bisector."
  },
  "model": {
    "id": "claude-sonnet-5",
    "label": "Claude Sonnet 5",
    "vendor": "Anthropic",
    "invoked_as": "Agent tool, model alias \"sonnet\"; the same stored file as v6-a, sent blind and concurrently. The born-duplicated second draw, non-charging by pre-registration.",
    "self_reported_cutoff": "2026-01",
    "cutoff_basis": "Self-reported and attributed to the harness, as v6-a's was: \"I'm told my training cutoff is January 2026, though my confident, detailed knowledge of Prisma's changelog effectively thins out well before that.\" The two draws agree on the figure and on the qualification.",
    "believed_latest_version": null,
    "believed_latest_quote": "\"I know the Prisma 6 line existed and progressed well through 2025 … and I have a vague, unconfirmed sense that a Prisma 7 major version was being discussed/planned. I cannot respond with confidence on which specific version is 'latest' as of now.\"",
    "knowledge_stops_at_version": "6.0.0",
    "knowledge_stops_on": "2024-11-28",
    "knowledge_gap_starts_at_version": "6.1.0",
    "knowledge_gap_starts_on": "2024-12-17",
    "boundary_note": "Unambiguous and much lower than its twin's: \"6.1.0 onward is effectively where I go from 'recall' to 'guessing,' and I'd call 6.1.0 the first release I know only as a version number.\" v6-a placed the same subject's boundary six minors higher on the same prompt in the same hour — the instrument spread this battery's duplicate exists to measure, and it is 155 days and six releases wide.",
    "cutoff_lag_months": 14
  },
  "test": {
    "date": "2026-09-12",
    "battery": "prisma/v6-b",
    "battery_spec": "prompts/prisma.md",
    "prompt_file": "prompts/sent/prisma-v6.txt",
    "tasks": 4,
    "direct_questions": 4,
    "elicits_code": true,
    "tool_uses_during_test": 0,
    "probe_window": {
      "from": "6.16.0",
      "to": "7.10.0"
    },
    "self_test": false,
    "saturated": false,
    "status": "open",
    "retested_on": null
  },
  "sources": [
    "https://github.com/prisma/prisma/releases/tag/6.16.0",
    "https://github.com/prisma/prisma/releases/tag/7.0.0",
    "https://registry.npmjs.org/prisma"
  ],
  "findings": [],
  "non_findings": [
    {
      "kind": "miss",
      "summary": "Reproduces v6-a's charged belief, independently and in the same words: TASK 2(a) \"Yes\", and \"`previewFeatures = [\\\"queryCompiler\\\", \\\"driverAdapters\\\"]` — the actual switch. `queryCompiler` turns on the TypeScript/WASM query planner instead of the Rust binary\". At TASK 3 it keeps the line — \"still real as far as I know, and still the actual switch\".",
      "api": "previewFeatures = [\"driverAdapters\"]",
      "introduced_in": "6.16.0",
      "chargeable_miss": true,
      "miss_class": "non_charging_arm",
      "charged_on": "prisma--claude-sonnet-5--v6-a--2026-09-12",
      "why_not_a_finding": "The replicate arm charges nothing (HARNESS.md § Replicates). The failure is already carried by v6-a as F1; counting it twice would inflate the dataset. Recorded with chargeable_miss so the pair reads as two independent reproductions of one belief rather than one."
    },
    {
      "kind": "context",
      "summary": "THE PAIR DISAGREES ON A ONE-WORD VERDICT. TASK 3(a): v6-a said \"No\", this draw said \"Yes\" — and this draw is right, with the right mechanism: \"Prisma's generator-block parsing is lenient about keys it no longer recognizes for a given provider — it does not hard-fail generation over `engineType`/`engineMode` being present.\" Measured true on 31 rungs this session (LF39e, LF39h).",
      "chargeable_miss": false,
      "why_not_a_finding": "A disagreement between two blind draws of one stored prompt is evidence about the instrument, not about the library. It is the fifth quantity in this battery on which the pair splits, and the only one where a single draw would have published a false verdict as the subject's answer."
    },
    {
      "kind": "correct",
      "summary": "TASK 1 omits the preview flag deliberately and says why: \"I'm deliberately *not* putting `previewFeatures = [\\\"driverAdapters\\\"]` in there … driver adapters graduated out of preview into general availability partway through the Prisma 6 line.\" The same split as v6-a — TASK 1 correct, TASK 2 stale — reproduced.",
      "api": "previewFeatures = [\"driverAdapters\"]",
      "chargeable_miss": false
    },
    {
      "kind": "correct",
      "summary": "Catches the invented sibling: \"`engineMode = \\\"wasm\\\"` … I don't have confident memory of `engineMode` being a documented, currently-effective key.\" Declines TASK 4 outright rather than naming a release, and declines all four cells of direct (d) including the poison rung 6.22.0.",
      "chargeable_miss": false
    },
    {
      "kind": "context",
      "summary": "The clearest statement in the battery that a subject reads the WHOLE prompt before answering any of it: at direct (d) this arm says it knows 6.16.0 \"only because it's the baseline named in Task 3's prompt … that tells me roughly what a 6.16-era compiler-client preview schema looked like, but I can't independently recall 6.16.0's changelog beyond what's given to me here.\"",
      "chargeable_miss": false
    }
  ],
  "open_questions": [],
  "summary": "The non-charging twin, and it holds the better answer on the one verdict the pair splits on — TASK 3(a), where it says the stale block generates and gives the correct reason. It reproduces v6-a's charged belief about the preview flags word for word, which is what makes that charge a belief rather than a draw. It also places this subject's own describable boundary at 6.0.0 where its twin placed it around 6.7.0, on a byte-identical prompt in the same hour: 155 days apart."
}