kotlin-lib-mcp: Skill for Claude Code

Bump Kotlin + Analysis API (version-locked)

The Analysis API (standalone K2/FIR) is the single most version-fragile part of this repo. Kotlin and every *-for-ide artifact must share the exact same version, and two runtime deps (caffeine, intellijCoroutines) are pinned to match what the bundled IntelliJ core expects. Getting this wrong shows up as NoSuchMethodError / NoClassDefFoundError at runtime or as silent loss of type resolution — never a clean compile error. Follow the steps; do not eyeball it.

1. Snapshot the current pins

Read gradle/libs.versions.toml and record:

• kotlin — the shared version ref used by all of: analysisApi-standalone, analysisApi-highLevel, analysisApi-k2, analysisApi-lowLevelFir, analysisApi-implBase, analysisApi-platform, analysisApi-symbolLightClasses, kotlin-compiler, plus the kotlin-* / composeCompiler-* plugin artifacts.
• caffeine (comment: "runtime dep of the Analysis API -for-ide jars; matches Kotlin's own pin").
• intellijCoroutines (comment: "JetBrains coroutines fork the bundled IJ core expects (KT-81457)").
• compose (comment: "aligned to Kotlin X.Y.Z") — Compose is Kotlin-coupled too.

Because every Analysis-API artifact uses version.ref = "kotlin", bumping the single kotlin entry moves them all. The risk is not forgetting one artifact — it's the three coupled satellites (caffeine, intellijCoroutines, compose) and undocumented API breaks.

2. Confirm the target and its coupled expectations (official sources)

For $ARGUMENTS (or the intended target Kotlin version), verify against official sources:

• kotlinlang.org release notes / Kotlin GitHub release: is this a stable release? Any Analysis API / standalone breaking changes called out?
• The -for-ide artifacts exist for this version in the IntelliJ dependencies repo (https://www.jetbrains.com/intellij-repository/), not just on Maven Central.
• Does the new Kotlin change the caffeine version its -for-ide jars expect? (Check the Kotlin build's own bundled version.) If so, update the caffeine pin to match and update the comment.
• Did the kotlin-compiler fat jar drop anything the -for-ide jars rely on? Kotlin moves modules between that jar and the -for-ide set (prepare/compiler vs prepare/ide-plugin-dependencies in its build), and the fat jar is ProGuard-shrunk against only what it contains. Diff the two versions' package lists (unzip -Z1 … | grep '\.class$' | sed 's|/[^/]*$||' | sort -u) before trusting a green compile. Known blocker for 2.4.20+: it moved the decompiler (org.jetbrains.kotlin.analysis.decompiler.*) out of kotlin-compiler into kotlin-compiler-common-for-ide, and the shrinker then stripped IntelliJ members only the decompiler used (FileType.getDefaultExtension()). Pulling kotlin-compiler-common-for-ide alongside the fat jar trades the NoClassDefFoundError: ClsKotlinBinaryClassCache for a NoSuchMethodError (tried, CI-verified). Getting past 2.4.10 needs an unshrunk classpath — the IntelliJ platform jars plus kotlin-compiler-*-for-ide instead of kotlin-compiler — or the org.jetbrains.kotlin:kotlin-analysis-api* artifacts 2.4.20's build defines (prepare/analysis-api/), once they are published. detekt hit the same wall (detekt/detekt#9734). Still true for 2.4.21 (checked 2026-10-16: no decompiler, analysis.utils or decompiled.light.classes packages in the fat jar, no kotlin-analysis-api* on Central), and its changelog is Wasm/JS/Native/scripting only. detekt's maintainers are skipping 2.4.20+ and going straight to 2.5.0, where they say a fix is coming — so the next target to try is 2.5.0 stable, not another 2.4.x patch.
• Is KT-81457 fixed in this version, making the intellijCoroutines fork pin unnecessary? If yes, that's a chance to drop the fork; if not, keep the pin.
• Compose Multiplatform ↔ Kotlin compatibility: pick the compose version aligned to the new Kotlin (JetBrains compatibility table) and update the # aligned to Kotlin … comment.