Turn Flutter release readiness into a traceable go/no-go decision. Stop running mobile releases from memory, chat messages, and a last-minute “looks good to me.” Mobile Release Ops Kit is an evidence-first operating system for small Flutter teams shipping to Google Play and the Apple App Store. It tells you what to verify, who needs to decide, what evidence to save, and when a release must remain blocked. INSIDE THE CORE EDITION • 64-control master checklist across scope, app identity, environments, permissions, privacy, signed builds, testing, store metadata, reviewer access, launch monitoring, and closure • Release evidence ledger with owner, status, timestamp, and proof fields • Google Play + App Store listing worksheet with a claims ledger and cross-store consistency gate • Data-practices inventory for first-party code and third-party SDKs • Review-notes template for access, non-obvious features, permissions, and purchases • Go/no-go decision record that refuses to treat blanks or intent as approval • Incident and rollback runbook with app-specific thresholds and communications • Eight safe AI prompts for evidence, copy, privacy consistency, reviewer notes, tests, decisions, and incident review • Secret-free Flutter CI starter for formatting, analysis, and tests • Fictional completed example, customer license, changelog, and current official source register • Editable files plus a print-friendly PDF workbook DESIGNED FOR Solo developers, agencies, and small teams that need a dependable release ritual and clear separation between technical readiness and owner approval. THE EVIDENCE-FIRST DIFFERENCE PASS means reproducible evidence tied to the exact release build. Missing proof stays missing. Product, privacy, policy, legal, pricing, and account decisions stay visibly assigned to a human owner. FORMAT Markdown, CSV, YAML, TXT, and PDF. No proprietary project-management tool required. IMPORTANT BOUNDARY This kit is not a full code or security audit, legal advice, platform certification, or a guarantee of review acceptance, ranking, revenue, uptime, or compliance. Your team remains responsible for the app, declarations, embedded SDKs, current agreements, and release decisions. Official source links were verified July 19, 2026 and should be re-checked before every submission.