Release v4.171.0

Inbound translations that capture another application's public events can now be specified and run in the reference evaluator, the way Chronicle runs them.

Added

• A specification drives a capture over events by presenting the consumed event itself: given <Event> and when append <Event> for an event a capture reads from. The capture keeps one state per key, folding earlier events in order, and appends what its rules map: the first event for a key counts as added, an event that changes nothing appends nothing, and when <field> and transitions hold only on a change. for on such a fixture is optional. See capturing from public events and decision 0077. (#483)

Changed

• New error PLAY0700: a capture over events must key by a property that every from event declares as required; a context key such as key $eventSourceId is refused. Chronicle fails the partition for an event without the key, so the model now says so at compile time. (#483)
• New error PLAY0701: given capture and when capture cannot name a capture over events, because a record does not say which event arrived. When the capture reads exactly one event, the quick fix in the editors and through MCP rewrites the step to given <Event> / when append <Event> with the same lines. (#483)

Fixed

• A specification that appended an event a capture over events reads, and expected then no events, passed even though Chronicle would append; the capture now receives the event and its appends are compared. (#483)