{"version":"2.1.251","anchor":"tooling-to-adopt-recorded-mock-responses-into-a-replay-direc","canonical_anchor":"tooling-to-adopt-recorded-mock-responses-into-a-replay-direc","heading":"Tooling to adopt recorded mock responses into a replay directory","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/tooling-to-adopt-recorded-mock-responses-into-a-replay-direc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Tooling to adopt recorded mock responses into a replay directory\n\nEval tooling can adopt recorded mock responses into a checksummed replay directory.\n\n**What**\n\nInternal eval tooling can now take newly recorded MCP mock server responses from a run and adopt them into a `.replay\/` directory, with a manifest file and per-file sha256 hashes so a copy can be checked, and guards against another process writing at the same time.\n\n**Details**\n\n- Developer and eval tooling only; nothing here is reachable from a normal session.\n\n**Evidence**\n\n`Each line carries the sha256 of the file as written; check the copy you take against the hash printed to the terminal`\n\n- Area: Plugin Eval\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}