Release v4.195.0

Changed

• Generated authorization policies are named after the modeled policy: operations bound to the same authorization share one {Name}Policy class registered as {Name}, and differing bindings are qualified with the operation and, if needed, the feature path. Names are the same for scoped and application renders and contain no hashes. (#495)

• A validation message that uses $strings when no strings catalog is supplied is refused with STAGE-ESM-019 naming the missing catalog, and canonical golden vectors render $strings validation messages. (#539)

• Rendering specifications reuse generated applications across assertions instead of repeatedly rendering the same application. (#726)

• A projection mapping that adds or subtracts a product of two event values (add total by unitPrice * quantity) is now converted to a Stage projection definition instead of being refused. PropertyMapping gains an optional Factor that carries the second operand, so a consumer such as Studio can hold the whole mapping.

• Play still cannot run such a mapping: Chronicle's $add and $subtract take one event property, so building the Chronicle definition from a mapping with a factor now fails with a clear message instead of adding the first operand alone.