Start a run (render + verify)
Start one augmentation run job over the saved sample + plan: mine pairs from the selected episodes, compose, render (real GPU spend), and gate every candidate. Returns the job id, poll GET /api/aug/jobs/{job_id}.
Playground precise-splice path: pass pairs (records returned VERBATIM by …/episodes//partners or …/proposals) and the explicit pairs REPLACE the sample/plan requirement, the chosen pairs ARE the selection. Only the first 8 records are used; each is re-validated (integer A/B in range, every numeric field present and in bounds), so a forged record is rejected 400.
Refused while health is recomputing after a target switch (409, so a run always reflects the settled target); when the plan’s transforms don’t run in the workbench yet (object swap / environment restyle , 400 until New trajectories is added); and when new-trajectory is not READY for this dataset per the …/transforms catalog, e.g. the target class is not certified (400 with the specific missing step). Fail-closed: if readiness cannot be evaluated the run does not start (503).
Authorizations
Either a Supabase user access token (from a password login, or the passwordless magic-link flow) or a long-lived forge_sk_… API key. Both are sent as Authorization: Bearer <value> and resolve to the same owner, so every endpoint accepts either. Session tokens expire in ~1h; API keys do not expire and are the credential for MCP clients, CI, and partner integrations.
Path Parameters
Body
Explicit pair records (send /partners or /proposals records verbatim). Replaces the sample+plan path; only the first 8 are used.
Response
Run started.
"aug_9f8e7d6c5b4a"

