[woksin]

A screen action can now pick its command from the selected item's state, so a Screenplay action with when … execute … alternatives renders as one button instead of being refused.

Added

• core:guarded-action component: an action with ordered when <condition> execute <Command> alternatives runs the first alternative whose condition holds for the selected item, falls back to otherwise execute <Command> or hides itself, and stays hidden while nothing is selected. See Guarded actions. (Guarded screen actions: pick the command from the selected item's state #68)
• Interaction bindings can carry ordered guarded alternatives with first-match semantics, evaluated against the interaction's subject. (Guarded screen actions: pick the command from the selected item's state #68)
• Guard conditions evaluate identically in C# and TypeScript: a condition on a missing field never matches, a field that is present and null matches only == null, and a condition that cannot be evaluated fails closed with diagnostic SCENE-GUARD-001. (Guarded screen actions: pick the command from the selected item's state #68)
• InteractionContext accepts an optional subject, the item an interaction acts on. (Guarded screen actions: pick the command from the selected item's state #68)

[woksin]

Notes for reviewers (not part of the release note)

Local gates on 0328773

• Release build: dotnet build Scene.slnx -c Release --no-incremental /p:TreatWarningsAsErrors=true. Zero warnings or errors.
• Release specs: Engine 177 and Model 40 pass.
• The JavaScript last changed at 1061de8. Run at 1061de8 and still valid: yarn ci, verify-packages and verify-blueprints, the scaffold proof, the Storybook build and the 17 browser suites.

Review: two cross-provider rounds. Round 1 found one blocker: GuardedActionProperties.ToProperties wrote camelCase guard enums that the engines then refused. It is fixed in 0328773 with a regression spec that fails without the fix. Round 2 found no blocking issues.

Code Health: CodeScene's change-set gate reports "failed". The owner accepted these findings:

• runActions.ts: the pre-existing Overall Code Complexity finding is unchanged (penalty 2.0 -> 2.0). Its function mean rose from 5.0 to 5.5.
• New GuardConditions.cs and evaluateGuardCondition.ts: each scores 9.38 (floor 9.0), with an Overall Code Complexity flag (mean 4.65 / 4.67 against a threshold of 4).
• Argument-count findings on the public data-shape records GuardedSelection (5), GuardedActionProperties (7) and InteractionBinding (5). These keep backward-compatible constructors, so they were not refactored.
• No new function-level smells.

Not run locally: hosted CI. Production UI.