pi-apexlang 0.1.0

package/skills/apexlang/references/domains/page-components/page-items.md

@@ -0,0 +1,68 @@
+---
+name: page-items
+description: Configure Oracle APEX page items the Items skill. Use when Codex must add or adjust page items under Apex Developer guardrails.
+---
+
+# Reference Package — Page Items & LOVs
+
+**Parent Entries:** `references/domains/README.md` (domain), `SKILL.md` (router)
+
+## Purpose
+- Add or modify page items with correct types, LOVs, format masks, validations, and computations.
+- Leverage canonical item templates under `templates/items/`.
+
+## When to Trigger
+- The user requests new items or updates to existing items (type, LOV, default, validation, computation).
+- Use alongside Region/Template sub-skills for full page composition.
+
+## Required Inputs
+- Item names, desired types (text, select list, checkbox, etc.)
+- LOV source (static or SQL) with value/display columns
+- Validation requirements and error messages
+- Computation context (execution point, body, target item)
+
+## Authoritative Policies
+- `references/policies/memory-bank/00-guard/ai.guard.md`
+- `references/policies/memory-bank/10-global/apex.global.md`
+- `references/policies/memory-bank/40-components/apex.templates.md`
+- `references/policies/memory-bank/40-components/apex.items.md`
+- `references/policies/memory-bank/20-data/apex.sql.md`
+- `references/policies/memory-bank/20-data/apex.logic.md`
+- `references/policies/governance/00-governance.md`
+
+## Operational References
+- Templates: `templates/items/*`
+- `references/domains/page-components/page-items/templates.md`
+- `references/domains/page-components/page-items/registry.md`
+- Business-logic coupling: `references/domains/README.md` for computations/validations workflows
+
+## Execution Agents
+- `references/ops/sqlcl-agents/00-connection-gate.md` when DB validation is needed.
+- `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md` for import-ready completion checks.
+- `references/ops/runtime-gates/01-direct-sqlcl-import.md` for online import runs.
+- The internal generate/review/fix loop remains under `references/workflows/apex-generation/agents/`.
+
+## Guardrails
+- Computations: `type: expression` for PL/SQL expressions; scalar SQL computations require `type: sqlQuerySingleValue`, and multi-value SQL computations require `type: sqlQueryMultipleValues`.
+- LOV SQL wrapped in triple backticks; no fabricated columns.
+- Validation logic adheres to `apex.logic` policies (invokeApi, named notation, SSC catalog).
+- Missing inputs must be flagged (no guesses for PK or LOV details).
+- Default visible item templates and label presentation are owned by the shared composition contract in `references/policies/memory-bank/40-components/apex.templates.md`, not by styling workflows.
+
+## Agent Flow
+- Invoke `references/ops/sqlcl-agents/00-connection-gate.md` when DB validation is needed.
+- Use the internal generate -> review -> fix loop via Apex Developer agents, referencing business-logic prompts when computations/validations are involved.
+- For import-ready runs, execute `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md`.
+- After runtime gate pass, import via `references/ops/runtime-gates/01-direct-sqlcl-import.md` proceeds automatically.
+
+## Outputs & Acceptance
+- Item definitions updated in target page file.
+- LOV definitions added to shared components if required.
+- Computations/validations logged with correct request guards.
+
+## References
+- `references/domains/page-components/page-items/templates.md` (template paths)
+- `references/domains/page-components/page-items/registry.md` (keyword → template mapping)
+- `references/domains/README.md` for validations/computations/dynamic actions
+
+Use this package for any page item, LOV, validation, or computation tasks within Apex Developer.

package/skills/apexlang/references/domains/page-components/page-patterns/registry.md

@@ -0,0 +1,11 @@
+# Component Registry Excerpts — Page Patterns
+
+| Keyword | Registry Entry | Notes |
+|---------|----------------|-------|
+| `page` | `page` | Default scaffold; loads `30-pages/apex.page.md` |
+| `navigation` | `navigation` | Appends to shared-components/lists.apx |
+| `breadcrumb` | `breadcrumb` | Appends entry in shared-components/breadcrumbs.apx |
+| `page-group` | `page-group` | Injects `pageGroup` at page root |
+| `help-text-batch` | `references/domains/universal-attr-config/workflow-help-text-batch.md` | Use when adding inline help to page components |
+
+Consult the full `components.registry.json` for additional synonyms when matching user prompts.

package/skills/apexlang/references/domains/page-components/page-patterns/templates.md

@@ -0,0 +1,35 @@
+# Template References — Page Patterns
+
+## Authoritative Policies
+- `references/policies/governance/00-governance.md`
+- `references/policies/memory-bank/00-guard/ai.guard.md`
+- `references/policies/memory-bank/10-global/apex.global.md`
+- `references/policies/memory-bank/30-pages/apex.page.md`
+- `references/policies/memory-bank/30-pages/apex.form.md`
+- `references/policies/memory-bank/30-pages/apex.interactive-report.md`
+- `references/policies/memory-bank/30-pages/apex.dashboard.md`
+- `references/policies/memory-bank/30-pages/apex.chart-page.md`
+- `references/policies/memory-bank/30-pages/apex.calendar.md`
+- `references/policies/memory-bank/30-pages/apex.map-page.md`
+- `references/policies/memory-bank/20-data/apex.logic.md` (for server-side conditions)
+
+## Operational References
+Canonical page templates reside under `templates/page-examples/`:
+
+- `templates/page-examples/global_page_0/global_page_0._index.md`
+- `templates/page-examples/home-page/home-page._index.md`
+- `templates/page-examples/login-page/login-page._index.md`
+- `templates/page-examples/blank-page/blank-page._index.md`
+- `templates/page-examples/interactive-report-page/interactive-report-page._index.md`
+- `templates/page-examples/interactive-grid/interactive-grid._index.md`
+- `templates/page-examples/form-page/form-page._index.md`
+- `templates/page-examples/dashboard-page/dashboard-page._index.md`
+- `templates/page-examples/classic-report-page/classic-report-page._index.md`
+- `templates/page-examples/calendar-page/calendar-page._index.md`
+- `templates/page-examples/map-page/map-page._index.md`
+- `templates/page-examples/faceted-search/faceted-search._index.md`
+- `templates/page-examples/task-definition-my-tasks-page/task-definition-my-tasks-page._index.md`
+- `templates/page-examples/task-definition-initiated-tasks-page/task-definition-initiated-tasks-page._index.md`
+- `templates/page-examples/task-definition-task-details/task-definition-task-details._index.md`
+
+Use `assets/rules-mapping.json` to load the minimal subset required for each request.

package/skills/apexlang/references/domains/page-components/page-patterns.md

@@ -0,0 +1,119 @@
+---
+name: page-patterns
+description: Scaffold Oracle APEX page-patterns, page or app navigation, and breadcrumbs using the page-scaffolding workflow. Use when Codex must create new APEXlang pages or adjust page-level metadata under the Page Scaffolding & Navigation recipe.
+---
+
+# Reference Package — Page Patterns & Navigation
+
+**Parent Entries:** `references/domains/README.md` (domain), `SKILL.md` (router)
+
+This skill executes the page-patterns playbook defined in this repository. It ensures new pages follow standards for naming, navigation, breadcrumbs, and page groups, while honoring guardrails.
+
+---
+
+## Purpose
+- Add a new page with correct metadata, navigation list entry, and breadcrumb.
+- Apply page-group assignments and server-side conditions using approved catalog types.
+
+## When to Trigger
+- The user requests a new page scaffold, navigation/breadcrumb updates, or page-group assignments.
+- Use for page-level adjustments before adding specific regions or items.
+
+---
+
+## Required Inputs
+- `page_number`
+- `navigation_list_target`
+- `breadcrumb_target`
+- Optional: `page_group` (e.g., `@administration`)
+- Flags: `add_navigation` (default true for non-modal pages), `add_breadcrumb` (default true for non-modal pages)
+
+### Progressive Prompts (Server-Side Conditions)
+1. “Do any components on this page require a server-side condition? (Reply ‘none’ to skip.)”
+2. If yes, capture `scope` (button, region, item, dynamic action, or process) and `identifier`.
+3. Request the catalog `type` or SSC token from `references/policies/memory-bank/20-data/apex.logic.md`.
+4. Collect required attributes (`item`, `value/list`, `requestValue`, `plsqlExpression`, `sqlQuery`, etc.). Missing answers halt the workflow.
+
+---
+
+## Authoritative Policies
+- `references/policies/memory-bank/00-guard/ai.guard.md`
+- `references/policies/governance/00-governance.md`
+- `assets/rules-mapping.json`
+- Load minimal domain rules from:
+  - `references/policies/memory-bank/10-global/apex.global.md`
+  - `references/policies/memory-bank/30-pages/apex.page.md`
+  - `references/policies/memory-bank/20-data/apex.logic.md` (only when SSC is requested)
+
+## Operational References
+- `references/domains/page-components/page-patterns/templates.md`
+- `references/domains/page-components/page-patterns/registry.md`
+- APEX page templates under `templates/page-examples/**`
+- Do not use `applications/**` as a page-pattern source; target-app reads remain integration-only.
+
+## Execution Agents
+- `references/ops/sqlcl-agents/00-connection-gate.md` (pre-agent saved-connection resolution).
+- `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md` (import-ready completion checks).
+- The internal generate/review/fix loop remains under `references/workflows/apex-generation/agents/`.
+- `references/ops/runtime-gates/01-direct-sqlcl-import.md` for online import runs.
+
+---
+
+## Rule Loading (Minimal Context)
+1. `references/policies/memory-bank/00-guard/ai.guard.md`
+2. `references/policies/governance/00-governance.md`
+3. `assets/rules-mapping.json`
+4. Via rules map:
+   - `references/policies/memory-bank/10-global/apex.global.md`
+   - `references/policies/memory-bank/30-pages/apex.page.md`
+   - `references/policies/memory-bank/20-data/apex.logic.md` only when server-side conditions are requested
+5. Templates referenced as needed from `templates/**`
+
+---
+
+## Agent Flow Integration
+- Invoke `references/ops/sqlcl-agents/00-connection-gate.md` (Pre-Agent 0) to resolve `db_connection_name` for live metadata and roundtrip work.
+- The apexdev master standards use a transient temp workspace outside the repo for generation and review, require an internal confidence score of at least `0.95`, and publish to `applications/<target-app>/...` only after the resolved live runtime action succeeds when a live roundtrip is requested.
+- For import-ready runs, execute `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md`.
+- After runtime gate pass, call `references/ops/runtime-gates/01-direct-sqlcl-import.md` automatically; do not wait for a separate import approval.
+
+---
+
+## Outputs & Acceptance Gates
+- When `add_navigation: true`: append entry to `shared-components/lists.apx` under `navigation-menu`, linking `f?p=&APP_ID.:&PAGE_ID.:&APP_SESSION.::&DEBUG.:::` with appropriate sequence.
+- When `add_navigation: true` and the navigation entry emits `isCurrent { type: pages }`, set `pages` to the new entry's own page id only.
+- If a related page also needs navigation, create a separate list entry for that page instead of appending its page id to another entry's `isCurrent.pages` value.
+- When `add_breadcrumb: true`: append breadcrumb entry to `shared-components/breadcrumbs.apx`.
+- When `add_breadcrumb: true`: add a visible page breadcrumb region with `type: breadcrumb` and `source.breadcrumb: @breadcrumb`.
+- When `page_group` provided: set `pageGroup` at the page root (not inside appearance/nav/css/security).
+- Fail if a non-modal user page lacks required nav, a matching breadcrumb entry, or a visible breadcrumb region when flags are true.
+- Fail if a requested server-side condition is missing catalog type or required attributes.
+
+---
+
+## Guardrails to Enforce
+- Minimal rule loading; never touch `.archive/`.
+- No invented attributes or UT classes.
+- Server-side conditions must use supported catalog types from `20-data/apex.logic.md`.
+- For navigation current-state metadata, do not emit comma-separated `isCurrent.pages` values for different pages that already have their own navigation entries.
+- Respect process policy split when adding processes (page process invokeApi-default with thin-wrapper exception; appProcess executeCode-only). Defer to page-specific workflows for full process logic.
+- Record Missing Inputs instead of fabricating values.
+
+---
+
+## Completion Checklist
+1. Working page changes stay in the transient temp workspace until review passes.
+2. The internal review loop records PASS/CONFIDENCE in the compact runtime report when the workflow reaches runtime gates.
+3. Final page artifact updates `applications/app_###/pages/` unless the calling master passes a resolved application path.
+4. Execute the import runtime gate for import-ready runs.
+5. Run Import Changes Gate after the live APEXlang check succeeds.
+
+---
+
+## Examples
+- “Create Page 42 ‘Customer Dashboard’, add it to Navigation Menu under Administration, breadcrumb ‘Customers’, assign page group `@administration`.”
+- “Add a new modal page 120 and hide its navigation entry; ensure no breadcrumb is emitted.”
+
+---
+
+Use this package whenever page scaffolding or navigation adjustments are needed prior to populating regions and items.

package/skills/apexlang/references/domains/page-components/regions/calendar/workflow-calendar-link-targets.md

@@ -0,0 +1,39 @@
+# Workflow: Calendar Link Targets
+
+Purpose
+- Resolve `settings.createLink` and `settings.viewEditLink` for calendar regions without inferring downstream page targets.
+
+Required inputs
+- Calendar source table/view and primary key column.
+- Whether `createLink`, `viewEditLink`, or both are in scope.
+- For `createLink`, whether to use an existing form page or create a new same-table modal form page.
+- For `viewEditLink`, whether to use an existing report page or create a new report page.
+- For a new `viewEditLink` target, the chosen report type: Interactive Report or Classic Report.
+
+Clarify — progressive prompts
+- For `createLink`: “Do you want to use an existing form page, or should I create a new form page on the same table?”
+- If existing form page: ask for the target page identifier and target item mapping.
+- If new form page: gather the page number and any item mapping needed from the calendar.
+- For `viewEditLink`: “Do you want to use an existing report page, or should I create a new report page?”
+- If existing report page: ask for the target page identifier and the page item that receives the calendar primary key.
+- If new report page: “Should the new report page be an Interactive Report or a Classic Report?”
+- For any new report page: gather the page number, the PK-holding page item, and the filter contract for the report SQL.
+
+Stop conditions
+- If the existing-vs-new decision is unresolved after the single clarification round, stop with `Missing Inputs`.
+- If a new report page is requested and the report type is not chosen, stop with `Missing Inputs`.
+- If a report target lacks the PK item/filter contract, stop with `Missing Inputs`.
+
+Downstream workflows
+- New form page from `createLink`:
+  - `references/domains/page-components/regions/form/workflow-modal-crud-form.md`
+- New Interactive Report page from `viewEditLink`:
+  - `references/domains/page-components/regions/interactive-report/workflow-interactive-report.md`
+- New Classic Report page from `viewEditLink`:
+  - `references/policies/memory-bank/30-pages/apex.classic-report.md`
+  - `templates/page-examples/classic-report-page/classic-report-page._index.md`
+
+References
+- `references/policies/memory-bank/00-guard/ai.guard.md`
+- `references/policies/memory-bank/30-pages/apex.calendar.md`
+- `templates/region-components/calendar/calendar._common.md`

package/skills/apexlang/references/domains/page-components/regions/chart/workflow-charts.md

@@ -0,0 +1,30 @@
+# Workflow: Charts
+
+Purpose
+- Generate charts with correct series queries, axes, and formatting.
+- Enforce axis value format enums; only the documented Oracle APEX values are allowed (dateShort/dateMedium/dateLong/dateFull, timeShort/timeMedium/timeLong/timeFull, datetimeShort/datetimeMedium/datetimeLong/datetimeFull, decimal/currency/percent). `format: text` must never be emitted.
+
+Required inputs
+- Chart type, series query, axes/labels, formatting.
+
+Clarify — progressive prompts
+- Do any chart regions, related buttons, or items require a server-side condition? (Answer "none" to skip.)
+- If yes, capture component scope (region, button, item, dynamic action, or process) and identifier.
+- Provide the desired condition type or business rule; valid types are listed in references/policies/memory-bank/20-data/apex.logic.md.
+- Gather required attributes for that type (item, value/list, request value, plsqlExpression, sqlQuery, etc.). Missing answers block the workflow.
+
+Load
+- references/policies/memory-bank/00-guard/ai.guard.md
+- references/policies/memory-bank/10-global/apex.global.md
+- references/policies/memory-bank/30-pages/apex.chart-page.md
+- references/policies/memory-bank/20-data/apex.sql.md
+
+Composition reference
+- references/policies/memory-bank/40-components/apex.templates.md for shared template and layout defaults.
+
+References
+- references/policies/governance/00-governance.md
+- assets/rules-mapping.json
+
+Completion
+- On user approval, collect ``db_connection_name`, `app_path`, and `application_id` (if not already set), run `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md`, then route to `references/ops/runtime-gates/01-direct-sqlcl-import.md`.

package/skills/apexlang/references/domains/page-components/regions/dashboard/workflow-dashboard.md

@@ -0,0 +1,51 @@
+# Workflow: Dashboard (KPIs/Cards)
+
+Purpose
+- Create dashboards with KPI regions/cards and consistent layout.
+
+Required inputs
+- KPI definitions, source queries, layout hints.
+
+Clarify — progressive prompts
+- Will any dashboard regions, buttons, or items use a server-side condition? (Answer "none" to skip.)
+- If yes, state the component scope (region, button, item, dynamic action, or process) and identifier.
+- Provide the desired condition type or business rule, referencing references/policies/memory-bank/20-data/apex.logic.md for valid options.
+- Collect the required attributes for that type (item, value/list, request value, plsqlExpression, sqlQuery, etc.). Missing answers block the workflow.
+
+Load
+- references/policies/memory-bank/00-guard/ai.guard.md
+- references/policies/memory-bank/10-global/apex.global.md
+- references/policies/memory-bank/30-pages/apex.layout.md
+- references/policies/memory-bank/30-pages/apex.dashboard.md
+- references/policies/memory-bank/20-data/apex.sql.md
+
+Layout defaults
+- Build a row plan before emitting regions.
+- Create a required `layout_row_plan` before emitting KPI strips, chart rows, report/detail rows, or side-by-side component rows.
+- `layout_row_plan` entries must include `slot`, `row`, `recipe`, and ordered `regions` static IDs.
+- KPI strips use one normalized Metric Card region with `recipe: metric-card-strip`.
+- Each `layout_row_plan` entry represents one physical row. Stacked full-width detail, contextual summary, and cards sections must be separate one-region entries; do not list multiple stacked sections in the same `regions` array.
+- Do not emit a generic `dashboard-chart-flow` recipe; split charts into explicit `two-up-equal` and `three-up-equal` entries.
+- Dashboard KPI Metric Card strips default to `appearance.template: @/blank-with-attributes`; use `@/standard` only when explicitly titled or landmarked visible region chrome is required.
+- Default chart rows:
+  - 2 charts: one `two-up-equal` row.
+  - 3 charts: one `three-up-equal` row.
+  - 4 charts: two `two-up-equal` rows.
+  - 5 charts: one `two-up-equal` row, then one `three-up-equal` row.
+  - More than 5 charts: repeat `two-up-equal` and `three-up-equal` rows, preferring balanced rows.
+- First chart in each row omits `startNewRow`; second-and-later charts in that row use `startNewRow: false`.
+- Do not literally stack multiple dashboard charts unless the user explicitly requests vertical stacking or a chart is intentionally a detail/full-width section.
+- Equal-width sibling rows must use sequence ordering plus `startNewRow: false` on second-and-later siblings.
+- Do not emit `column` / `columnSpan` for KPI strips or standard two-up / three-up dashboard rows.
+- Use explicit coordinates only when the requested dashboard is intentionally asymmetric.
+
+Composition reference
+- references/policies/memory-bank/40-components/apex.templates.md
+
+References
+- references/policies/governance/00-governance.md
+- assets/rules-mapping.json
+
+Completion
+- After Revision, prompt for ``db_connection_name`, `app_path`, and `application_id` if missing, run `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md`, then invoke `references/ops/runtime-gates/01-direct-sqlcl-import.md`.
+- Fail the workflow if a requested server-side condition is not mapped to a catalog type or lacks the required attributes.

package/skills/apexlang/references/domains/page-components/regions/form/workflow-modal-crud-form.md

@@ -0,0 +1,46 @@
+# Workflow: CRUD Form Region
+
+Purpose
+- Scaffold a CRUD form using the standard template and minimal rule set for modal, drawer, or normal embedded form targets.
+
+Required inputs
+- Target table/view, primary key, page number, button names (Save/Create/Delete).
+- Form presentation when it is not the default drawer end/right: standard modal dialog, drawer start/top/bottom, wizard modal dialog, popout-style standard modal dialog, or normal non-modal detail page.
+- If invoked from calendar `createLink`, keep the new modal form on the same base table/view as the calendar source and gather any explicit calendar-to-form item mappings.
+- Every generated form region must include PK source item mappings with `primaryKey: true`; this is mandatory for normal, modal, and drawer pages.
+
+Clarify — progressive prompts
+- Do any new or updated components in this modal form require a server-side condition? (Answer "none" to skip.)
+- If yes, specify the component scope (button, region, item, dynamic action, or process) and identifier.
+- Provide the desired condition type or business rule. Valid types are listed in references/policies/memory-bank/20-data/apex.logic.md under "Server-Side Condition Catalog".
+- Gather required attributes for the chosen type (for example, item name, comparison value/list, request value, plsqlExpression, sqlQuery). Missing answers block the workflow.
+
+Load
+- references/policies/memory-bank/00-guard/ai.guard.md
+- references/policies/memory-bank/10-global/apex.global.md (+ 10-global/apex.acronyms.md as needed)
+- references/policies/memory-bank/30-pages/apex.form.md
+- references/policies/memory-bank/40-components/apex.items.md (if item specifics/LOVs)
+- references/policies/memory-bank/20-data/apex.sql.md (query standards, LOV SQL)
+- references/policies/memory-bank/20-data/apex.logic.md (processes, validations, DAs)
+
+Clarify
+- ARP vs packaged PL/SQL for DML.
+- Presentation only when the user or spec asks for something other than the default: drawer end/right is the default for report row edit/create flows; standard modal dialog, drawer start/top/bottom, wizard modal, popout-style dialog, and normal detail page require explicit requirements or a page design reason.
+- LOV sources (static vs SQL) and FK behavior.
+- If invoked from calendar `createLink`, confirm the target item that receives the selected calendar value(s) such as start date.
+- Keep create-link selected-date prefill separate from drag/drop persistence. `&APEX$NEW_START_DATE.` is allowed for `createLink.items` date prefills, while `:APEX$NEW_START_DATE` / `:APEX$NEW_END_DATE` remain drag/drop persistence bind variables.
+
+Templates
+- templates/page-examples/form-page/form-page._index.md
+- templates/page-layout-templates/modal-dialog/modal-dialog._index.md
+- templates/page-layout-templates/drawer/drawer._index.md (only when drawer is explicitly selected)
+- templates/page-layout-templates/wizard-modal-dialog/wizard-modal-dialog._index.md (only for wizard-style flows)
+
+References
+- references/policies/governance/00-governance.md
+- assets/rules-mapping.json
+
+Completion
+- After Revision, confirm or prompt for ``db_connection_name`, `app_path`, and `application_id`, run `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md`, then invoke `references/ops/runtime-gates/01-direct-sqlcl-import.md`.
+- Fail the workflow if a requested server-side condition is not mapped to an accepted catalog type or lacks required attributes.
+- Fail the workflow if any generated form region has no source-mapped PK item with `primaryKey: true`.

package/skills/apexlang/references/domains/page-components/regions/interactive-report/workflow-interactive-report.md

@@ -0,0 +1,56 @@
+# Workflow: Interactive Report
+
+Purpose
+- Build an Interactive Report with validated SQL and consistent column configuration.
+
+Required inputs
+- Source table/view(s), page number, optional edit form link target.
+- If invoked from calendar `viewEditLink`, require the page item that will hold the calendar primary key and filter the report SQL with that item.
+
+Clarify — progressive prompts
+- Are any report components, buttons, or related items expected to use a server-side condition? (Answer "none" to skip.)
+- If yes, note the component scope (region, button, item, dynamic action, or process) and identifier.
+- Provide the desired condition type or business rule; the canonical list resides in references/policies/memory-bank/20-data/apex.logic.md.
+- Gather required attributes per type (item, value/list, request value, plsqlExpression, sqlQuery, etc.). Missing answers block the workflow.
+
+Load
+- references/policies/memory-bank/00-guard/ai.guard.md
+- references/policies/memory-bank/10-global/apex.global.md
+- references/policies/memory-bank/30-pages/apex.interactive-report.md
+- references/policies/memory-bank/20-data/apex.sql.md
+- When the Interactive Report includes user-entered text filters, generate `LOWER()`-normalized predicates for `=` / `!=` / `LIKE`.
+- Interactive Report column links must keep the column `type: plainText` and use a column-level `link { target: ... linkText: ... }`; never emit Classic Report-only `type: link`.
+
+Valid Interactive Report column link example:
+
+```apexlang
+column DNAME (
+  type: plainText
+  link {
+    target: {
+      page: 4
+      items: {
+        P4_DNAME: #DNAME#
+      }
+      clearCache: 4
+    }
+    linkText: #DNAME#
+  }
+)
+```
+
+Options
+- 40-components/apex.items.md (if report links to a form)
+- 20-data/apex.logic.md (DA refresh or server-side logic)
+- If invoked from calendar `viewEditLink`, use a dedicated page item for the calendar PK and bind it in `source.sqlQuery`.
+
+Templates
+- templates/page-examples/interactive-report-page/interactive-report-page._index.md
+
+References
+- references/policies/governance/00-governance.md
+- assets/rules-mapping.json
+
+Completion
+- After Revision, confirm or prompt for ``db_connection_name`, `app_path`, and `application_id`, run `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md`, then invoke `references/ops/runtime-gates/01-direct-sqlcl-import.md`.
+- Fail the workflow if a requested server-side condition is not tied to an accepted catalog type or lacks required attributes.

package/skills/apexlang/references/domains/page-components/regions/registry.md

@@ -0,0 +1,16 @@
+# Component Registry Excerpts — Regions
+
+| Keyword | Workflow / Component | Required Inputs |
+|---------|----------------------|-----------------|
+| `interactive-report` | `interactive-report` | SQL/table, columns |
+| `dashboard` | `dashboard` | KPI queries, region sequence |
+| `chart` | `chart-*` variants (area, bar, line, etc.) | Dataset SQL, measure/dimension columns |
+| `calendar` | `calendar` + `calendar-link-targets` | Date column, primary key column, create/view link target decisions |
+| `map` | `map` | Lat/Long or geocode columns |
+| `form` | `modal-crud-form` | Table, PK, CRUD buttons |
+| `dynamic-action` | `dynamic-action-*` | Trigger selectors, refresh targets |
+| `da-batch-apply` | `dynamic-action-batch` | Archetype, target pages |
+| `button-actions-batch` | `button-actions-batch` | Button names, target pages |
+| `computation-plsql-batch` | `computation-batch` | Computation type, logic |
+
+Refer to `components.registry.json` for synonyms and template references.

package/skills/apexlang/references/domains/page-components/regions/templates.md

@@ -0,0 +1,47 @@
+# Template & Rule References — Regions
+
+## Authoritative Policies
+- `references/policies/governance/00-governance.md`
+- `references/policies/memory-bank/00-guard/ai.guard.md`
+- `references/policies/memory-bank/10-global/apex.global.md`
+- `references/policies/memory-bank/20-data/apex.sql.md`
+- `references/policies/memory-bank/20-data/apex.logic.md`
+- `references/policies/memory-bank/40-components/apex.templates.md`
+- `references/policies/memory-bank/30-pages/apex.interactive-report.md`
+- `references/policies/memory-bank/30-pages/apex.dashboard.md`
+- `references/policies/memory-bank/30-pages/apex.chart-page.md`
+- `references/policies/memory-bank/30-pages/apex.calendar.md`
+- `references/policies/memory-bank/30-pages/apex.map-page.md`
+
+## Operational References
+### Region Templates
+- `templates/page-examples/interactive-report-page/interactive-report-page._index.md`
+- `templates/page-examples/dashboard-page/dashboard-page._index.md`
+- `templates/region-components/chart/chart._common.md`
+- `templates/page-examples/calendar-page/calendar-page._index.md`
+- `templates/page-examples/map-page/map-page._index.md`
+- `templates/region-components/static-content/static-content._common.md`
+- `templates/region-components/breadcrumb/breadcrumb._common.md`
+- `templates/region-components/collapsible-region/collapsible-region._common.md`
+- `templates/region-components/dynamic-content/dynamic-content._common.md`
+- `templates/region-components/interactive-report/interactive-report._common.md`
+- `templates/region-components/interactive-grid/interactive-grid._common.md`
+- `templates/region-components/interactive-grid/interactive-grid.standard.md`
+- `templates/region-components/interactive-grid/interactive-grid.region.md`
+- `templates/region-components/interactive-grid/interactive-grid._saved-report._common.md`
+- `templates/region-components/interactive-grid/interactive-grid._columns._common.md`
+- `templates/page-examples/interactive-grid/interactive-grid._index.md`
+- `templates/region-components/cards/cards._common.md`
+- `templates/region-components/chart/chart._common.md`
+- `templates/region-components/calendar/calendar._common.md`
+- `references/domains/page-components/regions/calendar/workflow-calendar-link-targets.md`
+- `templates/region-components/map/map._common.md`
+- For map work, use the attached canonical attribute vocabulary: `initialPositionAndZoom`, layer `source { ... }`, `columnMapping.geometryColumnDataType`, and `body` where the page pattern calls for it.
+- Prefer `source { tableName: ... }` for the baseline path, emit typed `source.type: sqlQuery` for new SQL-backed layers, and reserve `source.type: functionBody` for advanced fallback cases.
+- `templates/region-components/region-display-selector/region-display-selector._common.md`
+- `templates/region-components/search-config/search-config._common.md`
+- `templates/region-components/smart-filter-search/smart-filter-search._common.md`
+- `templates/business-logic/dynamic-actions/dynamic-actions.refresh-region-after-dialog.md`
+- `templates/business-logic/dynamic-actions/dynamic-actions.execute-server-side-code.md`
+
+Load only relevant files per region type using `assets/rules-mapping.json`.