Release v7.126.0

Cratis guidance now treats a fast build and spec feedback loop as a product requirement, and tells you when to specify behavior with a plain call and when with a scenario.

Added

• New universal rule: building and running specs must be as fast as possible locally and in CI, specs are safe to run in parallel, setup cost is fixed in the framework rather than paid per spec, and analyzers and generators stay cheap (#968)
• A per-artifact table in the scenario specification guidance: plain calls for decisions (Handle, Provide, validators, reducer transitions, reactor logic), scenarios for wiring and engine behavior, with what each scenario must cover (#968)

Changed

• The specification, command, event, read-model, reducer and reactor skills follow the new table and show a plain Handle spec, a negative authorization scenario and a reactor called directly with substitutes (#968)