Kotlin API reference

Step 1: Identify the exact API question

1. DEFINE lookup | availability | overload resolution | platform difference | opt-in/deprecation | behavior clarification | version comparison.
2. RECORD symbol spelling, expected fully qualified name, declaration kind, receiver, argument types, return context, library artifact/module, dependency version, Kotlin version, platform, and source set.
3. DISTINGUISH local/project API from external Kotlin ecosystem API. For local API, use language-server/source navigation; for generated API documentation, use the Dokka skill.
4. LIMIT this workflow to official Kotlin, kotlinx, Ktor, Kotlin Gradle plugin, Kotlin metadata, and Compose Material3 references listed by the official catalog.

Completion: one exact symbol/artifact/version/platform question is stated without relying on an unqualified name.

Step 2: Inspect dependency evidence

RUN from repository root:

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

For an isolated coordinate, add --coordinate group:artifact:version. CONFIRM detected literal/catalog/Maven coordinates, version resolution, Kotlin plugin/stdlib inference, API portal, and source repository. Resolve aliases, BOMs, constraints, parent properties, and dependency locking with the build tool before trusting a version.