pi-apexlang 0.1.0

package/skills/apexlang/templates/business-logic/computations/computations.time.md

@@ -0,0 +1,36 @@
+---
+templateId: computations.time
+componentType: computation
+version: 1.0
+imports:
+  - computations._common
+description: Time/timestamp computation archetype.
+---
+
+# Purpose
+
+Use for computations deriving time or timestamp values (combining date/time fields, generating timestamps).
+
+---
+
+# Output Template – Minimal
+```
+computation {{computationStaticId}} (
+    name: {{computationName}}
+    location: pageProcess
+    computationPoint: beforeHeader
+    type: functionBody
+    item: {{item}}
+    plsqlFunctionBody:
+        ```plsql
+        {{plsqlFunctionBody}}
+        ```
+)
+```
+
+---
+
+# Conditional Rendering Rules
+
+- Adjust `location` and `computationPoint` to align with when the timestamp should be computed.
+- Ensure the function body returns a string or date compatible with the target item data type.

package/skills/apexlang/templates/business-logic/dynamic-actions/README.md

@@ -0,0 +1,57 @@
+# Dynamic Actions Templates
+
+## Purpose
+Canonical dynamic action documentation for declarative client behavior and guarded server-side integration patterns.
+
+## Usage
+- Load `dynamic-actions._common.md` first to align variable contracts, guardrails, and required inputs.
+- Prefer declarative actions and keep API/package invocations aligned with invokeApi-first governance in data/logic rules.
+- Preserve canonical path references and markdown-first conventions when updating workflow or registry links.
+- For dialog workflows, choose templates by lifecycle intent:
+  - Cancel dialog interaction (client-side): `dynamic-actions.cancel-dialog.md`
+  - Submit current page from client event: `dynamic-actions.submit-page.md`
+  - Close dialog after server-side submit processing: `dynamic-actions.close-dialog.md` plus `../processes/processes.close-dialog.md`
+
+## Template Catalog
+- `dynamic-actions._common.md`
+- `dynamic-actions.add-remove-class-item.md`
+- `dynamic-actions.add-remove-class.md`
+- `dynamic-actions.alert-confirm-cancel.md`
+- `dynamic-actions.cancel-dialog.md`
+- `dynamic-actions.close-dialog.md`
+- `dynamic-actions.delete-with-notification.md`
+- `dynamic-actions.enable-disable-items.md`
+- `dynamic-actions.execute-server-side-code.md`
+- `dynamic-actions.execution-debounce-throttle.md`
+- `dynamic-actions.generate-text-ai.md`
+- `dynamic-actions.refresh-region-after-api.md`
+- `dynamic-actions.refresh-region-after-dialog.md`
+- `dynamic-actions.refresh-region-on-change.md`
+- `dynamic-actions.set-focus-on-ready.md`
+- `dynamic-actions.submit-page.md`
+- `dynamic-actions.set-value-javascript-expression.md`
+- `dynamic-actions.set-value-plsql-function.md`
+- `dynamic-actions.set-value-sql.md`
+- `dynamic-actions.set-value-static.md`
+- `dynamic-actions.show-error-message.md`
+- `dynamic-actions.show-hide-items.md`
+- `dynamic-actions.show-ai-assistant.md`
+- `dynamic-actions.show-success-message.md`
+- `dynamic-actions.view-document-inline.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Update catalogs and usage notes whenever templates are added, removed, or renamed.
+- Revalidate action recommendations when guardrails for invokeApi, conditions, or client behavior policies change.
+- New or updated scenario templates (`dynamic-actions.*.md` except `_common`) should include:
+  - `# Settings Contract`
+  - `# Conditional Rendering Rules`
+  - `# Event & Execution Semantics`
+  - `# Validation Checklist`
+
+## Router Cheat Sheet
+- "Submit the page when item changes/click happens": `dynamic-actions.submit-page.md`
+- "Cancel button should close the dialog without submit": `dynamic-actions.cancel-dialog.md`
+- "Close dialog only after successful CREATE/SAVE/DELETE": `dynamic-actions.close-dialog.md` + `../processes/processes.close-dialog.md`
+- "Refresh parent region after dialog closes": `dynamic-actions.refresh-region-after-dialog.md`
+- "Generate text with AI from a service prompt, AI Agent, item, or JavaScript input": `dynamic-actions.generate-text-ai.md`

package/skills/apexlang/templates/business-logic/dynamic-actions/dynamic-actions._common.md

@@ -0,0 +1,286 @@
+---
+templateId: dynamic-actions.common
+componentType: dynamicAction
+version: 2.0
+imports:
+  - dynamic-actions._common
+description: Shared canonical contract for dynamic action templates, including submit/cancel/close dialog lifecycles.
+---
+
+# Purpose
+
+Standardize dynamic action generation with deterministic field contracts, action capability rules, and lifecycle-safe dialog patterns aligned with `references/policies/memory-bank/20-data/apex.logic.md`.
+
+---
+
+# Generation Rules (MANDATORY)
+
+1. Load `references/policies/memory-bank/20-data/apex.logic.md` before drafting dynamic actions.
+2. Use only documented action names and properties. Do not invent aliases, keys, or ad-hoc settings.
+3. Use button aliases in DA triggers (`@button-static-id`) and component aliases for regions/actions.
+4. Default every action execution block to `fireOnInit: false` unless explicitly requested.
+5. Keep client-side behavior in dynamic actions; keep post-submit dialog closure in processes (`type: closeDialog`) unless explicit client-only closure is requested.
+
+---
+
+# Variable Contract
+
+| Name | Required | Type | Notes |
+|------|----------|------|-------|
+| dynamicActionStaticId | yes | string | Static identifier (`DA_<purpose>`). |
+| name | yes | string | Descriptive name shown in the builder. |
+| execution.sequence | yes | number | Execution order on the page. |
+| when.event | yes | enum | Triggering event. Must be one of the approved event values listed below; never invent aliases such as `dialogClosed`. |
+| when.selectionType | yes | enum | Trigger scope (`button`, `region`, `items`, `jQuerySelector`, `eventSource`, `javascriptExpression`). |
+| when.button | conditional | alias | Required when `selectionType: button`; always `@...` alias format. |
+| when.items/item | conditional | string | Required when `selectionType` targets items/item. |
+| when.region | conditional | alias | Required when `selectionType: region`. |
+| clientSideCondition.* | optional | condition | Declarative client-side gating. |
+| serverSideCondition.* | optional | condition | Declarative server-side gating. |
+| security.authZScheme | optional | string | Authorization scheme alias. |
+| action.name | yes | string | Unique action identifier. |
+| action.action | yes | enum | Action type (`refresh`, `setValue`, `executeServerSideCode`, etc.). |
+| action.execution.sequence | yes | number | Order relative to other actions. |
+| action.execution.event | no | n/a | Do not emit; current APEXlang compilers ignore action-level `execution.event`. |
+| action.execution.fireOnInit | optional | boolean | Default is `false`; set `true` only when explicitly requested. |
+| action.execution.fireWhenEventResultIs | optional | enum | Use for explicit true/false branches after `confirm` actions. |
+| affectedElements.selectionType | conditional | enum | Target for the action (`region`, `items`, `triggeringElement`, `jquerySelector`, `javaScriptExpression`). |
+| affectedElements.* | conditional | string | References for the selected target. |
+| settings.type | optional | enum | For `setValue`, allowed values are `static`, `sqlQuery`, `plsqlFunctionBody`, `javaScriptExpression`. |
+| settings.requestButtonName | conditional | string | Required when `action.action = submitPage`; submit request alias (for example `DELETE`). |
+| settings.* | conditional | variant | Action-specific settings (`class`, `itemsToSubmit`, `value`, `sqlQuery`, `plsqlFunctionBody`, etc.). |
+| action.serverSideCondition.* | optional | condition | Server-side gating for the action. |
+| action.security.authZScheme | optional | string | Authorization scheme alias for the action. |
+
+---
+
+# Approved `when.event` Values
+
+Use only these values for `when.event`:
+
+```text
+apexafterclosecanceldialog
+apexafterclosedialog
+apexafterrefresh
+apexbeforepagesubmit
+apexbeforerefresh
+apexdoubletap
+apexpan
+apexpress
+apexselectionchange
+apexswipe
+apextap
+change
+click
+custom
+dblclick
+focusin
+focusout
+input
+item/geocodedAddress/apexgeocoderresponse
+item/geocodedAddress/apexgeocoderselection
+item/markdownEditor/markdownified
+item/shuttle/shuttlechangeorder
+keydown
+keypress
+keyup
+load
+mousedown
+mouseenter
+mouseleave
+mousemove
+mouseup
+ready
+region/calendar/apexcalendardateselect
+region/calendar/apexcalendareventselect
+region/calendar/apexcalendarviewchange
+region/cards/tablemodelviewpagechange
+region/facetedSearch/facetsafterremovechart
+region/facetedSearch/facetsbeforeaddchart
+region/facetedSearch/facetschange
+region/interactiveGrid/apexbeginrecordedit
+region/interactiveGrid/gridpagechange
+region/interactiveGrid/interactivegridmodechange
+region/interactiveGrid/interactivegridreportchange
+region/interactiveGrid/interactivegridsave
+region/interactiveGrid/interactivegridselectionchange
+region/interactiveGrid/interactivegridviewchange
+region/map/spatialmapchanged
+region/map/spatialmapclick
+region/map/spatialmapinitialized
+region/map/spatialmapobjectclick
+region/smartFilters/facetschange
+region/tree/treeviewselectionchange
+resize
+scroll
+select
+unload
+```
+
+Dialog lifecycle mapping:
+- Use `apexafterclosedialog` after successful dialog close flows.
+- Use `apexafterclosecanceldialog` after cancel-close flows.
+- Do not emit aliases such as `dialogClosed`.
+- Prefer page-ready behavior through `when.event: ready`.
+- Do not combine `when.event: ready` with `action.execution.fireOnInit`; choose one initialization mechanism, not both.
+
+---
+
+# Action Capability Matrix
+
+| Action Value | Notes |
+|--------------|-------|
+| addClass / removeClass | Declarative class manipulation. |
+| show / hide | Toggle visibility of targets. |
+| refresh | Refresh region or component. Valid only in DA `action (...)`; Settings required: ``affectedElements`; commonly chained after `apexafterclosedialog` or `apexafterclosecanceldialog` depending on the dialog lifecycle. |
+| submitPage | Submit page declaratively; use `settings.requestButtonName` for the request value. |
+| cancelDialog | Client-side dialog cancel; no submit/DML by default. Valid in DA `action (...)` and Button `triggerAction (...)` |
+| closeDialog | Client close intent; for post-submit closure prefer process `type: closeDialog`. Valid in DA `action (...)` (specialized) and Button `triggerAction (...)` (specialized) |
+| setValue | Populate items; must use `settings.type` and matching payload key (`value`, `sqlQuery`, `plsqlFunctionBody`, `javaScriptExpression`). |
+| enable / disable | Enable or disable items declaratively. |
+| confirm | yes | yes | `settings.message` | Pair with true/false branch actions as needed. |
+| showSuccessMessage / showErrorMessage | Display inline notifications. Valid in DA `action (...)` and Button `triggerAction (...)`; Settings required:`settings.message` |
+| executeJsCode | Execute JavaScript code; use `settings.jsCode`. |
+| executeServerSideCode | Execute PL/SQL (prefer invokeApi for packaged logic). Keep logic thin; package APIs preferred via process invokeApi. Valid in DA `action (...)` and Button `triggerAction (...)`; Settings required: `settings.plsqlCode` |
+| invokeServerSideEvent | Invoke server-side events. |
+| dialog | Open/close dialogs (openDialog, closeDialog). |
+| navigate | Perform navigation actions. |
+| timer | Timer-based actions (start/stop). |
+| custom | Reserved for plugin/custom actions—use with caution. |
+
+# Dialog Lifecycle Patterns (Authoritative)
+
+1. Cancel flow
+   - Trigger: cancel button click.
+   - Action: `cancelDialog`.
+   - Outcome: closes/cancels dialog interaction without submit.
+
+2. Submit flow
+   - Trigger: click/change/other event.
+   - Action: `submitPage`.
+   - Outcome: submit-bound validations/processes execute.
+
+3. Close-after-submit flow
+   - Primary closure point: server-side `process ... type: closeDialog`.
+   - Guard with button/request conditions (for example `CREATE,SAVE,DELETE`).
+   - Use DA-based close only when explicitly requested as client behavior.
+
+---
+
+# Output Template – Full
+
+```
+dynamicAction {{dynamicActionStaticId}} (
+    name: {{name}}
+    execution {
+        sequence: {{execution.sequence}}
+    }
+    when {
+        event: {{when.event}}
+        selectionType: {{when.selectionType}}
+        button: @{{when.button}}
+        items: {{when.item}}
+        region: @{{when.region}}
+        jquerySelector: {{when.jQuerySelector}}
+    }
+    clientSideCondition {
+        type: {{clientSideCondition.type}}
+        item: {{clientSideCondition.item}}
+        value: {{clientSideCondition.value}}
+    }
+    serverSideCondition {
+        type: {{serverSideCondition.type}}
+        item: {{serverSideCondition.item}}
+        {{serverSideCondition.comparisonAttribute}}: {{serverSideCondition.comparisonValue}}
+    }
+    action {{action.name}} (
+        action: {{action.action}}
+        affectedElements {
+            selectionType: {{affectedElements.selectionType}}
+            region: @{{affectedElements.region}}
+            items: {{affectedElements.item}}
+            jquerySelector: {{affectedElements.jQuerySelector}}
+            javaScriptExpression: {{affectedElements.javaScriptExpression}}
+        }
+        settings {
+            type: {{settings.type}}
+            value: {{settings.value}}
+            message: {{settings.message}}
+            title: {{settings.title}}
+            itemsToSubmit: {{settings.itemsToSubmit}}
+            requestButtonName: {{settings.requestButtonName}}
+            itemsToReturn: {{settings.itemsToReturn}}
+            class: {{settings.class}}
+            sqlQuery:
+                ```sql
+                {{settings.sqlQuery}}
+                ```
+            plsqlFunctionBody:
+                ```plsql
+                {{settings.plsqlFunctionBody}}
+                ```
+            plsqlCode:
+                ```plsql
+                {{settings.plsqlCode}}
+                ```
+            javaScriptExpression: {{settings.javaScriptExpression}}
+            jsCode:
+                ```javascript
+                {{settings.jsCode}}
+                ```
+            javaScriptExpression: {{settings.javaScriptExpression}}
+        }
+        execution {
+            sequence: {{action.execution.sequence}}
+            fireOnInit: false
+            fireWhenEventResultIs: {{action.execution.fireWhenEventResultIs}}
+        }
+        serverSideCondition {
+            type: {{action.serverSideCondition.type}}
+            item: {{action.serverSideCondition.item}}
+            {{action.serverSideCondition.comparisonAttribute}}: {{action.serverSideCondition.comparisonValue}}
+        }
+        security {
+            authorizationScheme: @{{action.security.authZScheme}}
+        }
+    )
+)
+```
+
+---
+
+# Conditional Rendering Rules
+
+- Remove optional blocks (`clientSideCondition`, `serverSideCondition`, `security`) when not needed.
+- Render only fields compatible with selected `when.selectionType` or `affectedElements.selectionType`.
+- For `setValue`, use `settings.type` values only: `static`, `sqlQuery`, `plsqlFunctionBody`, `javaScriptExpression`.
+- Use `settings.jsCode` for `executeJsCode`; never use `settings.code`.
+- Do not emit action-level `execution.event`; the action inherits the parent dynamic action trigger.
+- Provide only the `affectedElements` fields relevant to the selection type.
+- Include action-specific settings required by the selected action (`type`, `value`, `itemsToSubmit`, etc.).
+- Condition `type` tokens are case-sensitive and must match the catalog in `references/policies/memory-bank/20-data/apex.logic.md` exactly.
+- Set `comparisonAttribute` to `list` for `itemIsInColonDelimitedList` / `itemIsNotInColonDelimitedList`; otherwise use `value`.
+  - Valid: `item=value`, `item!=value`
+  - Invalid: `item=Value`, `item!=Value`
+- For `action: submitPage`, use `settings.requestButtonName`.
+- Use `fireWhenEventResultIs` only when modelling false-action fallbacks (e.g., Cancel branch).
+- Do not combine `when.event: ready` with `action.execution.fireOnInit`; choose one initialization mechanism.
+- When a `clientSideCondition` is present for branch-style behavior, model both outcomes in the same dynamic action:
+  - `True` branch action(s): default execution path.
+  - `False` branch action(s): same DA, with `execution.fireWhenEventResultIs: false`.
+- Prefer one DA with true/false actions over two separate DAs for inverse outcomes (for example `disable`/`enable`, `show`/`hide`).
+- If the false branch is intentionally omitted, scenario template must explicitly document why.
+- Do not use `setType` or `type: sqlStatement` for `setValue`.
+- Do not use `action: executeJavaScriptCode` or `settings { code: ... }`; use `action: executeJsCode` with `settings { jsCode: ... }`.
+- For `selectionType: button`, always use `when.button` as `@button-static-id` alias format.
+- Set `fireOnInit: false` by default on every action execution block; only use `true` when explicitly requested.
+
+# Validation Checklist
+
+- Trigger alias is valid (`@...`) for button/region references.
+- Action name is supported in matrix and has matching settings.
+- `fireOnInit` explicitly false unless caller requested otherwise.
+- Dialog workflows use the correct lifecycle split:
+  - `cancelDialog` for cancel interaction.
+  - `submitPage` for submission.
+  - Process `type: closeDialog` for post-submit close.

package/skills/apexlang/templates/business-logic/dynamic-actions/dynamic-actions._index.md

@@ -0,0 +1,18 @@
+---
+templateId: dynamic-actions.index
+componentType: template
+version: 1.0
+imports:
+  - dynamic-actions._common.md
+description: Routing entrypoint for dynamic-actions templates.
+---
+
+# Purpose
+
+Primary routing entrypoint for `dynamic-actions` templates.
+
+# Load Order
+
+1. Load this file.
+2. Load `dynamic-actions._common.md`.
+3. Load one scenario template in this folder.

package/skills/apexlang/templates/business-logic/dynamic-actions/dynamic-actions.add-remove-class-item.md

@@ -0,0 +1,92 @@
+---
+templateId: dynamic-actions.add-remove-class-item
+componentType: dynamicAction
+version: 1.0
+imports:
+  - dynamic-actions._common
+description: Add or remove a CSS class on a single item.
+---
+
+# Purpose
+
+Toggle validation styling on a specific item when focus leaves the field and the item value is empty.
+
+---
+
+# Output Template – Full
+```
+dynamicAction {{dynamicActionStaticId}} (
+    name: {{name}}
+    execution {
+        sequence: {{execution.sequence}}
+    }
+    when {
+        event: focusout
+        selectionType: items
+        items: {{when.item}}
+    }
+    clientSideCondition {
+        type: itemIsNull
+        item: {{clientSideCondition.item}}
+    }
+    action {{actionAdd.name}} (
+        action: addClass
+        settings {
+            class: {{settings.class}}
+        }
+        affectedElements {
+            selectionType: items
+            items: {{affectedElements.item}}
+        }
+        execution {
+            sequence: {{actionAdd.execution.sequence}}
+            event: @{{dynamicActionStaticId}}
+        }
+    )
+    action {{actionRemove.name}} (
+        action: removeClass
+        settings {
+            class: {{settings.class}}
+        }
+        affectedElements {
+            selectionType: items
+            items: {{affectedElements.item}}
+        }
+        execution {
+            sequence: {{actionRemove.execution.sequence}}
+            event: @{{dynamicActionStaticId}}
+            fireWhenEventResultIs: false
+        }
+    )
+)
+```
+
+---
+
+# Settings Contract
+
+- Required:
+  - `settings.class`
+- Optional:
+  - none
+- Forbidden:
+  - `setType`
+  - `settings.code`
+
+# Conditional Rendering Rules
+
+- Swap the event or selection type to target different triggers (e.g., `change`).
+- Remove the second action when class removal is unnecessary.
+- Update `clientSideCondition` when using non-empty checks or other comparisons.
+
+# Event & Execution Semantics
+
+- Keep `execution.event` aligned to the parent dynamic action alias unless the template explicitly requires another event source.
+- Keep `fireOnInit: false` by default and only enable initialization execution when explicitly requested.
+- Ensure action ordering is deterministic: prerequisite actions first, mutation/submit/refresh actions last.
+
+# Validation Checklist
+
+- Action name and settings keys match the scenario contract.
+- Selector aliases (`@...`) are used where required.
+- Optional blocks not used by this scenario are removed from final output.

package/skills/apexlang/templates/business-logic/dynamic-actions/dynamic-actions.add-remove-class.md

@@ -0,0 +1,80 @@
+---
+templateId: dynamic-actions.add-remove-class
+componentType: dynamicAction
+version: 1.0
+imports:
+  - dynamic-actions._common
+description: Add or remove CSS classes declaratively.
+---
+
+# Purpose
+
+Toggle CSS classes on target elements in response to user events (buttons, regions, items).
+
+---
+
+# Output Template – Full
+```
+dynamicAction {{dynamicActionStaticId}} (
+    name: {{name}}
+    execution {
+        sequence: {{execution.sequence}}
+    }
+    when {
+        event: {{when.event}}
+        selectionType: {{when.selectionType}}
+        button: @{{when.button}}
+        region: {{when.region}}
+        item: {{when.item}}
+    }
+    action {{action.name}} (
+        action: addClass
+        settings {
+            class: {{settings.class}}
+        }
+        affectedElements {
+            selectionType: {{affectedElements.selectionType}}
+            region: {{affectedElements.region}}
+            item: {{affectedElements.item}}
+            jquerySelector: {{affectedElements.jQuerySelector}}
+        }
+        execution {
+            sequence: {{action.execution.sequence}}
+            event: {{action.execution.event}}
+            fireOnInit: false
+        }
+    )
+)
+```
+
+---
+
+# Settings Contract
+
+- Required:
+  - `settings.class`
+- Optional:
+  - none
+- Forbidden:
+  - `setType`
+  - `settings.code`
+
+# Conditional Rendering Rules
+
+- Use `action: removeClass` or duplicate the action block to support both add/remove behaviours.
+- Provide the affectedElements field that matches the selection type (omit unused fields).
+- Remove `settings.class` when targeting actions that do not require a class name.
+- If `selectionType: button`, keep `when.button` in alias format (`@button-static-id`).
+- Keep `fireOnInit: false` unless initialization behavior is explicitly requested.
+
+# Event & Execution Semantics
+
+- Keep `execution.event` aligned to the parent dynamic action alias unless the template explicitly requires another event source.
+- Keep `fireOnInit: false` by default and only enable initialization execution when explicitly requested.
+- Ensure action ordering is deterministic: prerequisite actions first, mutation/submit/refresh actions last.
+
+# Validation Checklist
+
+- Action name and settings keys match the scenario contract.
+- Selector aliases (`@...`) are used where required.
+- Optional blocks not used by this scenario are removed from final output.

package/skills/apexlang/templates/business-logic/dynamic-actions/dynamic-actions.alert-confirm-cancel.md

@@ -0,0 +1,76 @@
+---
+templateId: dynamic-actions.alert-confirm-cancel
+componentType: dynamicAction
+version: 1.0
+imports:
+  - dynamic-actions._common
+description: Display a confirmation dialog with optional cancel handling.
+---
+
+# Purpose
+
+Prompt users with a confirmation dialog before executing further actions (e.g., deletion).
+
+---
+
+# Output Template – Full
+```
+dynamicAction {{dynamicActionStaticId}} (
+    name: {{name}}
+    execution {
+        sequence: {{execution.sequence}}
+    }
+    when {
+        event: click
+        selectionType: button
+        button: @{{when.button}}
+    }
+    action {{actionConfirm.name}} (
+        action: alert
+        settings {
+            title: {{settings.title}}
+            message: {{settings.message}}
+            style: confirmation
+        }
+        execution {
+            sequence: {{actionConfirm.execution.sequence}}
+            event: {{actionConfirm.execution.event}}
+            fireOnInit: false
+        }
+    )
+)
+```
+
+---
+
+# Settings Contract
+
+- Required:
+  - `settings.title`
+  - `settings.message`
+- Optional:
+  - `settings.style` when action supports style variants
+- Forbidden:
+  - `settings.code`
+  - raw button names in `when.button` (must use `@button-static-id`)
+
+# Event & Execution Semantics
+
+- Use `action: confirm` when you need explicit true/false branching.
+- Use `fireWhenEventResultIs: false` for cancel-branch actions only.
+- Keep `fireOnInit: false` for all confirm/cancel chain actions unless explicitly requested.
+
+# Conditional Rendering Rules
+
+- Replace `action: alert` with `action: confirm` when requiring separate OK/Cancel callbacks.
+- Chain follow-up actions (e.g., `executeServerSideCode`) by adding additional action blocks with appropriate `fireWhenEventResultIs` values.
+- Remove `button` selection when triggering from items or regions.
+- Keep `when.button` in alias format (for example `@cancel-claim`).
+- Keep `fireOnInit: false` unless initialization behavior is explicitly requested.
+- For modal cancel behavior, prefer `dynamic-actions.cancel-dialog.md`.
+
+# Validation Checklist
+
+- Confirm vs alert selection matches required branching behavior.
+- `fireWhenEventResultIs` appears only on branch-specific actions.
+- No raw button names are used in trigger selectors.