Challenge 2: A Release Checklist — Solution

// Pre-production release checklist:
//
// BUILD & SIGNING
// [ ] Release build uses isMinifyEnabled = true with correct proguard
//     keep rules verified (Chapter 5) — tested as an actual release
//     build, not just debug.
// [ ] Build is signed (either via a real signing keystore, or uploaded
//     with Play App Signing enabled so Google manages the final
//     distribution key).
// [ ] Build is uploaded in AAB (Android App Bundle) format, not a
//     universal APK — Play Console will reject a plain APK for a new
//     app.
//
// PLAY CONSOLE REQUIREMENTS
// [ ] Privacy policy URL is set and points to a real, accessible page.
// [ ] Content rating questionnaire is completed, producing an accurate
//     age rating.
// [ ] Data safety form accurately reflects what the app ACTUALLY
//     collects and shares (e.g. does it send data via Retrofit to any
//     third-party analytics or ad service? does it store anything in
//     Room/DataStore that counts as personal data?) — this must match
//     real app behavior, not be filled in generically.
//
// STORE LISTING
// [ ] Title (max 30 characters) and short description (max 80
//     characters) are set.
// [ ] Full description is written.
// [ ] At least 2 screenshots are uploaded.
// [ ] A feature graphic (1024x500) is uploaded.
// [ ] App icon meets Play Console's requirements.
//
// RELEASE STRATEGY
// [ ] A release track has been chosen appropriate to how confident the
//     team is in this build (internal testing first for anything new
//     and risky, per Challenge 3's reasoning).

Notes:
- This checklist deliberately separates BUILD concerns (things covered
  in earlier chapters, like signing and R8) from PLAY CONSOLE concerns
  (privacy policy, content rating, data safety) and STORE LISTING
  concerns (screenshots, descriptions) — these are genuinely different
  categories of work, often owned by different people on a real team
  (an engineer handles the build; a product/marketing person might
  handle the listing).
- The data safety form item specifically calls back to what Course 2's
  chapters actually built (Retrofit networking, DataStore/Room storage)
  — this isn't boilerplate, it has to accurately describe THIS specific
  app's real behavior.