Release v4.199.0

Commands can now compare dates: require to >= from and validation rules such as dueDate > "2026-01-01" bind and run, ordering Date as a calendar date and DateTime as an instant.

Added

• Chronological ordering of Date and DateTime with ==, !=, >, >=, < and <= in require and produces when conditions (a command property against a command property or a literal) and in command and property validation rules (against a literal). Both sides must have the same primitive. DateTime values are compared as UTC instants at tick precision, so one instant written with different offsets is equal. Models that use it select ESM v26; every other model keeps its version and bytes. See decision 0087. (#803)
• A DateTime command input that takes part in a date comparison must carry an offset or Z; without one the command is rejected with a Validation outcome before any rule runs. (#803)
• A DateTime literal without an offset, or a date literal that does not parse, is reported as PLAY0273. Date ordering with $context operands, today, protected read paths, mixed Date and DateTime, on concept rules or in reaction where stays refused with PLAY0268. (#803)