pi-apexlang 0.1.0

package/skills/apexlang/templates/region-components/collapsible-region/collapsible-region._template_options.md

@@ -0,0 +1,39 @@
+# Collapsible Region Template Options
+
+Use the listed `static_id` as the exact value to pass in the region's `templateOptions`.
+Example: `templateOptions: [expanded, scroll-default]`
+`#DEFAULT#` remains a standalone entry when used. Do not concatenate it with another token or replace the documented accepted value with the emitted CSS class string.
+
+## Collapsible (`collapsible`)
+Preset: `is-expanded:t-Region--scrollBody`
+
+- Remember Collapsible State | `static_id=remember-collapsible-state` | `css=js-useLocalStorage` | `group=--`
+- Remove Body Padding | `static_id=remove-body-padding` | `css=t-Region--noPadding` | `group=--`
+- Accent 1 | `static_id=accent-1` | `css=t-Region--accent1` | `group=Accent`
+- Accent 10 | `static_id=accent-10` | `css=t-Region--accent10` | `group=Accent`
+- Accent 11 | `static_id=accent-11` | `css=t-Region--accent11` | `group=Accent`
+- Accent 12 | `static_id=accent-12` | `css=t-Region--accent12` | `group=Accent`
+- Accent 13 | `static_id=accent-13` | `css=t-Region--accent13` | `group=Accent`
+- Accent 14 | `static_id=accent-14` | `css=t-Region--accent14` | `group=Accent`
+- Accent 15 | `static_id=accent-15` | `css=t-Region--accent15` | `group=Accent`
+- Accent 2 | `static_id=accent-2` | `css=t-Region--accent2` | `group=Accent`
+- Accent 3 | `static_id=accent-3` | `css=t-Region--accent3` | `group=Accent`
+- Accent 4 | `static_id=accent-4` | `css=t-Region--accent4` | `group=Accent`
+- Accent 5 | `static_id=accent-5` | `css=t-Region--accent5` | `group=Accent`
+- Accent 6 | `static_id=accent-6` | `css=t-Region--accent6` | `group=Accent`
+- Accent 7 | `static_id=accent-7` | `css=t-Region--accent7` | `group=Accent`
+- Accent 8 | `static_id=accent-8` | `css=t-Region--accent8` | `group=Accent`
+- Accent 9 | `static_id=accent-9` | `css=t-Region--accent9` | `group=Accent`
+- 240px | `static_id=240px` | `css=i-h240` | `group=Body Height`
+- 320px | `static_id=320px` | `css=i-h320` | `group=Body Height`
+- 480px | `static_id=480px` | `css=i-h480` | `group=Body Height`
+- 640px | `static_id=640px` | `css=i-h640` | `group=Body Height`
+- Hide | `static_id=hide` | `css=t-Region--hiddenOverflow` | `group=Body Overflow`
+- Scroll - Default | `static_id=scroll-default` | `css=t-Region--scrollBody` | `group=Body Overflow`
+- Plus or Minus | `static_id=plus-or-minus` | `css=t-Region--hideShowIconsMath` | `group=Collapsible Button Icons`
+- End | `static_id=end` | `css=t-Region--controlsPosEnd` | `group=Collapsible Icon Position`
+- Collapsed | `static_id=collapsed` | `css=is-collapsed` | `group=Default State`
+- Expanded | `static_id=expanded` | `css=is-expanded` | `group=Default State`
+- Remove Borders | `static_id=remove-borders` | `css=t-Region--noBorder` | `group=Style`
+- Remove UI Decoration | `static_id=remove-ui-decoration` | `css=t-Region--noUI` | `group=Style`
+- Stack Region | `static_id=stack-region` | `css=t-Region--stacked` | `group=Style`

package/skills/apexlang/templates/region-components/collapsible-region/collapsible-region.standard.md

@@ -0,0 +1,29 @@
+---
+templateId: region.collapsible.standard
+componentType: region
+version: 1.0
+imports:
+  - collapsible-region._common
+description: Standard collapsible static-content region.
+---
+
+# Output Template
+
+```
+region {{regionStaticId}} (
+  name: {{name}}
+  type: staticContent
+  layout {
+    sequence: {{layout.sequence}}
+    slot: {{layout.slot}}
+  }
+  appearance {
+    template: {{appearance.template}}
+    templateOptions: [
+      #DEFAULT#
+      {{appearance.collapsedOption}}
+      {{appearance.scrollOption}}
+    ]
+  }
+)
+```

package/skills/apexlang/templates/region-components/dynamic-content/README.md

@@ -0,0 +1,18 @@
+# Dynamic Content Templates
+
+## Purpose
+Canonical guidance for the `dynamic-content` region family, including shared contract loading and supported scenario variants.
+
+## Usage
+- Load `dynamic-content._common.md` first to align variable contracts, guardrails, and required inputs.
+- Choose a scenario variant matching the requested interaction pattern, data source type, and page composition context.
+- Preserve canonical path references and markdown-first conventions when updating workflow or registry links.
+
+## Template Catalog
+- `dynamic-content._common.md`
+- `dynamic-content.standard.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Update catalogs and usage notes whenever templates are added, removed, or renamed.
+- Keep family guidance aligned with page-level standards in memory-bank rules and with scenario coverage in this folder.

package/skills/apexlang/templates/region-components/dynamic-content/dynamic-content._common.md

@@ -0,0 +1,21 @@
+---
+templateId: region.dynamic-content.common
+componentType: region
+version: 1.0
+description: Shared contract for dynamic-content regions.
+---
+
+# Variable Contract
+
+| Name | Required | Type | Notes |
+|------|----------|------|-------|
+| regionStaticId | yes | string | Region static id. |
+| source.plsqlFunctionBody | yes | plsql | Must return renderable text/HTML payload. |
+| appearance.template | yes | ref | Region template; default to `@/standard`. |
+
+# Guardrails
+
+- Dynamic content PL/SQL should render content only; avoid DML side effects.
+- Escape user-derived values before HTML emission.
+- Prefer declarative regions when equivalent behavior exists.
+- Use `appearance.template: @/standard` unless the prompt explicitly asks for another documented shell.

package/skills/apexlang/templates/region-components/dynamic-content/dynamic-content._index.md

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

package/skills/apexlang/templates/region-components/dynamic-content/dynamic-content.standard.md

@@ -0,0 +1,31 @@
+---
+templateId: region.dynamic-content.standard
+componentType: region
+version: 1.0
+imports:
+  - dynamic-content._common
+description: Standard dynamic-content region with PL/SQL function body.
+---
+
+# Output Template
+
+```
+region {{regionStaticId}} (
+  name: {{name}}
+  type: dynamicContent
+  source {
+    plsqlFunctionBody:
+      ```plsql
+      {{source.plsqlFunctionBody}}
+      ```
+  }
+  layout {
+    sequence: {{layout.sequence}}
+    slot: {{layout.slot}}
+  }
+  appearance {
+    template: {{appearance.template}}
+    templateOptions: #DEFAULT#
+  }
+)
+```

package/skills/apexlang/templates/region-components/faceted-search/README.md

@@ -0,0 +1,22 @@
+# Faceted Search Templates
+
+## Purpose
+Canonical guidance for the `faceted-search` region family, including shared contract loading and supported scenario variants.
+
+## Usage
+- Load `faceted-search._common.md` first to align variable contracts, guardrails, and required inputs.
+- Choose a scenario variant matching the requested interaction pattern, data source type, and page composition context.
+- For emitted child metadata, use `facet (...)` blocks in this family. Do not guess between `facet` and `filter`; follow the canonical example and shared contract here.
+- Prefer the canonical emitted facet type values shown in this family and the page example: `search`, `checkboxGroup`, `radioGroup`, `selectList`, and `range`.
+- Keep facet source data types runtime-safe: date/time facets use `dataType: date`, numeric facets use `dataType: number`, and string facets omit `source.dataType` instead of emitting SQL/report tokens such as `varchar2` or `VARCHAR2`.
+- For checkbox/radio facets, cap visible values with `listEntries.maxDisplayedEntries: 10`; for likely high-cardinality value lists, also set `listEntries.displayFilterInitially: true`.
+- Preserve canonical path references and markdown-first conventions when updating workflow or registry links.
+
+## Template Catalog
+- `faceted-search._common.md`
+- `faceted-search.standard.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Update catalogs and usage notes whenever templates are added, removed, or renamed.
+- Keep family guidance aligned with page-level standards in memory-bank rules and with scenario coverage in this folder.

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

@@ -0,0 +1,179 @@
+---
+templateId: region.faceted-search.common
+componentType: region
+version: 1.2
+description: Shared contract for left-column faceted-search regions and results region wiring.
+---
+
+# Purpose
+
+Document the native faceted-search region shell and its filter child metadata boundary. Define required wiring between the faceted-search region and its filtered results region for the standard left-column faceted-search page pattern.
+
+# Generation Rules (MANDATORY)
+
+1. Use the dedicated `region-faceted-search` template.
+2. Treat the filtered-region reference as mandatory.
+3. Document facets as separate child metadata from the region shell.
+4. Default the faceted-search region shell to `appearance.template: @/standard` unless a page pattern documents a deliberate exception.
+5. Default the faceted-search region layout to the left-column slot (`leftColumn`) for the standard page pattern; do not model the sidebar with `body` `columnSpan` coordinates.
+6. Emit child facets with `facet (...)` blocks in this family.
+7. Use the canonical emitted facet type values from the checked-in example set: `search`, `checkboxGroup`, `radioGroup`, `selectList`, and `range`.
+
+# Variable Contract
+
+| Name | Required | Type | Notes |
+|------|----------|------|-------|
+| regionStaticId | yes | string | Region identifier. |
+| name | yes | string | Display name. |
+| resultsRegionStaticId | yes | string | Static id of target results region. |
+| searchRegionStaticId | yes | string | Static id of faceted-search region. |
+| source.filteredRegion | yes | ref | Must reference results region id. |
+| layout.slot | optional | string | Default to `leftColumn` for the standard pattern. |
+| appearance.template | optional | string | Default to `@/standard`. |
+| compactNosThreshold setting | yes | number | Standard default is `10000`. |
+| showCurrentFacets setting | yes | boolean/string | Standard default is `true`; use `selector` only for explicit selector-mode requests. |
+| showTotalRowCount setting | yes | boolean | Standard default is `true`. |
+| displayChartForTopNValues setting | optional | positive integer | Opt-in only for explicit chart/top-N requests; common value is `10`. |
+| currentFacetsSelector setting | conditional | selector | Required only when `showCurrentFacets: selector` is emitted. |
+| facets | optional | array | Facet definitions and LOV/source metadata. |
+| searchFacet.enabled | optional | boolean | Enables free-text facet search. |
+
+## Facet Child Contract
+
+- Child block name: `facet (...)`
+- Canonical emitted `type` values:
+  - `search`
+  - `checkboxGroup`
+  - `radioGroup`
+  - `selectList`
+  - `range`
+- For discrete facets (`checkboxGroup`, `radioGroup`, `selectList`), prefer:
+  - `lov { type: distinctValues }`
+- For `checkboxGroup` and `radioGroup` facets, emit:
+  - `listEntries { maxDisplayedEntries: 10 }`
+  - add `displayFilterInitially: true` when the facet can have many values, especially Product, Customer, Store, Assignee, Owner, User, Employee, Supplier, Email, SKU, name, or title facets
+- For free-text search facets, use:
+  - `source { dbColumns: COL_A,COL_B,... }`
+- For range facets, use:
+  - `source { databaseColumn: <col> dataType: number|date }`
+- For date/time facets, use `dataType: date` even when the schema column is `TIMESTAMP`; the facets runtime expects the date facet type, not `timestamp` or `varchar2`.
+- For string/discrete facets, omit `source.dataType`; never emit `varchar2`, `VARCHAR2`, `STRING`, or report-column data type labels in faceted-search facet sources.
+
+## Minimal Child Examples
+
+```apexlang
+facet P7_F_SEARCH (
+  type: search
+  label {
+    label: Search
+  }
+  layout {
+    sequence: 10
+  }
+  source {
+    dbColumns: PRODUCT_NAME,STORE_NAME
+  }
+)
+
+facet P7_F_STATUS (
+  type: selectList
+  label {
+    label: Order Status
+  }
+  lov {
+    type: distinctValues
+  }
+  layout {
+    sequence: 20
+  }
+  source {
+    databaseColumn: ORDER_STATUS
+  }
+)
+
+facet P7_F_PRODUCT (
+  type: checkboxGroup
+  label {
+    label: Product
+  }
+  lov {
+    type: distinctValues
+  }
+  layout {
+    sequence: 25
+  }
+  listEntries {
+    maxDisplayedEntries: 10
+    displayFilterInitially: true
+  }
+  source {
+    databaseColumn: PRODUCT_NAME
+  }
+)
+
+facet P7_F_ORDER_DATE (
+  type: range
+  label {
+    label: Order Date
+  }
+  layout {
+    sequence: 30
+  }
+  source {
+    databaseColumn: ORDER_DATETIME
+    dataType: date
+  }
+)
+```
+
+# Output Template – Full
+
+```apexlang
+region {{regionStaticId}} (
+  name: {{name}}
+  type: facetedSearch
+  source {
+    filteredRegion: @{{source.filteredRegion}}
+  }
+  layout {
+    sequence: {{layout.sequence}}
+    slot: {{layout.slot}}
+  }
+  appearance {
+    template: {{appearance.template}}
+    templateOptions: #DEFAULT#
+  }
+  settings {
+    compactNosThreshold: 10000
+    showCurrentFacets: true
+    showTotalRowCount: true
+  }
+  {{facets}}
+)
+```
+
+# Conditional Rendering Rules
+
+- Emit the standard three-property `settings` block by default: `compactNosThreshold: 10000`, `showCurrentFacets: true`, and `showTotalRowCount: true`.
+- Keep current-facets selector configuration in `settings`, but only for explicit selector-mode requests.
+- When selector mode is requested, emit both `showCurrentFacets: selector` and a concrete `currentFacetsSelector` value. Do not invent an external target unless the generated page also creates a clearly named target.
+- Emit `displayChartForTopNValues` only for explicit chart/top-N requests; use a positive integer such as `10`.
+- Do not merge facet child definitions into the region shell description.
+- The standard page-level composition for this region family is breadcrumb in `breadcrumbBar`, results in `body`, and faceted search in `leftColumn`.
+- When the request calls for Product, Store, Status, or other discrete value filters, start from `selectList`, `checkboxGroup`, or `radioGroup` plus `lov { type: distinctValues }` instead of internal `NATIVE_*` token guessing.
+
+# Guardrails
+
+- `filteredRegion` must reference an existing results region.
+- Facet columns must exist in the results region source query.
+- Facet names must be page-scoped and collision-safe (for example `P{page}_FACET_*` or `FS_*`); avoid generic names like `FACET_SEARCH`.
+- `listEntries.maxDisplayedEntries` is allowed only when facet `type` is `checkboxGroup` or `radioGroup`.
+- For `checkboxGroup` and `radioGroup` facets, set `listEntries.maxDisplayedEntries`; default to `10` and keep deliberate values between `5` and `15`.
+- For high-cardinality value lists, set `listEntries.displayFilterInitially: true`.
+- For all other facet types (including `range`), omit the `listEntries` block.
+- Facet source data types are not generic SQL metadata. Use only `date` for date/time facets and `number` for numeric facets. Omit `source.dataType` for string facets so the runtime does not receive unsupported `VARCHAR2` facet metadata.
+- Do not emit internal runtime tokens such as `NATIVE_SEARCH` or `NATIVE_SELECT_LIST` in APEXlang unless a compiler-validated example explicitly requires them; the canonical emitted DSL in this repo uses the simple type names above.
+- Keep facet definitions declarative; avoid custom JS unless required.
+- Do not use `slot: body` plus `columnSpan` values for the canonical faceted-search sidebar.
+- Do not assume a page-header wrapper region; breadcrumb placement belongs directly in `breadcrumbBar` for the standard pattern.
+- Metadata export lookup: search for `Faceted Search`, the filtered-region reference, and child facet metadata.

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

@@ -0,0 +1,19 @@
+---
+templateId: faceted-search.index
+componentType: template
+version: 1.1
+imports:
+  - faceted-search._common.md
+description: Routing entrypoint for faceted-search templates.
+---
+
+# Purpose
+
+Primary routing entrypoint for `faceted-search` templates.
+
+# Load Order
+
+1. Load this file.
+2. Load `faceted-search._common.md`.
+3. Load one scenario template in this folder.
+4. Load `faceted-search.button-bar.md` when the generated active-facets bar is in scope.

package/skills/apexlang/templates/region-components/faceted-search/faceted-search.button-bar.md

@@ -0,0 +1,43 @@
+---
+templateId: region.faceted-search.button-bar
+componentType: region
+version: 1.0
+imports:
+  - faceted-search._common.md
+description: Companion button-bar region generated for faceted search pages.
+---
+
+# Purpose
+
+Document the generated button-bar support region used to render active facets above the result region.
+
+# Generation Rules (MANDATORY)
+
+1. Load `faceted-search._common.md` first.
+2. Use this region only as a support region for faceted search.
+
+# Variable Contract
+
+## Required Variables
+
+- `source.htmlCode`
+- `appearance.template`
+
+# Output Template – Full
+
+```apexlang
+region button-bar (
+  name: Button Bar
+  type: staticContent
+  source {
+    htmlCode: <div id="active_facets"></div>
+  }
+  appearance {
+    template: @/buttons-container
+  }
+)
+```
+
+# Conditional Rendering Rules
+
+- Keep this companion region separate from the faceted-search shell.

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

@@ -0,0 +1,46 @@
+---
+templateId: region.faceted-search.standard
+componentType: region
+version: 1.0
+imports:
+  - faceted-search._common
+description: Standard left-column faceted-search region paired with report results.
+---
+
+# Output Template
+
+```
+region {{searchRegionStaticId}} (
+  name: {{name}}
+  type: facetedSearch
+  source {
+    filteredRegion: @{{resultsRegionStaticId}}
+  }
+  layout {
+    sequence: {{layout.sequence}}
+    slot: leftColumn
+  }
+  appearance {
+    template: {{appearance.template}}
+    templateOptions: #DEFAULT#
+  }
+  settings {
+    compactNosThreshold: 10000
+    showCurrentFacets: true
+    showTotalRowCount: true
+  }
+  {{facets}}
+)
+```
+
+# Standard Notes
+
+- Emit child facets as `facet (...)` blocks after the region shell.
+- Default generated faceted-search regions use only the `settings` block values `compactNosThreshold: 10000`, `showCurrentFacets: true`, and `showTotalRowCount: true`.
+- Emit `displayChartForTopNValues` only for explicit chart/top-N requests; use a positive integer such as `10`.
+- Emit selector mode only for explicit external/current-facets selector requests. Pair `showCurrentFacets: selector` with a concrete `currentFacetsSelector` value.
+- For the common “Product / Order Date / Order Status / Store” shape:
+  - Product: `type: search` with `source.dbColumns`
+  - Order Date: `type: range`
+  - Order Status: `type: selectList`, `checkboxGroup`, or `radioGroup` with `lov { type: distinctValues }`
+  - Store: `type: selectList`, `checkboxGroup`, or `radioGroup` with `lov { type: distinctValues }`

package/skills/apexlang/templates/region-components/form/README.md

@@ -0,0 +1,26 @@
+# Form Templates
+
+## Purpose
+Canonical guidance for the `form` region family, including shared contract loading and supported scenario variants.
+
+## Usage
+- Load `form._index.md` first.
+- Load `form._common.md` next to align variable contracts, guardrails, and required inputs.
+- Load `form._template_options.md` when the request changes form-region or companion button-region `appearance.templateOptions`.
+- Load `form._items._common.md` for canonical form item contracts.
+- Load `form._processes._common.md` for canonical process linkage and placeholders.
+- Load one scenario variant matching the requested interaction pattern and data source type.
+
+## Template Catalog
+- `form._index.md`
+- `form._common.md`
+- `form._template_options.md`
+- `form._items._common.md`
+- `form._processes._common.md`
+- `form.basic.md`
+- `form.rest-source.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Update catalogs and usage notes whenever templates are added, removed, or renamed.
+- Keep family guidance aligned with page-level standards in memory-bank rules and with scenario coverage in this folder.

package/skills/apexlang/templates/region-components/form/form._common.md

@@ -0,0 +1,112 @@
+---
+templateId: region.form.common
+componentType: region
+version: 1.0
+description: Shared contract for form regions.
+---
+
+# Purpose
+
+Standardize the variable contract, guardrails, and template skeleton for form region scenarios. Document the native `form` region shell emitted by the current generator.
+
+---
+
+# Generation Rules (MANDATORY)
+
+1. Load `references/policies/memory-bank/30-pages/apex.form.md` and related logic/SQL rules before drafting form regions.
+2. Use the dedicated `region-form` template.
+3. Keep edit operations explicit in the `edit` block.
+4. Map items to table columns or REST attributes consistently; keep form region sources aligned with processes.
+5. Pair form regions with initialization and automatic row processing templates as needed.
+6. Treat companion dialog buttons as a separate generated support region.
+7. Default form regions to `appearance.template: @/standard`; keep `@/buttons-container` only for the companion buttons region.
+
+---
+
+# Variable Contract
+
+| Name | Required | Type | Notes |
+|------|----------|------|-------|
+| regionStaticId | yes | string | Identifier used after the `region` keyword (e.g., `FORM_REGION`). |
+| name | yes | string | Builder display name. |
+| type | yes | enum | Always `form`. |
+| source.location | yes | enum | `localDatabase`, `restSource`, etc. |
+| source.type | conditional | enum | Use only for typed non-table source modes such as `sqlQuery`, `functionBody`, or `propertyGraph`. Omit it for the standard table-backed path. |
+| source.sqlQuery | conditional | sql | Required for `source.type: sqlQuery`. |
+| source.plsqlFunctionBody | conditional | plsql | Required for `source.type: functionBody`; the body must return SQL text. |
+| source.tableName | conditional | string | Required for the standard table-backed local-database path; omit `source.type` when `tableName` is used. |
+| source.restSource | conditional | string | REST Data Source alias when using `restSource`. |
+| layout.sequence | yes | number | Region order in the page slot. |
+| layout.slot | yes | enum | Slot the region occupies (e.g., `BODY`). |
+| appearance.template | yes | string | Region template reference; default to `@/standard`. |
+| appearance.templateOptions | optional | array | Additional modifiers (`#DEFAULT#` default); use the documented accepted values in `form._template_options.md`, keep `#DEFAULT#` standalone, and do not substitute emitted CSS class strings. |
+| edit.enabled | optional | boolean | Enables automatic DML for the form region; when emitted, use `true`. |
+| serverSideCondition.* | optional | condition | Visibility gating. |
+| security.authorizationScheme | optional | string | Authorization scheme alias. |
+
+---
+
+# Output Template – Full
+
+```
+region {{regionStaticId}} (
+  name: {{name}}
+  type: form
+  source {
+    location: {{source.location}}
+    tableName: {{source.tableName}}
+    sqlQuery:
+        ```sql
+        {{source.sqlQuery}}
+        ```
+    plsqlFunctionBody:
+        ```plsql
+        {{source.plsqlFunctionBody}}
+        ```
+    restSource: @{{source.restSource}}
+  }
+  layout {
+    sequence: {{layout.sequence}}
+    slot: {{layout.slot}}
+  }
+  appearance {
+    template: {{appearance.template}}
+    templateOptions: {{appearance.templateOptions}}
+  }
+  edit {
+    enabled: {{edit.enabled}}
+  }
+  serverSideCondition {
+    type: {{serverSideCondition.type}}
+    item: {{serverSideCondition.item}}
+    {{serverSideCondition.comparisonAttribute}}: {{serverSideCondition.comparisonValue}}
+  }
+  security {
+    authorizationScheme: @{{security.authorizationScheme}}
+  }
+)
+```
+
+---
+
+# Conditional Rendering Rules
+
+- Remove optional blocks (`edit`, `serverSideCondition`, `security`) when not required.
+- Include `restSource` only when `location: restSource` is used.
+- For table-backed local-database forms, emit `source.tableName` only and omit `source.type`.
+- For typed local-database forms, emit exactly one typed mode such as `source.type: sqlQuery` + `source.sqlQuery` or `source.type: functionBody` + `source.plsqlFunctionBody`.
+- Ensure table/column definitions align with the form's source and associated processes.
+- Pair form regions with `form-initialization` and `form-automatic-row-processing` when using table or REST DML.
+- For item colon-list membership conditions, render `comparisonAttribute` as `list`; keep `value` for other comparison types.
+- Keep dialog buttons outside the form region itself.
+- For form regions, emit only `edit.enabled`; do not emit `edit.add`, `edit.update`, `edit.delete`, or `edit.allowedOperations`.
+
+---
+
+# Guardrails
+
+- Keep form region SQL lightweight; prefer views or packaged APIs for complex logic.
+- Validate REST sources support required operations before enabling automatic DML.
+- Ensure session state protection is configured via item templates and processes.
+- Treat `edit.add`, `edit.update`, and `edit.delete` as interactive-grid borrowing errors when the region type is `form`.
+- Metadata export lookup: search for `Form`, `NATIVE_FORM`, and form edit-operation properties.

package/skills/apexlang/templates/region-components/form/form._index.md

@@ -0,0 +1,23 @@
+---
+templateId: region.form.index
+componentType: region
+version: 1.0
+imports:
+  - form._common.md
+  - form._items._common.md
+  - form._processes._common.md
+description: Routing entrypoint for form region templates.
+---
+
+# Purpose
+
+Primary routing entrypoint for `form` region templates.
+
+# Load Order
+
+1. Load this file.
+2. Load `form._common.md`.
+3. Load `form._items._common.md`.
+4. Load `form._processes._common.md`.
+5. Load `form.dialog-buttons.md` when the scenario is a dialog form.
+6. Load one scenario template in this folder.