Test plans from a coding AI

A test plan settles what to test before the tests are written: the agent's main tasks, what must never happen, the attack template, the test accounts and data. That step was removed: the web's plan page (the rounds of questions that used to start an empty project, and its approve button) is gone, and its old address opens the datasets list; a coding AI connected to the project can't start or change a plan either. To have AI write a dataset, use "Generate a dataset with AI" on the datasets list, or "Generate rows with AI" on a dataset (datasets); for a sandbox project's scenarios, Datasets → "All tests (detailed list)" → "Let AI draft your tests" (scenarios and test sets); a coding AI writes them from get_prompt (the loop and the tools).

A plan approved before still holds: a coding AI reads it in full with get_plan, and the prompts from get_prompt and "Let AI draft your tests" carry it. The five tools that made plans (start_plan, answer_plan, next_plan_round, write_plan, edit_plan) are still there, and only answer the error plan_removed with what to do instead (see the test plan tools).

The routes: GET /v1/dev/plan reads the plan approved before; the ones on /v1/dev/plan that started, answered, moved on, wrote and edited a plan answer 410 plan_removed (dev AI routes).