Release v4.186.0

Changed

• A specification that appends an event the event log refuses because of a constraint (when append <event> then then error "<the constraint's message>") renders: the generated scenario seeds the given events, appends the event through the in-process event log and asserts that the append failed with that constraint, with that message, and that nothing else was appended. The given events must really make the append violate the constraint; anything else keeps the STAGE-ESM-011 refusal, now naming why.
• A reaction refusal scenario renders when the command it invokes has generated properties pinned with given generated <Command>.<property>, reads (reads) or has constraint-target events among its productions: the scenario pins the generated values, runs in a scenario typed by the command (so Arc reads the decision state the given events seed), the real command pipeline enforces the constraint, and the events the reaction appends are read back from the event log. A constraint-target event among a refusal branch's productions is still refused.
• given generated <Command>.<property> = <value> on a specification whose action is that command pins the generated value of the action; renderer, admission and the specification executor all read it so.

Fixed

• The five Acme Commerce Purchasing and Warehouse specifications refused with STAGE-ESM-011 (AutoReplenishDraftsAnOrderForThePreferredSupplier, AutoReplenishSkipsWhenAnOpenOrderCoversTheSku, AutoReplenishReportsAMissingPreferredSupplier, OfferingAProduct, AShipmentIsDispatchedOnce) render, build and pass: the Purchasing + Warehouse variant renders with an empty drop list, dotnet build 0 warnings / 0 errors, dotnet test 292/292. (#598)