gradle-agp-workflowlisted

# Android Gradle And AGP Workflow ## Purpose Keep Android build, dependency, variant, and packaging work grounded in the repository's real Gradle and Android Gradle Plugin configuration. The practical decision is which Gradle files own the change, which Android modules and variants are affected, and which command proves the change without relying on machine-global state. ## Source Check Use repo-local Gradle files, checked-out dependency sources, and Dash.app Gradle or Java docsets opportunistically. Use official documentation as authority for Android-specific and version-sensitive behavior: - [Android build documentation](https://developer.android.com/build) - [Android Gradle Plugin release notes](https://developer.android.com/build/releases/gradle-plugin) - [Gradle User Manual](https://docs.gradle.org/current/userguide/userguide.html) - [Gradle Java Toolchains](https://docs.gradle.org/current/userguide/toolchains.html) - [Kotlin Gradle plugin documentation](https://kotlinlang.org/docs/gradle.html) Translate documentation into concrete Gradle files, module names, variants, and commands. ## Inspection Workflow 1. Identify the Gradle owner: - `settings.gradle` or `settings.gradle.kts` - root `build.gradle` or `build.gradle.kts` - module `build.gradle` or `build.gradle.kts` - `gradle/libs.versions.toml` - `gradle.properties` - `gradle/wrapper/gradle-wrapper.properties` 2. Identify Android plugin shape: - `com.android.application` - `com.android.