⭐ Versioning Approach

This fork versions independently of upstream — 1.0.0-SNAPSHOT, not tied to Axon's 5.4.0-SNAPSHOT, so there's no implication of drop-in compatibility with a specific upstream release. group stays org.axonframework, matching upstream's actual Maven coordinates (needed for the publish-compatibility goal).

No gradle/libs.versions.toml catalog either — a catalog was built once from build/parent/pom.xml's ~50-entry dependencyManagement block, then deliberately removed in favor of inline-per-module versions, matching the style already used in this user's other Gradle fork, saga-full. Accepted tradeoff: nothing catches two modules drifting to different versions of the same dependency the way a shared Maven parent would.