| Primary job | Submit an iOS or Android build with store policy, privacy, review, and test-track evidence | Prove that a service, model, tool, API, and data path work in the intended production environment |
| Input | Framework, stores, release type, and product features; app name and version are optional | A state and short evidence note for each gate; never paste tokens, secrets, or personal data |
| Output | Conditional Markdown release checklist | Markdown readiness report with an explicit verdict |
| Best for | Flutter and cross-platform developers, indie makers, and release owners | Agent engineers, product owners, SREs, and deployment reviewers |