release: prepare 0.29.1 (publish skainet-compile-minerva)

[michalharakal]

Summary

Patch release 0.29.1 that fixes publishing of the Minerva export module shipped in 0.29.0.

Stacked on release/0.29.0 (#727). Base is release/0.29.0, not develop — merge #727 into develop first, then this. This PR's diff is only the publishing fix + version/notes bump on top of 0.29.0.

Root cause

skainet-compile-minerva applies the vanniktech.mavenPublish plugin and is auto-included in the BOM, but — unlike every other published module — it had no per-module gradle.properties (POM_ARTIFACT_ID / POM_NAME). Maven Central rejects a publication with no POM name, so the artifact never made it to Central.

Fix

• Add skainet-compile/skainet-compile-minerva/gradle.properties:

  POM_ARTIFACT_ID=skainet-compile-minerva
  POM_NAME=skainet neural network Minerva secure-MCU export
  

• Bump VERSION_NAME 0.29.0 → 0.29.1.
• CHANGELOG — add [0.29.1] - 2026-06-09 Fixed entry.
• README — bump BOM coordinate, retitle "What's New", demote 0.29.0 highlights into Recent releases.
• Docs — bump skainet-bom coordinates to 0.29.1; regenerate kernel-support-matrix.adoc.

Audit

Scanned all modules applying the publish plugin for a missing POM_ARTIFACT_ID: skainet-compile-minerva was the only one (the root project declares the plugin apply false and does not publish). No other module is affected.

Notes

• BOM inclusion is automatic (no BOM build edit needed) — minerva already applies the publish plugin and is not on bomCoverage.excludePublished.
• Release tag 0.29.1 to be cut after merge to publish to Maven Central.

🤖 Generated with Claude Code