Gradle plugin io.heapy.kinetica, released as 0.4.0

[IRus]

Kinetica is compiler-plugin-only, so a Gradle consumer had to resolve the plugin jar through its own configuration and push -Xplugin into every KotlinCompilationTask by hand. This adds the kinetica-gradle-plugin module, which does that wiring, adds the version-matched runtime dependencies, and keeps sourcePipeline=psi on JVM compilations only — the one rule the manual wiring cannot express. Built as a toolchain jvm/lib against dev.gradleplugins:gradle-api and kotlin-gradle-plugin-api, both compile-only; the pom-only plugin marker is written by scripts/gradle-plugin-marker.sh, which release.sh calls before staging.

Two publication defects had to be fixed first, both of which blocked any Gradle consumption:

• The toolchain publishes every dependency as runtime-scoped, so consumers had nothing on the compile classpath and failed on SerializerFactory, a supertype of Role.Companion. Coroutines and serialization-json are exported now — both leak into the public API (EffectScope : CoroutineScope) — as is kinetica-runtime from kinetica-markdown, the one battery that was not exporting it.
• kinetica-compiler was Java 21 bytecode, and it is loaded into the consumer's Kotlin compile daemon. A JDK 17 daemon — Android, Spring, anything on jvmToolchain(17) — died with UnsupportedClassVersionError before compiling a line. It targets 17 now, like the Gradle plugin itself.

release.sh also grew a fix found by the release itself: it drops every local artifact of the version being released, including the compiler plugin every other module compiles with, and the toolchain has no ordering edge to the module that produces it. It publishes the compiler on its own first now.

Verification

node scripts/verify-gradle-plugin.mjs — 10 assertions over two fixtures (multiplatform and single-target JVM) whose build scripts carry no Kinetica wiring at all: both build and test, sourcePipeline=psi is withheld from the JS compilation, an authoring-rule violation is rejected by the FIR checkers on both the JVM and the JS compilation, and a configuration-cache entry is stored and reused. Plus ./kotlin test -m kinetica-gradle-plugin (6 contract tests guarding the baked-in coordinates against publish.module-template.yaml, common.module-template.yaml and KineticaCompilerContract).

0.4.0 is on Maven Central. examples/gradle-ssr now consumes it as alias(libs.plugins.kinetica) — clean jvmTest + jsBrowserDistribution with --no-build-cache --rerun-tasks, no Kinetica artifact declared anywhere in that build.

Worth a look in review

• The fixture check runs in the macOS CI job, not the JVM one: it publishes kinetica-runtime & co, whose macosArm64 targets a Linux runner cannot build. That job's timeout went 30 → 40 min. This PR is the first CI run of any of it.
• kinetica-runtime and friends stay at Java 21 bytecode. That is the app's runtime floor and a library policy call, unchanged here; only the compiler plugin moved to 17.
• Kotlin/Native from Gradle is unverified — the fixtures are jvm+js. KGP 2.4.10 has no getPluginArtifactForNative(), so Native takes the same artifact path, but nothing exercised it. Recorded as the open item in KNT-0048.

🤖 Generated with Claude Code