Reference table
| Page | Why it matters |
|---|---|
| Render screenshots | The primary POST endpoint for generating assets |
| Async renders | Large matrices without holding CI runners open |
| Screenshot lint report | Machine-readable review findings |
| Fastlane ZIP output | Store-ready folder structure for deliver |
| Webhooks | Signed completion events |
| Idempotency keys | Safe retries from CI and agents |
APIs before editors
Each reference page links to adjacent release workflows so a developer, CI job, or coding agent can move from concept to a concrete API call without dead ends.