{
  "schemaVersion": 1,
  "slug": "shot-manifest-file-binding",
  "locale": "en",
  "evidenceClass": "executed-local-fixture-not-provider-generation",
  "providerModelTest": false,
  "productionTaskRun": false,
  "runCommand": "node run-recipe.mjs --out ./my-run",
  "environment": {
    "nodeVersion": "v24.18.0",
    "ffmpeg": null
  },
  "title": "Bind shot identity, file, hash and editorial order in one manifest",
  "description": "Validate three original shot records and reject duplicate IDs, reordered rows, swapped files, missing downloads and wrong identity even after a hash is rebound.",
  "goal": "Keep shotId, exact filename, SHA-256 and order consistent before assembly. These checks establish file identity and sequence, not visual continuity or the quality of generated footage.",
  "preparation": [
    "Use Node.js with built-in filesystem and crypto modules. The three original one-second shot specifications are opening, hinge and hold; no media provider is contacted.",
    "Read shot-manifest.json together with the JSON files in shots/. Each file carries its own shotId in addition to the external manifest binding.",
    "Choose a fresh output directory and require order values 1–3 to match row position. Basenames are local and unique; parent paths and duplicated filenames are not allowed."
  ],
  "steps": [
    {
      "title": "01. Define identities independently from filenames",
      "body": "The fixture writes three distinct shot JSON files and a manifest with shotId, order, file and sha256. The editorial identity is opening/hinge/hold, while the basenames are shot-01.json through shot-03.json. This distinction lets a renamed file remain a separate reviewed decision."
    },
    {
      "title": "02. Validate order and uniqueness first",
      "body": "Check the exact row count, unique shot IDs, sequential order values and unique safe filenames. A duplicate ID is a failure even when its bytes can be opened; a reordered manifest is not silently sorted into a different editorial sequence."
    },
    {
      "title": "03. Check both file bytes and internal shot identity",
      "body": "Require the file to exist, its SHA-256 to match and its internal shotId to equal the manifest. The suite swaps a filename while keeping the original hash, then rebinds the hash to the wrong shot as a separate case. The second case still fails identity binding."
    },
    {
      "title": "04. Preserve the failed bindings for review",
      "body": "Inspect eight assertions and six expected-rejection records. A missing shot, duplicate ID, wrong order, swapped filename, wrong internal identity and duplicated file each retain a concrete failure reason. Use a separate video review for action and continuity."
    }
  ],
  "acceptance": [
    "The valid three-row manifest passes without reordering its records.",
    "opening, hinge and hold are three unique shot identities.",
    "A duplicate shot ID and a reordered row are separately rejected.",
    "A filename swap fails the original SHA-256 binding.",
    "A missing file and a duplicate filename are rejected.",
    "Even after rebinding the swapped file’s hash, its wrong internal shotId is rejected; all eight checks pass."
  ],
  "troubleshooting": [
    {
      "symptom": "A readable file is attached to the wrong shot.",
      "change": "Correct the file-to-shotId binding and recheck its internal identity. Regenerating a hash alone cannot repair the editorial mismatch."
    },
    {
      "symptom": "Two rows use one shot ID.",
      "change": "Assign the intended distinct shotId to the incorrect record and its file content, then recompute only that file’s expected hash."
    },
    {
      "symptom": "The sequence changes after download.",
      "change": "Use the manifest order values as the handoff contract and reject row-position disagreement; do not substitute alphabetical file sorting."
    }
  ],
  "ending": "The manifest makes the three shot specifications reviewable as a package. It does not inspect footage, enforce narrative meaning or demonstrate any video model run.",
  "assetCaption": "Original shot specification JSON files, actual binding failures and a shot-to-file matrix diagram. Standard-library execution only."
}