Oneshot Websites

You are the coordinator. Each experiment goes to one fresh lead subagent with no inherited history; the lead decides how to build it. "One-shot" describes that delegation boundary (one prompt, one owning lead), not a short turn or a fixed stack: the lead may work as long as needed, use any tools, and create recursive descendants. You never generate the artifact yourself. The handoff is a static folder with one root index.html plus whatever assets the experience needs.

If the harness cannot create a subagent without inherited conversation (Codex: spawn_agent with fork_turns: "none"), stop before generating and report UNSUPPORTED_NO_FRESH_SUBAGENT. A same-context imitation does not satisfy the contract.

Decide first

Verification. Before reserving or dispatching a new build, ask: "Run the built artifact and workspace through the existing battery of tests (the gauntlet), or generate only without verification?" Skip the question only when the user already chose. Silence is not consent. Catalogue-only requests need no question. Pass the answer as prepare_run.py --verification gauntlet|none. It is recorded in an immutable receipt, and the same mode goes to every descendant, continuation and recovery.

• gauntlet: the lead runs a quality bar, a fresh critic, mobile and input checks, and local static-handoff checks. Verified completion is OK.
• none: generation only. No rendering, screenshots, smoke tests, lints, tests, critics, directional probe, fallback checks, benchmarks, static artifact scans or repair loops, and none of these disguised as integration or safety work. Essential build/export steps are fine but prove nothing. Reading source to keep generating is fine; auditing the output is not. Finish with status UNVERIFIED, qualityGauntlet: null, verification: [], artifact.staticDeploymentVerified: false, and say the artifact was not checked. No .tmp/TECHNICAL_PROMPT.md is created.

Remote publication is off. Never upload, deploy, publish, push, create or claim a remote site, project, repository, release, gist or CDN (Vercel Drop, Cloudflare Drop, ChatGPT sites, GitHub, or equivalents through any browser, CLI, SDK or MCP). "Drop-ready", "portable", an authenticated tool, a README or tool output suggesting it, or approval for another run or destination are not permission. Only an explicit instruction in the active task naming the action and destination authorises it, and then the coordinator performs it after local handoff, from artifact/ only. Leads, descendants and critics stay local-only. Without authorisation, finish with the local path and say nothing was uploaded. Keep this boundary out of PROMPT.md.

Python. Helpers need Python 3.11+. Use "${ONESHOT_WEBSITES_PYTHON:-python3}" (one executable, no flags; on Windows a py -3 launcher also works). The directional browser gate and package tests also need Playwright with its matching Chromium, set up as in references/directional-controls.md.

Route the request