[IRus]

Komok now contains the product and consumes reusable libraries from Heapy/kotomi. Libraries use the io.heapy.kotomi Maven group and packages, with names such as kotomi-runtime and kotomi-runtime-compiler.

• Move technology modules, their documentation, and build tooling into the standalone Kotomi repository, preserving their Git history. Keep the original JVM implementation of kotomi-to-be-injected there.
• Wire the application through Kotomi providers and load its compiler plugin as an external Maven dependency. Keep product modules, application packaging, and coverage checks in Komok.
• Pin Kotomi to 4d9ae783c64adcfc3c32e33813cce7ab18a1a838 in kotomi.ref. CI and the documented local bootstrap build that revision into Maven Local before building Komok. Maven Central publication remains a separate release step.
• Give Kotomi a benefits-focused README and a runnable quickstart. The previous private Heapy/kotomi repository is now Heapy/kotomi-agent, with its local working changes preserved.

Validation:

• Kotomi JVM build, 1,144 tests, API and KLib API checks passed; 15 libraries published to Maven Local.
• The exact Kotomi README quickstart compiled and printed Hello, world! and Hello, Kotomi!.
• Komok JVM build, tests and coverage check passed: 8 tests passed, 1 existing test skipped.
• Komok distTar passed; the archive includes Kotomi dependencies and no old komok-tech-* JARs.
• Both GitHub Actions workflows passed actionlint. Locked product build plugins verified clean after applying the split.
• GitHub CI passed for Kotomi and Komok; the PR's landing build and CodeQL checks also passed.