Repository navigation
Release v1.0.2
Closes #102
Fixed
- A host releasing an organization name now frees it even when an organization registered that name through self-service signup. Before, a registration's name claim was stored without its name, because the Chronicle kernel only auto-maps properties from generation-1 events and
OrganizationRegistrationCompletedis generation 2 (Cratis/Chronicle#4367). Every later release then failed and was retried forever, so released names stayed taken. The name is now mapped explicitly. - Name claims stored before this fix are resolved from their events when a release arrives, so releases work whether or not the claims projection has been replayed. Replaying
OrganizationNameClaimafter upgrading also repairs those claims for the case-insensitive duplicate check. Depending on the kernel's projection evolution policy, Chronicle may only record a replay recommendation, in which case an operator should run the replay.
Added
- A specification that fails if any read model relies on auto-mapping from an event generation above 1.
Known upstream issue: the .NET client does not send IgnoreCasing for constraints (Cratis/Chronicle#4368), so case-insensitive uniqueness currently relies on Ante's own checks.
Local: Tier 1 PASS, Integration 110/110. Reviewed with Anthropic models only (same-provider review, no cross-provider check).