pi-apexlang 0.1.0

package/skills/apexlang/templates/page-layout-templates/drawer/drawer.basic.md

@@ -0,0 +1,56 @@
+---
+templateId: page.drawer.basic
+component: page
+dslVersion: 1.0
+imports:
+  - drawer._common.md
+description: Baseline drawer page example with body content and a footer region host.
+---
+
+## Purpose
+Provide a baseline `@/drawer` example for side-sheet and sheet-style modal workflows.
+
+## Template
+```apexlang
+page 100 (
+    name: Drawer Details
+    alias: DRAWER-DETAILS
+    title: Drawer Details
+    appearance {
+        pageMode: modalDialog
+        dialogTemplate: @/drawer
+        templateOptions: #DEFAULT#
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: argumentsMustHaveChecksum
+        formAutoComplete: false
+    }
+
+    region CONTENT (
+        name: Content
+        type: staticContent
+        layout {
+            sequence: 10
+            slot: BODY
+        }
+    )
+
+    region FOOTER (
+        name: Footer
+        type: staticContent
+        layout {
+            sequence: 20
+            slot: REGION_POSITION_03
+        }
+    )
+)
+```
+
+## Notes
+- Host create, edit, close, and next actions in a footer region or inline-drawer pattern anchored to `REGION_POSITION_03`.
+- Keep drawer headers or helper actions in `REGION_POSITION_01` when required.
+- Use drawer position and size template options instead of custom CSS classes.

package/skills/apexlang/templates/page-layout-templates/left-and-right-side-columns/README.md

@@ -0,0 +1,18 @@
+# Left And Right Side Columns Templates
+
+## Purpose
+Canonical guidance for the `@/left-and-right-side-columns` page layout family and its markdown entrypoints.
+
+## Usage
+- Load [`../_shared/page.common.md`](../_shared/page.common.md) first to align shared non-dialog variables and slot guidance.
+- Load `left-and-right-side-columns._common.md` next for the `@/left-and-right-side-columns` family contract.
+- Load `left-and-right-side-columns.basic.md` for a baseline example.
+
+## Template Catalog
+- `left-and-right-side-columns._common.md`
+- `left-and-right-side-columns.basic.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Preserve the markdown-only contract for page layout templates in this tree.
+- Keep slot and template-option guidance aligned with current Theme 42 metadata.

package/skills/apexlang/templates/page-layout-templates/left-and-right-side-columns/left-and-right-side-columns._common.md

@@ -0,0 +1,85 @@
+---
+templateId: page.left-and-right-side-columns
+component: page
+dslVersion: 1.0
+description: Standard Theme 42 page layout with both left and right side columns.
+---
+
+## Purpose
+Apply the shared non-dialog page contract to the Theme 42 `Left and Right Side Columns` page template. Use this layout when the page needs persistent content on both sides of the main body.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| base page vars | inherited | `page.common` | Load [`../_shared/page.common.md`](../_shared/page.common.md) first. |
+| appearance.pageTemplate | yes | string | Must be `@/left-and-right-side-columns`. |
+| appearance.templateOptions | optional | string or array | Usually `#DEFAULT#` or `sticky-header-on-mobile`; use the `static_id` values from the inventory in [`../README.md`](../README.md). |
+| layout slots | derived | slot set | Standard slots plus `REGION_POSITION_02` (`leftColumn`) and `REGION_POSITION_03` (`rightColumn`). |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageTemplate: @/left-and-right-side-columns
+        templateOptions: [appearance.templateOptions]
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region leftRail (
+        name: [leftRailName]
+        type: [leftRailType]
+        layout {
+            sequence: 10
+            slot: REGION_POSITION_02
+        }
+    )
+
+    region content (
+        name: [contentRegionName]
+        type: [contentRegionType]
+        layout {
+            sequence: 20
+            slot: BODY
+        }
+    )
+
+    region rightRail (
+        name: [rightRailName]
+        type: [rightRailType]
+        layout {
+            sequence: 30
+            slot: REGION_POSITION_03
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `REGION_POSITION_02` (`leftColumn`): Navigation, filters, or status summaries.
+- `REGION_POSITION_03` (`rightColumn`): Inspector panels, related actions, or contextual detail.
+- In the current Theme 42 implementation, both side rails are fixed-width columns of about `15rem` each. Treat that width as a build-pinned selection heuristic, not as a tunable page-grid split.
+- When one rail is intended to select or drive the main body content, prefer the left rail for that local navigation or chooser role and keep the opposite rail for supporting detail, actions, or inspection.
+- All standard-page slots remain available.
+
+## Conditional Rules
+- Keep the left and right rails focused on distinct concerns; avoid duplicating page actions across both.
+- If the left rail contains contextual sub-navigation for a local page cluster, keep that same sub-navigation menu on every page in that cluster rather than only on the entry page.
+- If one rail is optional in most scenarios, reassess whether a single-column template would be clearer.
+
+## Guardrails
+- Use this template only when both side rails are consistently meaningful across the page's primary use cases.
+- If either side needs to behave like a wider or adjustable sidebar, prefer a different page shell and explicit body-grid coordinates.
+- Keep the main body as the dominant content area; side rails should stay secondary.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/left_and_right_side_columns.sql`

package/skills/apexlang/templates/page-layout-templates/left-and-right-side-columns/left-and-right-side-columns._index.md

@@ -0,0 +1,18 @@
+---
+templateId: left-and-right-side-columns.index
+componentType: template
+dslVersion: 1.0
+imports:
+  - ../_shared/page.common.md
+  - left-and-right-side-columns._common.md
+description: Routing entrypoint for left-and-right-side-columns templates.
+---
+
+## Purpose
+Primary routing entrypoint for `left-and-right-side-columns` templates.
+
+## Load Order
+1. Load this file.
+2. Load `../_shared/page.common.md`.
+3. Load `left-and-right-side-columns._common.md`.
+4. Load `left-and-right-side-columns.basic.md` when a baseline example is needed.

package/skills/apexlang/templates/page-layout-templates/left-and-right-side-columns/left-and-right-side-columns.basic.md

@@ -0,0 +1,63 @@
+---
+templateId: page.left-and-right-side-columns.basic
+component: page
+dslVersion: 1.0
+imports:
+  - left-and-right-side-columns._common.md
+description: Baseline dual-rail page example with both left and right supporting columns.
+---
+
+## Purpose
+Provide a baseline `@/left-and-right-side-columns` page example for pages that need persistent rails on both sides of the main content.
+
+## Template
+```apexlang
+page 120 (
+    name: Operations Console
+    alias: OPERATIONS-CONSOLE
+    title: Operations Console
+    appearance {
+        pageTemplate: @/left-and-right-side-columns
+        templateOptions: #DEFAULT#
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: argumentsMustHaveChecksum
+        formAutoComplete: false
+    }
+
+    region LEFT_RAIL (
+        name: Left Rail
+        type: staticContent
+        layout {
+            sequence: 10
+            slot: REGION_POSITION_02
+        }
+    )
+
+    region CONTENT (
+        name: Content
+        type: staticContent
+        layout {
+            sequence: 20
+            slot: BODY
+        }
+    )
+
+    region RIGHT_RAIL (
+        name: Right Rail
+        type: staticContent
+        layout {
+            sequence: 30
+            slot: REGION_POSITION_03
+        }
+    )
+)
+```
+
+## Notes
+- Use the dual-rail layout only when both side areas are structurally important.
+- Prefer a simpler page template when one rail is optional or empty most of the time.

package/skills/apexlang/templates/page-layout-templates/left-side-column/README.md

@@ -0,0 +1,18 @@
+# Left Side Column Templates
+
+## Purpose
+Canonical guidance for the `@/left-side-column` page layout family and its markdown entrypoints.
+
+## Usage
+- Load [`../_shared/page.common.md`](../_shared/page.common.md) first to align shared non-dialog variables and slot guidance.
+- Load `left-side-column._common.md` next for the `@/left-side-column` family contract.
+- Load `left-side-column.basic.md` for a baseline example.
+
+## Template Catalog
+- `left-side-column._common.md`
+- `left-side-column.basic.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Preserve the markdown-only contract for page layout templates in this tree.
+- Keep slot and template-option guidance aligned with current Theme 42 metadata.

package/skills/apexlang/templates/page-layout-templates/left-side-column/left-side-column._common.md

@@ -0,0 +1,78 @@
+---
+templateId: page.left-side-column
+component: page
+dslVersion: 1.0
+description: Standard Theme 42 page layout with an additional left column slot.
+---
+
+## Purpose
+Apply the shared non-dialog page contract to the Theme 42 `Left Side Column` page template. Use this layout when navigation-adjacent or summary content belongs in a persistent left rail.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| base page vars | inherited | `page.common` | Load [`../_shared/page.common.md`](../_shared/page.common.md) first. |
+| appearance.pageTemplate | yes | string | Must be `@/left-side-column`. |
+| appearance.templateOptions | optional | string or array | Usually `#DEFAULT#` or `sticky-header-on-mobile`; use the `static_id` values from the inventory in [`../README.md`](../README.md). |
+| layout slots | derived | slot set | Standard slots plus `leftColumn`. |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageTemplate: @/left-side-column
+        templateOptions: [appearance.templateOptions]
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region sideContent (
+        name: [sideRegionName]
+        type: [sideRegionType]
+        layout {
+            sequence: 10
+            slot: leftColumn
+        }
+    )
+
+    region content (
+        name: [contentRegionName]
+        type: [contentRegionType]
+        layout {
+            sequence: 20
+            slot: body
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `leftColumn`: Side-rail filters, status panels, or contextual navigation.
+- In the current Theme 42 implementation, `leftColumn` is a fixed-width rail of about `15rem`. Treat that width as a build-pinned selection heuristic, not a tunable body-grid ratio.
+- Prefer this rail when the left-side content is meant to drive or select what appears in the main body, for example a contextual sub-navigation menu, section chooser, or parent selector whose current choice determines the main pane content.
+- All standard-page slots remain available.
+- For the standard faceted-search pattern, place the faceted-search region in `leftColumn` and keep the filtered results region in `body`.
+
+## Conditional Rules
+- Hide the left column region when the page has no contextual side content instead of moving that content into the main body.
+- When the rail contains contextual sub-navigation to sibling pages, keep that same sub-navigation menu on each page it links to so the local navigation context remains stable after navigation.
+- Keep actionable overlay launch regions in `REGION_POSITION_04`.
+
+## Guardrails
+- Use this template only when the left rail is part of the page contract. Otherwise prefer `@/standard`.
+- If the requirement needs a wider or tunable sidebar-main ratio such as `4/8` or `3/9`, prefer `@/standard` plus explicit body-grid coordinates instead of this fixed rail.
+- Do not treat contextual sub-navigation as a one-page-only decoration; when it defines a local page group, repeat it across that group's linked pages.
+- Do not place full-width bands in the left-column slot; use `REGION_POSITION_08` for breakout content.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/left_side_column.sql`
+- Internal template-source metadata (`page-left-side-column`)

package/skills/apexlang/templates/page-layout-templates/left-side-column/left-side-column._index.md

@@ -0,0 +1,18 @@
+---
+templateId: left-side-column.index
+componentType: template
+dslVersion: 1.0
+imports:
+  - ../_shared/page.common.md
+  - left-side-column._common.md
+description: Routing entrypoint for left-side-column templates.
+---
+
+## Purpose
+Primary routing entrypoint for `left-side-column` templates.
+
+## Load Order
+1. Load this file.
+2. Load `../_shared/page.common.md`.
+3. Load `left-side-column._common.md`.
+4. Load `left-side-column.basic.md` when a baseline example is needed.

package/skills/apexlang/templates/page-layout-templates/left-side-column/left-side-column.basic.md

@@ -0,0 +1,54 @@
+---
+templateId: page.left-side-column.basic
+component: page
+dslVersion: 1.0
+imports:
+  - left-side-column._common.md
+description: Baseline left-side-column page example with a persistent side rail.
+---
+
+## Purpose
+Provide a baseline `@/left-side-column` page example for pages that need a persistent left rail.
+
+## Template
+```apexlang
+page 110 (
+    name: Worklist
+    alias: WORKLIST
+    title: Worklist
+    appearance {
+        pageTemplate: @/left-side-column
+        templateOptions: #DEFAULT#
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: argumentsMustHaveChecksum
+        formAutoComplete: false
+    }
+
+    region SIDE_RAIL (
+        name: Side Rail
+        type: staticContent
+        layout {
+            sequence: 10
+            slot: leftColumn
+        }
+    )
+
+    region CONTENT (
+        name: Content
+        type: staticContent
+        layout {
+            sequence: 20
+            slot: body
+        }
+    )
+)
+```
+
+## Notes
+- Keep the left rail focused on contextual navigation, filters, or status.
+- Use `@/standard` instead when the side rail is optional or mostly empty.

package/skills/apexlang/templates/page-layout-templates/login/README.md

@@ -0,0 +1,18 @@
+# Login Templates
+
+## Purpose
+Canonical guidance for the `@/login` page layout family and its markdown entrypoints.
+
+## Usage
+- Load [`../_shared/page.common.md`](../_shared/page.common.md) first for shared non-dialog context, then load `login._common.md` for the login-specific contract.
+- Load `login.basic.md` for a baseline example.
+- Keep login-only authentication and slot guidance in this family rather than reusing `@/login` for authenticated pages.
+
+## Template Catalog
+- `login._common.md`
+- `login.basic.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Preserve the markdown-only contract for page layout templates in this tree.
+- Keep slot and template-option guidance aligned with current Theme 42 metadata.

package/skills/apexlang/templates/page-layout-templates/login/login._common.md

@@ -0,0 +1,71 @@
+---
+templateId: page.login
+component: page
+dslVersion: 1.0
+description: Public-facing login page layout with dedicated header, footer, and background slots.
+---
+
+## Purpose
+Apply the shared non-dialog page contract to the Theme 42 `Login` page template. Use this layout for authentication entry points and other public pages that need login-style chrome.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| pageNumber | yes | number | Page identifier; current examples commonly use a dedicated login page such as `9999`. |
+| name | yes | string | Page name. |
+| alias | yes | string | Page alias, often `LOGIN`. |
+| title | optional | string | Browser and page title. |
+| appearance.pageTemplate | yes | string | Must be `@/login`. |
+| appearance.templateOptions | optional | string or array | Usually `#DEFAULT#`, `background-1`, `background-2`, `background-3`, or `split`; use the `static_id` values from the inventory in [`../README.md`](../README.md). |
+| security.authentication | usually yes | enum | Commonly `public` for login entry pages. |
+| layout slots | derived | slot set | `BACKGROUND_IMAGE` (`backgroundImage`), `BODY` (`contentBody`), `REGION_POSITION_01` (`bodyHeader`), `REGION_POSITION_02` (`bodyFooter`), `AFTER_HEADER` (`afterHeader`), `BEFORE_FOOTER` (`beforeFooter`). |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageTemplate: @/login
+        templateOptions: [appearance.templateOptions]
+    }
+    navigation {
+        warnOnUnsavedChanges: false
+    }
+    security {
+        authentication: public
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region loginContent (
+        name: [loginRegionName]
+        type: [loginRegionType]
+        layout {
+            sequence: 10
+            slot: contentBody
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `BODY` / `contentBody`: Main login content such as the login region or explanatory content.
+- `REGION_POSITION_01` / `bodyHeader`: Header content above the main login body.
+- `REGION_POSITION_02` / `bodyFooter`: Footer content below the main login body.
+- `AFTER_HEADER` / `afterHeader`: Supplemental content immediately below the page header.
+- `BEFORE_FOOTER` / `beforeFooter`: Supplemental content immediately above the page footer.
+- `BACKGROUND_IMAGE` / `backgroundImage`: Background artwork or media region.
+
+## Conditional Rules
+- Keep the page public if it is the application login entry point.
+- Use conditions on supplemental header or footer regions when the page supports multiple auth scenarios.
+
+## Guardrails
+- Do not reuse this template for authenticated application pages just to get the visual treatment.
+- Keep background-image usage accessible and non-essential to the task flow.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/login.sql`
+- Internal template-source metadata (`page-login`)

package/skills/apexlang/templates/page-layout-templates/login/login._index.md

@@ -0,0 +1,18 @@
+---
+templateId: login.index
+componentType: template
+dslVersion: 1.0
+imports:
+  - ../_shared/page.common.md
+  - login._common.md
+description: Routing entrypoint for login templates.
+---
+
+## Purpose
+Primary routing entrypoint for `login` templates.
+
+## Load Order
+1. Load this file.
+2. Load `../_shared/page.common.md`.
+3. Load `login._common.md`.
+4. Load `login.basic.md` when a baseline example is needed.

package/skills/apexlang/templates/page-layout-templates/login/login.basic.md

@@ -0,0 +1,45 @@
+---
+templateId: page.login.basic
+component: page
+dslVersion: 1.0
+imports:
+  - login._common.md
+description: Baseline login page example with public authentication and a single login region.
+---
+
+## Purpose
+Provide a baseline `@/login` example for the public application entry page.
+
+## Template
+```apexlang
+page 9999 (
+    name: Login
+    alias: LOGIN
+    title: Login
+    appearance {
+        pageTemplate: @/login
+        templateOptions: #DEFAULT#
+    }
+    navigation {
+        warnOnUnsavedChanges: false
+    }
+    security {
+        authentication: public
+        pageAccessProtection: argumentsMustHaveChecksum
+        formAutoComplete: false
+    }
+
+    region LOGIN_CONTENT (
+        name: Login Content
+        type: staticContent
+        layout {
+            sequence: 10
+            slot: contentBody
+        }
+    )
+)
+```
+
+## Notes
+- Add header, footer, or background-image regions only when they support the authentication experience.
+- Do not reuse this family for authenticated application pages.

package/skills/apexlang/templates/page-layout-templates/marquee/README.md

@@ -0,0 +1,18 @@
+# Marquee Templates
+
+## Purpose
+Canonical guidance for the `@/marquee` page layout family and its markdown entrypoints.
+
+## Usage
+- Load [`../_shared/page.common.md`](../_shared/page.common.md) first to align shared non-dialog variables and slot guidance.
+- Load `marquee._common.md` next for the `@/marquee` family contract.
+- Load `marquee.basic.md` for a baseline example.
+
+## Template Catalog
+- `marquee._common.md`
+- `marquee.basic.md`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Preserve the markdown-only contract for page layout templates in this tree.
+- Keep slot and template-option guidance aligned with current Theme 42 metadata.

package/skills/apexlang/templates/page-layout-templates/marquee/marquee._common.md

@@ -0,0 +1,74 @@
+---
+templateId: page.marquee
+component: page
+dslVersion: 1.0
+description: Theme 42 marquee page layout with hero, master-detail, and right-column display points.
+---
+
+## Purpose
+Apply the shared non-dialog page contract to the Theme 42 `Marquee` page template. Use this layout for landing, dashboard, and master-detail pages that need a strong top section plus supporting side content.
+
+## Variables
+| Name | Required | Type | Description |
+|------|----------|------|-------------|
+| base page vars | inherited | `page.common` | Load [`../_shared/page.common.md`](../_shared/page.common.md) first. |
+| appearance.pageTemplate | yes | string | Must be `@/marquee`. |
+| appearance.templateOptions | optional | string or array | Usually `#DEFAULT#` or `sticky-header-on-mobile`; use the `static_id` values from the inventory in [`../README.md`](../README.md). |
+| layout slots | derived | slot set | Standard-slot family plus `REGION_POSITION_02` (`masterDetail`) and `REGION_POSITION_03` (`rightSideColumn`). |
+
+## Template
+```apexlang
+page [pageNumber] (
+    name: [name]
+    alias: [alias]
+    title: [title]
+    appearance {
+        pageTemplate: @/marquee
+        templateOptions: [appearance.templateOptions]
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        authorizationScheme: mustNotBePublicUser
+        pageAccessProtection: [security.pageAccessProtection]
+        formAutoComplete: false
+    }
+
+    region hero (
+        name: [heroRegionName]
+        type: [heroRegionType]
+        layout {
+            sequence: 10
+            slot: REGION_POSITION_07
+        }
+    )
+
+    region content (
+        name: [contentRegionName]
+        type: [contentRegionType]
+        layout {
+            sequence: 20
+            slot: BODY
+        }
+    )
+)
+```
+
+## Slot Guidance
+- `REGION_POSITION_07` (`banner`): Top marquee or hero content.
+- `REGION_POSITION_02` (`masterDetail`): Master-detail or highlight content block.
+- `REGION_POSITION_03` (`rightSideColumn`): Secondary supporting content.
+- `BODY`: Main page content.
+- Standard slots such as `REGION_POSITION_01`, `REGION_POSITION_04`, `REGION_POSITION_05`, `REGION_POSITION_06`, and `REGION_POSITION_08` remain available.
+
+## Conditional Rules
+- Keep marquee and master-detail content distinct so the hero area does not become a second main body.
+- Put dialogs and drawers in `REGION_POSITION_04` even when the page already uses both side slots.
+
+## Guardrails
+- Use this template when the hero and supporting rails are intentional parts of the information architecture.
+- Avoid filling every available slot by default; a marquee page should still preserve visual hierarchy.
+
+## Source Anchors
+- `core/themes/theme_42/f8842.261/application/shared_components/user_interface/templates/page/marquee.sql`

package/skills/apexlang/templates/page-layout-templates/marquee/marquee._index.md

@@ -0,0 +1,18 @@
+---
+templateId: marquee.index
+componentType: template
+dslVersion: 1.0
+imports:
+  - ../_shared/page.common.md
+  - marquee._common.md
+description: Routing entrypoint for marquee templates.
+---
+
+## Purpose
+Primary routing entrypoint for `marquee` templates.
+
+## Load Order
+1. Load this file.
+2. Load `../_shared/page.common.md`.
+3. Load `marquee._common.md`.
+4. Load `marquee.basic.md` when a baseline example is needed.