[woksin]

Fixed

• Guards compare enum values by their declared member numbers when the condition carries enumerationNumbers, instead of by declaration position (Guards compare enum values by declaration position instead of their numbers #280)

[woksin]

Reviewer notes (not part of the release note)

• Delivered by the implementing lane: one commit d38f45c on top of Opt-in strict string operands for Contains guards #279, plus a merge of origin/main (Write component properties as indented blocks in the foundation docs #281 docs only, no overlap).
• Additive contract change: optional enumerationNumbers on ComparisonGuardCondition. An older engine ignores it and keeps positional comparison; a new engine without the field uses the unchanged positional path. Old JSON is byte-identical.
• Alternatives considered: replacing enumeration with name/number pairs (breaking, rejected); resolving numbers in the engine from names (no source of numbers there, rejected).
• Full whole-change cross-provider review (including security) passed with no findings.
• Delivery gates: Engine.Specs and Model.Specs Release -warnaserror; Engine.Specs 181/181, Model.Specs 45/45; model and engine yarn ci. Owner gate: whole-solution Release build.