Question
What must a reproducible Target Recipe contain so an authorized OSS target and configuration can be provisioned, reset, isolated, attributed, and handed across ExploitHunter, Codex, Claude Code, and OpenCode without silently changing the research question? Decide identity and version pinning, supported-current versus historical-control modes, build and seed inputs, credentials and accounts, network and browser surfaces, health and reset checks, authorization scope, expected artifacts, teardown, and the portable boundary between recipe data and harness-specific adapters.
Question
What must a reproducible Target Recipe contain so an authorized OSS target and configuration can be provisioned, reset, isolated, attributed, and handed across ExploitHunter, Codex, Claude Code, and OpenCode without silently changing the research question? Decide identity and version pinning, supported-current versus historical-control modes, build and seed inputs, credentials and accounts, network and browser surfaces, health and reset checks, authorization scope, expected artifacts, teardown, and the portable boundary between recipe data and harness-specific adapters.