Fix CodeQL Android build and Gradle configuration

[spiralgang]

This change fixes the failing CodeQL analysis for the Android project.
The main fix involves replacing the failing autobuild process with explicit Gradle build steps (./gradlew assembleDebug) and ensuring the Android SDK is correctly set up in the workflow environment.
Additionally, I fixed a configuration error in the root build.gradle.kts that was preventing the project from building correctly even with explicit commands.
The Gradle wrapper script was also restored to ensure the build can run in CI.

---

PR created automatically by Jules for task 13054695653750018689 started by @spiralgang

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Summary of Changes

Hello @spiralgang, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on resolving critical build and configuration issues that were preventing CodeQL analysis from running successfully on the Android project. It involves adjusting Gradle plugin application, re-enabling the Gradle wrapper script, and introducing a .gitignore file to manage build artifacts, thereby stabilizing the build process and enabling proper static analysis.

Highlights

• CodeQL Build Fix: Replaced CodeQL's failing autobuild process with explicit Gradle build steps (./gradlew assembleDebug) and ensured the Android SDK is correctly set up in the workflow environment, allowing CodeQL analysis to run successfully.
• Gradle Configuration Correction: Corrected a configuration error in the root build.gradle.kts by changing apply true to apply false for the com.android.application, com.android.library, and org.jetbrains.kotlin.android plugins. This resolves issues preventing the project from building correctly.
• Gradle Wrapper Restoration: The Gradle wrapper script was restored by renaming gradlew.bak to gradlew and removing gradlew.txt.bak, ensuring the build can run consistently in CI environments.
• Gitignore Addition: A new .gitignore file was added to properly exclude common build artifacts, Android-specific outputs, IDE files, and temporary logs from version control.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/codeql.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly addresses the CodeQL build failure by fixing the root build.gradle.kts configuration, switching from apply true to apply false for the Android and Kotlin plugins, which is the correct approach for a multi-module Gradle setup. Restoring the gradlew wrapper script is also a good step for ensuring consistent builds in CI.

One point of feedback: the Windows Gradle wrapper script (gradlew.bat) appears to have been removed (as gradlew.txt.bak) without a replacement. If development on Windows is expected, this script should be restored as gradlew.bat to provide a consistent build experience across platforms.

[gemini-code-assist]

It's a standard practice in Android projects to ignore the local.properties file, as it contains machine-specific configurations like the path to the Android SDK. Please add it to this section to prevent it from being accidentally committed.

# Android
local.properties