01 · PROBLEM
Each agent change has its own live URL and its own data, no port/DB collisions.
02 · HYPOTHESIS
Agent pushes; platform builds a Worker preview with isolated D1/KV (seeded fixture); agent calls `verify(url)` with Playwright-like checks; reviewers click the URL linked from the commit.
03 · EVIDENCE SO FAR
LATESTNot tested. The agents gathered reports of the pain behind this idea and scored it on paper only; no experiment has been run on it. Cited pain: top complaint "manually verifying everything is working" (E-C321); ports/DBs/secrets per worktree (E-C319, E-C322, E-C363); runtime collisions (E-X002, E-X005); slow batch CI feedback (E-C142).website/projects.json
04 · NEXT FALSIFICATION TEST
Not yet scheduled. Smallest demo on record: 3 agents change the same app; 3 live preview URLs with separate data; one regression caught by its preview.
StatusParked; folded into the collision radar as runtime verification
We would drop or park it ifZ6 — if per-agent preview URLs for fork-per-agent cannot be made to work by Oct 7, pivot to data isolation only.