[1tchy]

This makes JitPack serve the Kotlin engine as a Maven artifact, so sbt, Maven and Gradle builds can depend on com.github.openwatersio:slackwater:<commit> without a composite build. A root-level jitpack.yml and a Gradle init script, jitpack.gradle, build and publish only the engine with JDK 17, skipping IWLS, tests and coverage, and leave the Gradle build in kotlin/ unchanged. The published POM declares kotlin-stdlib, so consumers get it transitively, and kotlin/README.md explains the setup and usage. I tested it on my fork, where the JitPack build succeeded and a Java class in a throwaway sbt project predicted Newlyn's high and low tides from the artifact.

[Copilot]

🔵 Needs a closer look

CI does not exercise the root-level JitPack configuration; add relevant path filters or a publication smoke check.

No open issues 🎉

What changed in this PR

Adds JitPack publishing for the Kotlin tide and current prediction engine, enabling Maven, Gradle, and sbt consumers to use commit-based artifacts.

Changes:

• Configures JitPack to use JDK 17 and publish only the Kotlin engine.
• Adds Maven publication metadata, sources, and POM configuration.
• Documents JitPack consumption and local publication verification.

File	Description
kotlin/​README.md	Documents JitPack dependencies, Java usage, and local publication checks.
jitpack.yml	Configures the JitPack JDK and engine publication command.
jitpack.gradle	Adds the engine Maven publication and JitPack coordinate handling.

_{Review effort: Lite}