v0.4.0

• Raised the baseline to Java 17 and replaced Groovy 2.4 support with isolated Groovy 3, 4, and 5 verification.
• Compile the production artifacts once against Groovy 3 and verify the same publication with Gradle, Maven, classpath,
  and module-path consumers in all supported generations.
• Added klum-cast-spi and the stateless custom-check, typed binding, applicability-filter, and structured-diagnostic
  contracts. Compiler activation remains in klum-cast-compile; klum-cast-annotations remains Groovy-free.
• Added stable automatic module names for annotations, SPI, and compiler artifacts, eliminated split packages, and
  verified classpath plus generation-matching module-path activation.
• Added deterministic native rendering for structured diagnostics and the supported OR-composition tracer. Failing OR
  branches retain their diagnostics and provenance; AND/XOR syntax remains deferred and conditional syntax is not part of
  the 0.4 tracer.
• Removed forced Groovy version selection from SPI publication metadata. Custom-check authors now declare the matching
  Groovy compiler explicitly (org.codehaus.groovy for Groovy 3; org.apache.groovy for Groovy 4 and 5).
• Retained the 0.4 migration bridges for the legacy base class, exception/result shape, raw typed binding, and old OR
  declarations. These bridges are scheduled for removal in 1.0; see docs/migration/0.4.md.
• Added interim role-based onboarding for check writers, check aggregators, and check users, backed by one executable
  custom-check, composed-validation, and consuming-use journey in every supported Groovy lane.
• Codified protected, immutable RC/final publication and recovery procedures for the complete three-artifact product, and
  added clean Maven Central resolve-back evidence for Gradle/Maven, Groovy 3–5, classpath activation, and JPMS behavior.