testing-lint-workflowlisted

# Android Testing And Lint Workflow ## Purpose Run the narrowest useful Android tests and lint checks, explain failures clearly, and route emulator/device validation to the Android testing plugin. The practical decision is which module, source set, variant, and task prove the work without turning every change into a full device run. ## Source Check Use repo-local Gradle files, test files, lint config, checked-out dependency sources, and Dash.app docsets opportunistically for exact Gradle or Java questions. Use official documentation as authority for Android-specific testing and lint behavior: - [Test apps on Android](https://developer.android.com/training/testing) - [Android build documentation](https://developer.android.com/build) - [Android lint documentation](https://developer.android.com/studio/write/lint) - [Jetpack Compose testing documentation](https://developer.android.com/develop/ui/compose/testing) - [Gradle User Manual](https://docs.gradle.org/current/userguide/userguide.html) Translate documentation into concrete test source sets, Gradle tasks, variants, and failure modes. ## Inspection Workflow 1. Identify test layout: - `src/test` - `src/androidTest` - Compose UI test files - fixture, fake, mock, and dependency-injection test support 2. Identify lint setup: - `lint.xml` - lint baselines - Gradle lint options - CI lint commands 3. Identify affected variants: - debug versus release - product flavors - application versus li