Summary

Cratis.Chronicle, Cratis.Chronicle.AspNetCore and Cratis.Chronicle.Testing are updated from 16.9.1 to 16.9.4, picking up 16.9.2, 16.9.3 and 16.9.4.

Added

• Chronicle 16.9.2: ComplianceMetadataActionFailed replaces the bare InvalidOperationException when applying or releasing compliance metadata fails. On a failed release it names the property, the subject the value was released under, and explains that the value was encrypted under a different subject, pointing at CHR0038 — rather than surfacing only the underlying OpenSSL oaep decoding error.

Changed

• Cratis.Chronicle, Cratis.Chronicle.AspNetCore and Cratis.Chronicle.Testing are updated to 16.9.4
• Chronicle 16.9.2: CHR0038 now also reports the fluent builder.Join<TEvent>(_ => _.On(...)) form, not just the model-bound [Join<TEvent>] attribute. A [PII] value counts as reaching the read model through an explicit .Set(...).To(...) mapping or through AutoMap matching an identically named property.

Fixed

• Chronicle 16.9.3: CHR0038 no longer reports a fluent join when AutoMap cannot carry the value across — [NoAutoMap] on the read model, and [NoAutoMap] on the target property of a positional record, were both still reported. Since the rule is an error, each was a build break on correct code.
• Chronicle 16.9.4: Two links in the concepts docs pointed at /arc/backend/chronicle/aggregates/aggregate-root.md, which no longer exists — the Arc page is defining-an-aggregate-root.md. This was breaking the Documentation site's internal-links check.