KotlinPoet

Step 1: Define the generated-source contract

1. CLASSIFY standalone generator | annotation processor | KSP processor | schema/compiler output | metadata stub | generator migration | formatting/import defect.
2. IDENTIFY input authority, output package/path, declarations, visibility, language/API targets, module/source set, public API/ABI effect, regeneration owner, incremental ownership, and consumer compilation/runtime proof.
3. READ the current KotlinPoet documentation, release, and affected API reference before setup or migration.
4. KEEP KotlinPoet's boundary explicit: it models Kotlin files/declarations/types and renders code blocks; it does not parse or rewrite existing Kotlin expression/statement syntax.
5. ROUTE processor lifecycle, deferral, and incremental graph work to ksp; ordinary Kotlin behavior to kotlin-development; build/toolchain wiring to kotlin-gradle; exact symbol lookup to kotlin-api-reference.

Completion: input-to-output mapping, owning module/processor, generated API, deterministic order, incremental dependency class, and compilation targets are explicit.

Step 2: Inspect the generator project

RUN from the target repository root:

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