fix(bom): publish skainet-bom at sk.ainet:skainet-bom

The umbrella BOM was being emitted as `sk.ainet.core:skainet-bom`
because vanniktech's auto-coordinates feature picks up `GROUP=sk.ainet.core`
from the root `gradle.properties`, clobbering the per-module
`group = "sk.ainet"` override. Downstream BOMs (e.g.
`sk.ainet.transformers:skainet-transformers-bom`) import this with
`<groupId>sk.ainet</groupId>`, so they were unresolvable from a
fresh `mavenCentral()`-only project.

- Use vanniktech's explicit `mavenPublishing { coordinates(...) }`
  so the BOM lands at `sk.ainet:skainet-bom:0.22.2` regardless of
  the engine-wide GROUP.
- Extend `validate-published-poms.sh` to assert the BOM exists at
  `~/.m2/repository/sk/ainet/skainet-bom/` so the regression cannot
  ship again silently.
- Bump VERSION_NAME to 0.22.2; update README, CHANGELOG, and Antora
  docs samples (java-getting-started, java-model-training,
  io-readers, architecture) to the new version and BOM coordinates.

Fixes #584

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: michalharakal

.github/scripts/validate-published-poms.sh

@@ -15,13 +15,26 @@
 set -euo pipefail
 
 REPO_ROOT="${HOME}/.m2/repository/sk/ainet/core"
+BOM_ROOT="${HOME}/.m2/repository/sk/ainet/skainet-bom"
 
 if [[ ! -d "${REPO_ROOT}" ]]; then
   echo "ERROR: no published artifacts found under ${REPO_ROOT}" >&2
   echo "Did ./gradlew publishToMavenLocal run successfully?" >&2
   exit 1
 fi
 
+# The umbrella BOM must publish at sk.ainet:skainet-bom — downstream
+# BOMs (e.g. sk.ainet.transformers:skainet-transformers-bom) import it
+# with that group. Catching this here prevents the 0.22.1 regression
+# where the BOM landed at sk.ainet.core:skainet-bom and was effectively
+# unresolvable by consumers following the standard BOM pattern.
+if [[ ! -d "${BOM_ROOT}" ]]; then
+  echo "ERROR: skainet-bom not published at sk.ainet:skainet-bom" >&2
+  echo "Expected directory: ${BOM_ROOT}" >&2
+  echo "Check skainet-bom/build.gradle.kts mavenPublishing { coordinates(...) }." >&2
+  exit 1
+fi
+
 mapfile -t POMS < <(find "${REPO_ROOT}" -type f -name '*.pom' | sort)
 
 if [[ ${#POMS[@]} -eq 0 ]]; then

CHANGELOG.md

@@ -2,6 +2,12 @@
 
 ## [Unreleased]
 
+## [0.22.2] - 2026-05-02
+
+### Fixed
+
+- **`skainet-bom` published at the wrong Maven coordinates** — the umbrella BOM was being emitted as `sk.ainet.core:skainet-bom` because the engine-wide `GROUP=sk.ainet.core` from the root `gradle.properties` clobbered the per-module `group = "sk.ainet"` override picked up by `vanniktech.maven.publish`. Downstream BOMs (e.g. `sk.ainet.transformers:skainet-transformers-bom`) import this with `<groupId>sk.ainet</groupId>`, so they were unresolvable from a fresh `mavenCentral()`-only project. Fix uses vanniktech's explicit `mavenPublishing { coordinates("sk.ainet", "skainet-bom", VERSION_NAME) }` so the BOM publishes at `sk.ainet:skainet-bom:0.22.2`. `validate-published-poms.sh` extended to assert the BOM landed at the expected path so the regression cannot ship again. (Issue #584)
+
 ## [0.22.1] - 2026-04-30
 
 ### Added

README.md

@@ -19,11 +19,18 @@ Add the core dependencies (Gradle Kotlin DSL):
 
 ```kotlin
 dependencies {
-    implementation("sk.ainet.core:SKaiNET-lang-core:0.22.1")
-    implementation("sk.ainet.core:SKaiNET-backend-cpu:0.22.1")
+    // Recommended: import the umbrella BOM and drop versions on the engine modules.
+    implementation(platform("sk.ainet:skainet-bom:0.22.2"))
+
+    implementation("sk.ainet.core:skainet-lang-core")
+    implementation("sk.ainet.core:skainet-backend-cpu")
 }
 ```
 
+> The BOM was first correctly published to Maven Central in 0.22.2 — earlier versions
+> shipped at the wrong coordinates and could not be imported. Pin versions directly if
+> you need an older release.
+
 ### Hello Neural Net
 
 ```kotlin
@@ -137,6 +144,10 @@ SKaiNET is a modular ecosystem. While this repository contains the core engine,
 
 ---
 
+## What's New in 0.22.2
+
+- **`sk.ainet:skainet-bom` now resolves from Maven Central.** The umbrella BOM was previously published at the wrong coordinates (`sk.ainet.core:skainet-bom`), so consumers following the standard `platform(...)` import pattern — and downstream BOMs like `sk.ainet.transformers:skainet-transformers-bom` that import it transitively — got 404s from Central. Hotfix; no API or behavior changes. (Issue #584)
+
 ## What's New in 0.22.0
 
 - **Native (FFM) CPU kernel provider — M5 milestone closed.** New `skainet-backend-native-cpu` module bundles a hand-tuned C shared library (`-O3 -ffast-math` auto-vectorized into AVX2 / NEON FMA) reachable via FFM downcalls. **4.17×–5.87× faster than Panama Vector on Q4_K matmul** at LLM-typical 1024²–4096² shapes; **1.55×–1.77× faster on FP32 SGEMM** at 256³–1024³. Auto-registers via ServiceLoader; `KernelRegistry.bestAvailable()` routes through native when the lib loads, falls through cleanly to the priority-50 Panama provider otherwise.

docs/modules/ROOT/pages/how-to/io-readers.adoc

@@ -20,7 +20,9 @@ Add the following dependencies to your `build.gradle.kts`:
 [source,kotlin]
 ----
 dependencies {
-    implementation("sk.ainet:skainet-io-gguf:0.19.0")
+    implementation(platform("sk.ainet:skainet-bom:0.22.2"))
+
+    implementation("sk.ainet.core:skainet-io-gguf")
     implementation("org.jetbrains.kotlinx:kotlinx-io-core:0.8.2")
 }
 ----
@@ -30,7 +32,9 @@ dependencies {
 [source,kotlin]
 ----
 dependencies {
-    implementation("sk.ainet:skainet-io-onnx:0.19.0")
+    implementation(platform("sk.ainet:skainet-bom:0.22.2"))
+
+    implementation("sk.ainet.core:skainet-io-onnx")
     implementation("org.jetbrains.kotlinx:kotlinx-io-core:0.8.2")
     implementation("pro.streem.pbandk:pbandk-runtime:0.16.0")
 }

docs/modules/ROOT/pages/how-to/java-model-training.adoc

@@ -16,7 +16,7 @@ This guide covers building neural networks, defining loss functions and optimize
         <dependency>
             <groupId>sk.ainet</groupId>
             <artifactId>skainet-bom</artifactId>
-            <version>0.19.0</version>
+            <version>0.22.2</version>
             <type>pom</type>
             <scope>import</scope>
         </dependency>

docs/modules/ROOT/pages/reference/architecture.adoc

@@ -206,8 +206,11 @@ see the same source file (`DefaultCpuOpsJvm.transpose`).
 `sk.ainet.core:<module>-<target>:<version>`. KMP variants land per
 target (`*-jvm`, `*-android`, `*-iosarm64`, `*-macosarm64`,
 `*-linuxx64`, `*-linuxarm64`, `*-js`, `*-wasm-js`, `*-wasm-wasi`).
-* *Single BOM* — `sk.ainet.core:skainet-bom` provides a
-`platform()` import for downstream Gradle.
+* *Single BOM* — `sk.ainet:skainet-bom` provides a
+`platform()` import for downstream Gradle. Note the group is
+`sk.ainet`, not `sk.ainet.core`, so downstream BOMs (e.g.
+`sk.ainet.transformers:skainet-transformers-bom`) can import it
+under the standard umbrella group.
 * *Releases* — tags `0.X.Y` on the release branch trigger
 `.github/workflows/publish.yml` → `./gradlew publish` on macOS-latest
 with JDK 25.

docs/modules/ROOT/pages/tutorials/java-getting-started.adoc

@@ -29,7 +29,7 @@ The `skainet-bom` manages all SKaiNET module versions so you never have to keep
 ----
 <project>
     <properties>
-        <skainet.version>0.19.0</skainet.version>
+        <skainet.version>0.22.2</skainet.version>
     </properties>
 
     <dependencyManagement>
@@ -127,7 +127,7 @@ repositories {
 
 dependencies {
     // Import BOM for version alignment
-    implementation(platform("sk.ainet:skainet-bom:0.19.0"))
+    implementation(platform("sk.ainet:skainet-bom:0.22.2"))
 
     // Core tensor library
     implementation("sk.ainet:skainet-lang-core-jvm")

gradle.properties

@@ -1,5 +1,5 @@
 GROUP=sk.ainet.core
-VERSION_NAME=0.22.1
+VERSION_NAME=0.22.2
 POM_DESCRIPTION=SKaiNET
 
 POM_URL=https://github.com/SKaiNET-developers/skainet/

skainet-bom/build.gradle.kts

@@ -3,8 +3,22 @@ plugins {
     alias(libs.plugins.vanniktech.mavenPublish)
 }
 
+// Override the engine-wide `sk.ainet.core` group: downstream BOM
+// consumers (e.g. sk.ainet.transformers:skainet-transformers-bom)
+// import this with `<groupId>sk.ainet</groupId>`. vanniktech's
+// auto-coordinates feature otherwise picks up GROUP=sk.ainet.core
+// from the root gradle.properties and would publish the BOM at the
+// wrong coordinates.
+mavenPublishing {
+    coordinates(
+        groupId = "sk.ainet",
+        artifactId = "skainet-bom",
+        version = providers.gradleProperty("VERSION_NAME").getOrElse("unspecified"),
+    )
+}
+
 group = "sk.ainet"
-version = rootProject.findProperty("VERSION_NAME") ?: "0.14.0"
+version = providers.gradleProperty("VERSION_NAME").getOrElse("unspecified")
 
 javaPlatform {
     allowDependencies()