Kotlin Gradle

Step 1: Establish the build contract

1. DEFINE plugin setup | version alignment | compiler options | JVM toolchain | dependency/source-set change | generated sources | build performance | daemon failure | KGP variant | migration.
2. IDENTIFY affected projects, Kotlin targets/compilations/source sets, Gradle wrapper, KGP/AGP/JDK/Java target, language/API versions, repositories/catalogs/convention plugins, CI tasks, cache policy, and publication constraints.
3. READ the current Kotlin Gradle overview, compatibility table, and destination-version release/migration notes before changing versions.
4. PRESERVE the repository's wrapper, Kotlin/Groovy DSL, version catalog, convention-plugin ownership, repositories, toolchain, compiler options, and dependency policy unless the request changes them.
5. ROUTE Kotlin source behavior to kotlin-development; route detekt, Dokka, Kover, Spotless, ABI validation, and kotlinx-benchmark configuration to their dedicated skills.

Completion: exact module/target, version tuple, configuration owner, requested build behavior, and verification task are known.

Step 2: Inspect effective configuration

RUN from repository root:

python3 scripts/inspect-project.py --root . --json