release-readiness-workflowlisted

# Android Release Readiness Workflow ## Purpose Check whether an Android app or library is ready for release without starting a publish workflow by default. The practical decision is which version, signing, packaging, policy, changelog, and automation surfaces must be verified before a human or repo-owned release system publishes artifacts. ## Source Check Use repo-local Gradle files, release docs, CI workflows, Fastlane files, checked-out automation sources, and Dash.app docsets opportunistically for exact Gradle or Java questions. Use official documentation as authority for Android-specific release, signing, privacy, permissions, and Play behavior: - [Prepare and roll out a release](https://developer.android.com/studio/publish) - [Android App Bundles](https://developer.android.com/guide/app-bundle) - [Sign your app](https://developer.android.com/studio/publish/app-signing) - [Shrink, obfuscate, and optimize your app](https://developer.android.com/build/shrink-code) - [Play Developer API](https://developers.google.com/android-publisher) - [Fastlane supply documentation](https://docs.fastlane.tools/actions/supply/) Translate documentation into concrete release files, commands, artifacts, and gates. ## Inspection Workflow 1. Identify release ownership: - app module - release build type - product flavors - version code and version name - changelog or release notes - CI release workflow - Fastlane, Gradle Play Publisher, Play Developer Publishing AP