Kotlin binary compatibility

Step 1: Establish scope and validator

1. DEFINE enablement | ABI change review | baseline update | filter policy | multiplatform completeness | published-artifact validation | legacy migration | failure diagnosis.
2. IDENTIFY library modules, Kotlin/Gradle/AGP versions, JVM/Android/KLib targets, publications/transforms, current dump files, CI tasks, release compatibility policy, and supported build hosts.
3. READ the current KGP ABI guide, KGP API reference, and legacy validator repository before changing configuration.
4. SELECT the built-in Kotlin Gradle plugin validator for new adoption only when experimental DSL/dump stability is acceptable. PRESERVE the legacy plugin for existing builds unless migration is requested; it is maintained for fixes, not new features.
5. TREAT the validator as change detection. Classify each dump diff against compatibility policy; never infer semantic version or safety from task pass/fail alone.

Completion: validator, modules/targets, artifact boundary, baseline, host policy, and release policy are explicit.

Step 2: Inspect configuration and dumps

RUN from the repository root:

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