The OpenAPI document describes mirroring and forking from an origin, its job and stream, and origin apps #5152

Intent: an agent can follow a migration from an origin to the end through the OpenAPI document alone.

Done:

• [ ] Rows for POST /api/v1/user/origins/{id}/mirror and …/fork, GET /api/v1/user/origins/{id}/mirror/{job} and …/mirror/{job}/stream, GET /api/v1/migrate/{job}/stream, and GET, POST and DELETE /api/v1/user/origin-apps (DELETE takes {id}). The stream rows say they answer text/event-stream and name the events they send
• [ ] Each row has auth, body and query fields, its success status and its refusals as its handler has them
• [ ] Placed as one block directly after the ${REPO}/origin/reconnect row, changing no other row
• [ ] test/openapi.test.ts still passes, and a new test asserts each new path and method is in the served document

Parked by the crew: the check failed ("no method and path is described twice, so no row is dead") and the decider saw no point in another try (pull #5169 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.