Release v22.65.0

Summary

Screenplay documents generated from an Arc application now carry its event sources, streams and routes, so a routed application round-trips without its events landing on the default stream. Arc now builds on Cratis Screenplay 4.124.1.

Added

• The Screenplay generator writes event sources, streams, command routes and specification routes into its default output wherever Screenplay's executable model (ESM v8) can state them. This covers property, literal and single-placeholder [EventStreamId("{Name}")] stream ids, and no stream on unrouted expected events. (#3090)
• Routes Screenplay still refuses are left out with a diagnostic naming why, and stay available behind ScreenplayOptions.AuthoringOnlyConstructs. That covers property-path and handler-command mappings, generated-property mappings, colliding source or stream names, and a source named Default. (#3090)

Changed

• A routed command states its route instead of the legacy concurrency block. An information diagnostic names each concurrency dimension that is dropped. (#3090)
• Setting ScreenplayOptions.MaximumExecutableModelVersion below v8 keeps the previous output, with routes left out and reported. (#3090)
• Arc depends on Cratis.Screenplay 4.124.1 and @cratis/screenplay-language 4.124.1. Generated documents use the current compliance keywords: pii for personal data and secret for operational secrets. (#3090)
• When the generator leaves out a read model, it also leaves out the queries, screen data, productions and scenarios that depend on it, and says so, so the document still binds. A slice that becomes empty this way is reported. (#3090)

Fixed

• Observable and collection queries that Screenplay now admits bind clean instead of being tolerated as refusals. Same-named queries in different slices are a known Screenplay binder limit: Cratis/Screenplay#624. (#3090)