choose-project-shapelisted

# Choose Android Project Shape ## Purpose Pick the smallest correct Android-owned shape before code changes begin. The practical decision is whether the work belongs in an Android app, Android library, multi-module Android project, Kotlin-first implementation, Java-only maintenance, UI workflow, Gradle/AGP maintenance pass, test/lint pass, release-readiness pass, or a handoff to server-side JVM guidance. ## Source Check Use repo-local files, checked-out dependency sources, and Dash.app docsets opportunistically when they cover the exact Android-adjacent surface, especially Gradle, Java, or command-line reference material. Treat current official Android and Google documentation as authoritative for Android-specific behavior, APIs, release policy, permissions, privacy, Play delivery, and version-sensitive guidance: - [Android Developers documentation](https://developer.android.com/docs) - [Android build and Android Gradle Plugin documentation](https://developer.android.com/build) - [Jetpack Compose documentation](https://developer.android.com/compose) - [Gradle User Manual](https://docs.gradle.org/current/userguide/userguide.html) - [Kotlin documentation](https://kotlinlang.org/docs/home.html) - [Java documentation](https://docs.oracle.com/en/java/) Translate documentation into the concrete module, command, or implementation decision it changes. ## Classification Workflow 1. Inspect the repository shape: - `settings.gradle`, `settings.gradle.kts`, `build.gradle`, `b