Kotlin Symbol Processing

Step 1: Define the processing contract

1. DEFINE consume processor | author processor | generated API change | incremental defect | multi-round dependency | JVM/Android/KMP target | kapt/KSP1 migration | task/provider failure.
2. IDENTIFY annotation/input symbols, generated files and package/names, owning modules, target compilations/variants, processor options, public API/ABI impact, downstream consumers, Kotlin/KSP/KGP/AGP/Gradle versions, and clean/incremental test matrix.
3. READ the current KSP overview, latest release, and relevant branch reference before changing setup/API.
4. KEEP the boundary explicit: KSP reads declarations/types/annotations and generates files; it cannot inspect expression/statement bodies, modify source, or change language semantics.
5. ROUTE general Kotlin source to kotlin-development, build/toolchain ownership to kotlin-gradle, KMP hierarchy/targets to kotlin-multiplatform, and exact external API lookup to kotlin-api-reference.

Completion: inputs, outputs, processor/consumer owners, target configurations, round/incremental behavior, and verification artifacts are explicit.

Step 2: Inspect current KSP wiring

RUN from the target repository root:

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