Dokka

Step 1: Establish scope and version

1. DEFINE install | source-set configuration | content/link policy | output customization | aggregation | publication | plugin | DGP v1-to-v2 migration | failure diagnosis.
2. IDENTIFY Gradle, Maven, or CLI; Kotlin/Java/Android/KMP project type; build versions; modules/source sets; public API boundary; existing Dokka mode/configuration/tasks; output consumer.
3. READ the current Dokka introduction, selected runner guide, and latest release before changing versions.
4. KEEP every org.jetbrains.dokka artifact/plugin at one verified version. Treat HTML as recommended; treat Javadoc, GFM, and Jekyll stability limits explicitly.
5. USE DGP v2 for new Gradle integrations. DGP v2 and K2 analysis are default since 2.1.0.

Completion: runner, version, mode, source sets, output formats, aggregation boundary, and publication consumer are explicit.

Step 2: Inspect configuration

RUN from the repository root:

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