Release v4.65.0

A guarded action (when … execute … otherwise) and a guarded interaction such as on double click now run in a live Stage and in a generated React application, evaluated against the data on screen, instead of being refused.

Added

• Guarded actions run in the Stage frontend runtime: the action executes the first alternative whose guard holds for the item its screen's single-item data declaration reads, with its with values taken from that item. When none holds, otherwise hidden renders nothing and otherwise execute <Command> offers that command. Without an item nothing is offered, and the action follows the data as it changes. (part of #236)
• Guarded on click, on double click and on select interactions run exactly the branch that holds for the row they happened on, or their otherwise actions, through the Scene interaction engine. A table that declares a double click no longer selects or navigates on the click that starts it. (part of #237)

Changed

• STAGE-SCENE-ACTION-001 and STAGE-SCENE-INTERACTION-001 now refuse only guards Stage cannot evaluate: anything other than item.<field> compared with a literal (==, !=, >, >=, <, <=, contains, startswith) combined with and and or, and any fallback other than hidden or an execute that names a command. Such a guard is still refused in runnable rendering, in the Scene a running Stage serves, and by the frontend runtime, which shows the action disabled with the diagnostic. See Guarded actions and interactions. (part of #236)
• A navigation started by an interaction is a step the browser can go back from, and its arguments become the target screen's parameters. (part of #237)