pi-apexlang 0.2.2 → 0.4.0

package/skills/apexlang/templates/region-components/smart-filter-search/smart-filter-search._common.md

@@ -1,74 +1,135 @@
 ---
 templateId: region.smart-filters.common
 componentType: region
-version: 1.1
-description: Shared contract for smart-filters regions and target result region binding.
+version: 1.3
+description: Shared contract for a Smart Filters region, its search child, and one secured base results region.
 ---
 
 # Purpose
 
-Document the native smart-filters region shell and its filter child metadata boundary.
+Define the generation boundary for a Smart Filter Search experience without treating ticket fields as unproven APEXlang properties.
 
-# Generation Rules (MANDATORY)
+# Required Input Contract
+
+Freeze these decisions in the Generation Plan before emitting a Smart Filters region:
 
-1. Use the dedicated `region-smart-filters` template.
-2. Treat the filtered-region reference as mandatory.
-3. Do not emit region `settings` for Smart Filters unless active compiler metadata proves a valid settings group.
-4. Use the canonical search-filter source contract with `source.dbColumns` for free-text search; do not invent single-column shortcut shapes.
-5. Do not target map regions directly. For map pages, target a companion report/cards results region and refresh the sibling map explicitly.
+| Name | Type | Contract |
+|------|------|----------|
+| `smartFiltersRegionStaticId` | string | Unique static id for the Smart Filters region. |
+| `baseRegionStaticId` | string | Static id of the one authoritative filtered results region. |
+| `baseSource` | object | Secured view or canonical SQL plus `object_evidence_source`; never inferred from examples. |
+| `searchableAttributes` | non-empty ordered list | Explicit allowlist of base-source columns rendered to `source.dbColumns`. |
+| `matchSemantics` | enum | One of `contains`, `starts`, or `exact`. |
+| `minChars` | positive integer | Minimum input length that can run search or suggestions. |
+| `maxLen` | positive integer | Maximum accepted input length; must be greater than or equal to `minChars`. |
+| `tokenizationPolicy` | object | Stable whitespace, punctuation, case, accent, and token-order behavior. |
+| `securityScope` | object | Effective authorization scheme and server-side condition for both regions and all suggestion/refinement sources. |
+| `performanceReadiness` | object | Index strategy, statistics status, and expected cardinality evidence. |
+| `settingsContract` | object | Ticket settings plus property-level compiler evidence for the target build. |
 
-# Variable Contract
+Validation boundary: artifact lint checks emitted topology, source/projection, allowlist order, scope, refinement shape, and supported settings; the plan gate checks object evidence, `no_rewrite`, search/compiler evidence, performance, and runtime acceptance. Use `apexlang validate --generation-plan <path>`; require it with `--require-smart-filter-generation-plan`.
+
+# Generation Rules (MANDATORY)
 
-| Name | Required | Type | Notes |
-|------|----------|------|-------|
-| regionStaticId | yes | string | Region identifier. |
-| name | yes | string | Display name. |
-| smartFiltersRegionStaticId | yes | string | Smart filters region static id. |
-| source.filteredRegion | yes | ref | Results region static id. |
-| filters | optional | array | Filter definitions (radio/search/etc). |
-| filter.itemName | conditional | string | Canonical page item name for child search filters, e.g. `P14_F_SEARCH`. |
+1. Emit exactly one `smartFilters` region and bind it through `source.filteredRegion` to exactly one base results region.
+2. Use `baseRegionStaticId` as the single binding value and declare the Smart Filters region before that target region.
+3. Preserve the supplied secured-view or canonical-SQL base source. Do not rewrite, widen, or inject predicates into its SQL automatically.
+4. Emit at least one `type: search` child whose `source.dbColumns` is the ordered `searchableAttributes` allowlist. Every entry must be projected by base source.
+5. Keep filter children separate from the region shell and use page-scoped item names such as `P14_F_SEARCH`.
+6. For APEX 24.2, target Classic Report, Cards, Map, or Calendar. Target a Map region rather than its layer, and prove exactly one layer source for the single-dataset contract. Never target Smart Filters, Faceted Search, or another non-results component.
 
-# Output Template – Full
+# Output Template – Region Shell
 
 ```apexlang
-region {{regionStaticId}} (
-  name: {{name}}
-  type: smartFilters
-  source {
-    filteredRegion: @{{source.filteredRegion}}
-  }
-  {{filters}}
+region {{smartFiltersRegionStaticId}} (
+    name: {{name}}
+    type: smartFilters
+    source {
+        filteredRegion: @{{baseRegionStaticId}}
+    }
+    {{filters}}
 )
 ```
 
 # Output Template – Search Filter Child
 
 ```apexlang
-filter {{filter.itemName}} (
-  type: search
-  label {
-    label: {{filter.label}}
-  }
-  layout {
-    sequence: {{filter.layout.sequence}}
-  }
-  source {
-    dbColumns: {{filter.source.dbColumns}}
-  }
+filter {{searchFilterItemName}} (
+    type: search
+    label {
+        label: {{searchFilterLabel}}
+    }
+    layout {
+        sequence: {{searchFilterSequence}}
+    }
+    source {
+        dbColumns: {{searchableAttributes}}
+    }
 )
 ```
 
+# Search Behavior Contract
+
+- Record exactly one default match semantic: `contains`, `starts`, or `exact`; record per-attribute overrides only when the selected compiler-supported shape can represent them.
+- Do not execute search or suggestions below `minChars`. Reject input above `maxLen` predictably rather than silently changing the server-side value.
+- Apply one frozen tokenization policy to search, suggestions, and refinements. It must define trimming, repeated whitespace, punctuation boundaries, case normalization, accent normalization, duplicate tokens, and token order.
+- Use bind values for user input. Do not concatenate search text into the base SQL.
+- `SMART_FILTER_SEARCH_BEHAVIOR_CONTRACT_REQUIRED_001` blocks generation unless exactly one semantic, positive integer bounds with `maxLen >= minChars`, every tokenization decision, and property-level compiler evidence are frozen in the Generation Plan.
+- When the compiler has no property for a required behavior, keep it as a documented unresolved requirement and stop with Missing Inputs instead of inventing DSL or modifying the base SQL.
+- Reject contradictory overrides, incomplete tokenization scope, unresolved compiler evidence, or `base_sql_rewrite: true` with `SMART_FILTER_SEARCH_BEHAVIOR_CONTRACT_REQUIRED_001`.
+
+# Compiler-Gated Settings Contract
+
+The requested UI contract is:
+
+- `maxSuggestionChips: 100`
+- `moreFiltersSuggestionChip: true`
+- `compactNosThreshold: 10000`
+- `showTotalRowCount`: an explicit boolean
+- `totalRowCountLabel: Results` only when `showTotalRowCount` is `true`
+
+Query active compiler metadata for every requested property. Emit a `settings` block only for properties exposed by the target build. `SMART_FILTER_SETTINGS_VALUE_REQUIRED_001` enforces each supported value and the conditional `Results` label. Missing compiler metadata stops with `SMART_FILTER_SETTINGS_COMPILER_EVIDENCE_REQUIRED_001`; unsupported properties stop with `SMART_FILTER_SETTINGS_UNSUPPORTED_001` until the target build or an approved alternative resolves the requirement. Never silently drop a requested setting or copy syntax from ticket prose.
+
+# Security and Suggestion Contract
+
+- The Smart Filters region and base region must have the same effective authorization scheme and server-side condition; both may be absent only when the page contract explicitly permits public access.
+- Suggestions and refinements must derive from the same security-trimmed base dataset. Do not query a broader table, bypass a secured view, or omit tenant/row-level predicates.
+- Prove every referenced object and searchable column through schema documentation, live metadata, or an exact user assertion.
+
+# Performance Readiness Contract
+
+- Record expected cardinality, current statistics status, and an index/search strategy aligned to each selected match semantic.
+- Do not claim that a normal B-tree index solves substring `contains` searches. Record the proven text/function-based strategy or the accepted scan cost.
+- Avoid wrapping searchable columns in functions unless matching function-based index evidence exists.
+- Performance readiness remains unresolved while any required evidence is missing.
+- `SMART_FILTER_PERFORMANCE_READINESS_REQUIRED_001` blocks generation while index strategy, statistics status, or expected-cardinality evidence is incomplete.
+- For `contains`, reject a plain B-tree claim without text/function support or explicit accepted scan cost.
+
 # Conditional Rendering Rules
 
-- Keep filter children separate from the shell.
-- Use the advanced HTML DOM ID only when the owning scenario requires it.
-- Omit `settings` blocks for APEX 26.1 Smart Filters; the live compiler metadata for `NATIVE_SMART_FILTERS` has no settings group.
+- Use advanced DOM ids only when the selected scenario requires them.
+- Emit categorical/range filter children only when their columns are in the base projection and their suggestion source satisfies the security contract.
+- Set `totalRowCountLabel` only when `showTotalRowCount` is compiler-supported and true.
 
 # Guardrails
 
-- `filteredRegion` must reference an existing results region with compatible source columns.
-- The Smart Filters region must be declared before the referenced `filteredRegion` in the page file.
-- `filteredRegion` must reference a report/cards-style results region. Do not target map regions, map layers, Smart Filters regions, Faceted Search regions, or other non-results aliases.
-- Filter LOV/value definitions must match result columns.
-- Search filters must use `source.dbColumns`; do not collapse free-text search into `source.databaseColumn`.
-- Metadata export lookup: search for `Smart Filters`, the filtered-region reference, and child filter metadata.
+- `baseRegionStaticId` is mandatory, unique on the page, and resolves to one APEX 24.2 Classic Report, Cards, Map, or Calendar base region.
+- `searchableAttributes` is an explicit allowlist; never infer it from all projected columns or `select *`.
+- Search filters use `source.dbColumns`; do not collapse free-text search into `source.databaseColumn`.
+- Do not rewrite base SQL for match, tokenization, suggestions, or security. Store the original in `base_source.canonical_sql` and require an exact emitted match (ignoring outer whitespace).
+- Match named object evidence to actual SQL objects or `tableName`; secured-view evidence must record `object_type: view` and `secured: true`.
+- Traverse `filterGroup` and nested `checkbox` refinements for inherited authorization, conditions, base columns, and suggestion sources.
+- `SMART_FILTER_BASE_SOURCE_CONTRACT_REQUIRED_001` blocks until source mode, object evidence, projection, and no-rewrite are recorded.
+- Filter LOV/value definitions must be subsets of the base region's security-trimmed data.
+- Metadata export lookup: search for `Smart Filters`, `filteredRegion`, the base static id, and child filter metadata.
+
+# Validation Checklist
+
+- Exactly one base region is resolved and its static id matches `source.filteredRegion`.
+- Every searchable attribute is projected by the proven base source and no unlisted attribute is searchable.
+- Match semantics, `minChars`, `maxLen`, and tokenization are explicit and consistent.
+- Settings evidence is property-specific for the target compiler build.
+- Authorization, conditions, suggestions, and refinements share the base security scope.
+- Index strategy, statistics status, and expected cardinality evidence are recorded.
+- Refinement/suggestion `source.type` is `static` or `distinctValues`/`base`; reject shared, SQL, function, and unknown shapes.
+- Each search/refinement child has label/help; plan runtime acceptance sets `result_refresh_without_reload` and `filtered_exports` to `true`.

package/skills/apexlang/templates/region-components/smart-filter-search/smart-filter-search._index.md

@@ -13,6 +13,7 @@ Primary routing entrypoint for `smart-filter-search` templates.
 
 # Load Order
 
-1. Load this file.
-2. Load `smart-filter-search._common.md`.
-3. Load one scenario template in this folder.
+1. Resolve the `smart-filter-search` pattern and construction pack.
+2. Load this file.
+3. Load `smart-filter-search._common.md` and freeze every required input.
+4. Load `smart-filter-search.standard.md` only when its exact component shape matches.

package/skills/apexlang/templates/region-components/smart-filter-search/smart-filter-search.standard.md

@@ -1,29 +1,45 @@
 ---
 templateId: region.smart-filters.standard
 componentType: region
-version: 1.0
+version: 1.1
 imports:
   - smart-filter-search._common
-description: Standard smart filters region for search/filter experiences.
+description: Standard Smart Filters region with one search child bound to a secured base results region.
 ---
 
+# Usage
+
+Use only after the common contract has resolved `baseRegionStaticId`, the searchable allowlist, search behavior, security parity, performance evidence, and compiler-gated settings. Pair this component with the exact selected template for the base results region; this scenario does not invent a generic base-region shell.
+
 # Output Template
 
-```
+```apexlang
 region {{smartFiltersRegionStaticId}} (
-  name: {{name}}
-  type: smartFilters
-  source {
-    filteredRegion: @{{source.filteredRegion}}
-  }
-  layout {
-    sequence: {{layout.sequence}}
-    slot: {{layout.slot}}
-  }
-  appearance {
-    template: {{appearance.template}}
-    templateOptions: #DEFAULT#
-  }
-  {{filters}}
+    name: {{name}}
+    type: smartFilters
+    source {
+        filteredRegion: @{{baseRegionStaticId}}
+    }
+    layout {
+        sequence: {{layout.sequence}}
+        slot: {{layout.slot}}
+    }
+    appearance {
+        template: {{appearance.template}}
+        templateOptions: #DEFAULT#
+    }
+    filter {{searchFilterItemName}} (
+        type: search
+        label {
+            label: {{searchFilterLabel}}
+        }
+        layout {
+            sequence: {{searchFilterSequence}}
+        }
+        source {
+            dbColumns: {{searchableAttributes}}
+        }
+    )
+    {{additionalFilters}}
 )
 ```

package/skills/apexlang/templates/shared-components/component-settings/component-settings._common.md

@@ -15,6 +15,7 @@ Define deterministic defaults for APEX component settings. Use this markdown fam
 
 # Guardrails
 - For current compiler compatibility, use `settings { attributes: {...} }` for component settings.
+- Application-scoped plug-in attributes belong in a `componentSetting` declaration; do not add them to a page component's instance-level `settings` block.
 - Do not emit direct keys inside `settings {}` (for example `display_as`, `mode`, `match_mode`).
 - Do not invent unsupported component categories.
 - Keep environment-specific values out of templates.

package/skills/apexlang/templates/shared-components/component-settings.example.md

@@ -90,6 +90,7 @@ componentSetting NATIVE_DISPLAY_SELECTOR (
     type: region
     settings {
         attributes: {
+            includeSlider: false
         }
     }
 )

package/skills/apexlang/templates/shared-components/email-templates.example.md

@@ -87,7 +87,7 @@ emailTemplate order-confirmation (
             ```
     }
     advanced {
-        versionNo: 2
+        versionNumber: 2
     }
 )
 ```

package/skills/apexlang/templates/shared-components/rest-data-sources/example_rest_data_source.example.md

@@ -27,7 +27,7 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         urlPathPrefix: /data/Pagination
     }
     /*STRICTLY - Use this ONLY when asked to do Synchronization to local table with Synchronization type as 'append' */    
-    restSynchronization {
+    synchronization {
         jobIsActive: true
         localTableOwner: SAN
         localTableName: {{source.table}}
@@ -35,7 +35,7 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         httpRequestLimit: 1000
     }
     /*STRICTLY - Use this ONLY when asked to do Synchronization to local table with Synchronization type as 'merge' */    
-      restSynchronization {
+      synchronization {
         jobIsActive: true
         localTableOwner: SAN
         localTableName: {{source.table}}
@@ -44,7 +44,7 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         httpRequestLimit: 1000
     }
      /*STRICTLY - Use this ONLY when asked to do Synchronization to local table with Synchronization type as 'replace' or 'fullRefreshDelete' */    
-     restSynchronization {
+     synchronization {
         jobIsActive: true
         localTableOwner: SAN
         localTableName: {{source.table}}
@@ -60,11 +60,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
     authentication {
         credentials: @moviedb_api_key
     }
-    settings {
-        paginationType: pageSizeAndFetchOffset
-        pageSizeUrlParam: limit
-        rowOffsetUrlParam: offset
-        hasMoreRowsSelector: hasMore
+    comments {
+        comments: Confirm pagination settings with compiler-backed REST Data Source attributes before emission.
     }
 
     parameter search_query (
@@ -86,8 +83,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         rowSelector: items
     }
 
-    dataProfileCol data (
-        colName: DATA
+    dataProfileColumn data (
+        columnName: DATA
         source {
             sequence: 1
             dataType: varchar2
@@ -100,8 +97,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         }
     )
 
-    dataProfileCol data-capacity (
-        colName: DATA_CAPACITY
+    dataProfileColumn data-capacity (
+        columnName: DATA_CAPACITY
         source {
             sequence: 2
             dataType: varchar2
@@ -114,8 +111,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         }
     )
 
-    dataProfileCol data-hard-disk-size (
-        colName: DATA_HARD_DISK_SIZE
+    dataProfileColumn data-hard-disk-size (
+        columnName: DATA_HARD_DISK_SIZE
         source {
             sequence: 3
             dataType: varchar2
@@ -128,8 +125,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         }
     )
     
-    dataProfileCol data-capacity-gb (
-        colName: DATA_CAPACITY_GB
+    dataProfileColumn data-capacity-gb (
+        columnName: DATA_CAPACITY_GB
         source {
             sequence: 4
             dataType: number
@@ -142,8 +139,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         }
     )
 
-    dataProfileCol ID (
-        colName: ID
+    dataProfileColumn ID (
+        columnName: ID
         source {
             sequence: 5
             dataType: number
@@ -158,8 +155,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         }
     )
 
-    dataProfileCol NAME (
-        colName: NAME
+    dataProfileColumn NAME (
+        columnName: NAME
         source {
             sequence: 6
             dataType: varchar2
@@ -173,8 +170,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         }
     )
 
-    dataProfileCol {{source.dateColumn}} (
-        colName: {{source.dateColumn}}
+    dataProfileColumn {{source.dateColumn}} (
+        columnName: {{source.dateColumn}}
         source {
             sequence: 7
             dataType: timestampWithTimeZone
@@ -189,8 +186,8 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
         }
     )
 
-    dataProfileCol {{source.amountColumn}} (
-        colName: {{source.amountColumn}}
+    dataProfileColumn {{source.amountColumn}} (
+        columnName: {{source.amountColumn}}
         source {
             sequence: 8
             dataType: number
@@ -205,9 +202,7 @@ Markdown-preserved APEXlang example. Use this file for syntax and structure only
     )
 
     operation get_rows (
-        label {
-            label: GET
-        }
+        label: GET
         operation {
             urlPattern: .
             httpMethod: get
@@ -283,8 +278,8 @@ restDataSource icm-claims-data (
         rowSelector: items
     }
 
-    dataProfileCol claim-id (
-        colName: CLAIM_ID
+    dataProfileColumn claim-id (
+        columnName: CLAIM_ID
         source {
             sequence: 1
             dataType: number
@@ -294,8 +289,8 @@ restDataSource icm-claims-data (
         }
     )
 
-    dataProfileCol claim-number (
-        colName: CLAIM_NUMBER
+    dataProfileColumn claim-number (
+        columnName: CLAIM_NUMBER
         source {
             sequence: 3
             dataType: varchar2
@@ -305,8 +300,8 @@ restDataSource icm-claims-data (
         }
     )
 
-    dataProfileCol currency-code (
-        colName: CURRENCY_CODE
+    dataProfileColumn currency-code (
+        columnName: CURRENCY_CODE
         source {
             sequence: 6
             dataType: varchar2
@@ -316,8 +311,8 @@ restDataSource icm-claims-data (
         }
     )
 
-    dataProfileCol policy-id (
-        colName: POLICY_ID
+    dataProfileColumn policy-id (
+        columnName: POLICY_ID
         source {
             sequence: 2
             dataType: number
@@ -327,8 +322,8 @@ restDataSource icm-claims-data (
         }
     )
 
-    dataProfileCol reported-date (
-        colName: REPORTED_DATE
+    dataProfileColumn reported-date (
+        columnName: REPORTED_DATE
         source {
             sequence: 4
             dataType: date
@@ -338,8 +333,8 @@ restDataSource icm-claims-data (
         }
     )
 
-    dataProfileCol total-claimed-amount (
-        colName: TOTAL_CLAIMED_AMOUNT
+    dataProfileColumn total-claimed-amount (
+        columnName: TOTAL_CLAIMED_AMOUNT
         source {
             sequence: 5
             dataType: number
@@ -350,9 +345,7 @@ restDataSource icm-claims-data (
     )
 
     operation get (
-        label {
-            label: GET
-        }
+        label: GET
         operation {
             urlPattern: .
             httpMethod: get
@@ -361,14 +354,14 @@ restDataSource icm-claims-data (
     )
 
     operation post (
-        label {
-            label: POST
-        }
+        label: POST
         operation {
             urlPattern: .
             httpMethod: post
             databaseOperation: insert
-            requestBodyTemplate: 
+        }
+        requestBody {
+            template:
                 ```
                 {
                     "claim_id":"#CLAIM_ID#"
@@ -379,6 +372,7 @@ restDataSource icm-claims-data (
                    ,"currency_code":"#CURRENCY_CODE#"
                 }
                 ```
+            versionNumber: 1
         }
     )
 

package/skills/apexlang/templates/shared-components/task-definitions/action-task.example.md

@@ -116,36 +116,8 @@ taskDefinition LOAN_ACTION (
     action send-email (
         name: Send Email
         type: sendEMail
-        emailHeader {
-            to: &P12_CUSTOMER_EMAIL.
-        }
-        emailTemplate {
-            emailTemplate: @order-confirmation
-            placeholderValues: 
-                ```
-                {
-                    "ORDER_NUMBER":"&P12_ORDER_ID.",
-                    "CUSTOMER_NAME":"&P12_CUSTOMER_NAME.",
-                    "ORDER_DATE":"&P12_ORDER_DATE.",
-                    "SHIP_TO":"",
-                    "SHIPPING_ADDRESS_LINE_1":"",
-                    "SHIPPING_ADDRESS_LINE_2":"",
-                    "ITEMS_ORDERED":"",
-                    "ORDER_TOTAL":"&P12_TOTAL_AMT.",
-                    "ORDER_URL":"","MY_APPLICATION_LINK":""
-                }
-                ```
-        }
-        emailAttachments {
-            attachmentSql: 
-                ```sql
-                select file_blob blob_column,
-                       file_name,
-                       mime_type,
-                       null content_id
-                  from order_files
-                 where order_id = :APEX$TASK_PK
-                ```
+        comments {
+            comments: Email header, template placeholder, and attachment attributes require compiler-backed sendEMail task-action syntax before emission.
         }
         execution {
             onEvent: complete

package/skills/apexlang/templates/shared-components/task-definitions/approve-request.example.md

@@ -79,7 +79,7 @@ taskDefinition CHECKER_APPROVAL (
         label {
             label: Disbursed Amount
         }
-        value {
+        validation {
             required: false
         }
     )
@@ -148,36 +148,8 @@ taskDefinition CHECKER_APPROVAL (
      action send-email (
         name: Send Email
         type: sendEMail
-        emailHeader {
-            to: &P12_CUSTOMER_EMAIL.
-        }
-        emailTemplate {
-            emailTemplate: @order-confirmation
-            placeholderValues: 
-                ```
-                {
-                    "ORDER_NUMBER":"&P12_ORDER_ID.",
-                    "CUSTOMER_NAME":"&P12_CUSTOMER_NAME.",
-                    "ORDER_DATE":"&P12_ORDER_DATE.",
-                    "SHIP_TO":"",
-                    "SHIPPING_ADDRESS_LINE_1":"",
-                    "SHIPPING_ADDRESS_LINE_2":"",
-                    "ITEMS_ORDERED":"",
-                    "ORDER_TOTAL":"&P12_TOTAL_AMT.",
-                    "ORDER_URL":"","MY_APPLICATION_LINK":""
-                }
-                ```
-        }
-        emailAttachments {
-            attachmentSql: 
-                ```sql
-                select file_blob blob_column,
-                       file_name,
-                       mime_type,
-                       null content_id
-                  from order_files
-                 where order_id = :APEX$TASK_PK
-                ```
+        comments {
+            comments: Email header, template placeholder, and attachment attributes require compiler-backed sendEMail task-action syntax before emission.
         }
         execution {
             onEvent: complete