Release v15.36.1

Summary

Re-releases the 15.36.0 changes together with the Docker images, which failed to publish in 15.36.0 because the release pipeline's restricted token lacked the actions scope now required to write the GitHub Actions cache. There are no functional changes to the runtime or the libraries beyond 15.36.0.

Fixed

• Docker images (cratis/chronicle and the -workbench, -development, and -development-slim variants) are published again. The 15.36.0 publish failed to push them because the cache-saving build jobs were denied cache writes under GitHub's new Actions cache service.

---

Includes the 15.36.0 changes:

Added

• A CHR0023 analyzer that warns when a [ChildrenFrom] collection omits parentKey and the parent key cannot be inferred unambiguously — the event has more than one property of the parent read model's identifier type besides the child key. Specify parentKey to resolve it.

Changed

• The ReadModelScenario<T> test harness gives each driven event a distinct, monotonically increasing occurred time, so a time-based [FromAll] (for example a last-updated value mapped from EventContext.Occurred) reflects append order.

Fixed

• [FromAll] and [FromEvery] are now applied when declared on a positional record property ([property: FromAll(...)]). Previously the attribute was dropped, so the property was never projected, and [FromAll(contextProperty: ...)] was additionally mis-converted into a non-existent event-property lookup.
• [ChildrenFrom] with an omitted parentKey no longer mis-infers the child key as the parent key when the parent identifier and the event's child key share a type (such as a raw Guid), so the children resolve. When more than one event property still matches, the first by declaration order is used; specify parentKey to disambiguate.
• [ChildrenFrom] child collections now project in ReadModelScenario<T> when a child value is a decimal or TimeSpan; previously such collections materialized empty.