pi-apexlang 0.1.0

package/skills/apexlang/templates/base-app-structure/README.md

@@ -0,0 +1,121 @@
+# Base App Structure Templates
+
+## Purpose
+Canonical guidance for the `base-app-structure` whole-application family. The
+root of this folder is the documentation and metadata contract for a brand new
+application scaffold. The executable scaffold payload lives under
+`scaffold-example/`. This family is not a literal whole-directory copy-paste
+starter. The checked-in baseline uses the canonical `26.1.0+3102` APEXlang
+vocabulary and must remain the only supported whole-app scaffold contract in
+this repo.
+
+## Usage
+- Use `base-app-structure._index.md` as the routing entrypoint for
+  whole-application scaffolding.
+- Load `base-app-structure._common.md` immediately after to align generation
+  rules, required inputs, and baseline artifact guarantees.
+- Use `base-app-structure.registry.json` when tooling needs a machine-readable
+  catalog for this family.
+- Materialize only the named runtime artifacts from `scaffold-example/` into
+  `applications/app_###/`, then customize only the identifiers and attributes
+  backed by the user request, requested structure, or selected template
+  family.
+- Treat `scaffold-example/deployments/default.json` as a required runtime seed,
+  not a reusable literal. Before generating a brand new app, resolve or ask for
+  the destination APEX workspace name, record it in session
+  `context-resolution.json` under `db_context.workspace`, and replace
+  `deployments/default.json.workspace.name` with that exact value during
+  materialization.
+- Allowed top-level publish targets in the generated app are `.apex/`,
+  `application.apx`, `deployments/`, `page-groups.apx`, `pages/`,
+  `shared-components/`, and `supporting-objects/`.
+- Keep `base-app-runtime-seed.manifest.json` at the `base-app-structure/`
+  root. It is runtime seed metadata, not an executable scaffold payload.
+- Keep the root Markdown/JSON files in `base-app-structure/` as template-space
+  docs and metadata only. Do not publish them into generated app roots.
+- Keep `scaffold-example/` as the executable scaffold source in template
+  space only. Do not publish the `scaffold-example/` directory itself into
+  generated app roots.
+- Preserve the canonical baseline vocabulary when provisioning or updating the
+  scaffold:
+  - `application.apx`: `navigation`, `navigationMenu`, `navigationBar`
+  - `shared-components/themes/**/theme.apx`: `themeNumber`, `javaScript`,
+    `navigationBarList`, `navigationMenuListPosition`,
+    `navigationMenuListTop`, `navigationMenuListSide`
+  - `shared-components/breadcrumbs.apx`: `pageNumber`
+- Do not copy optional placeholder values or documentation-only examples such
+  as sample header/footer text, `CUSTOM_FILE_NAME.css`, inline sample JS, or
+  explanatory region copy unless the user explicitly asks for them. Help text
+  and maintainability comments are default generation concerns and should be
+  supplied through real message keys, documented sources, or provisional
+  translation-ready copy rather than omitted by default.
+- Preserve canonical path references and markdown-first conventions when
+  updating workflow or registry links.
+
+## Application Root Coverage
+- `base-app-structure/` is the canonical owner for the `app (...)` root
+  contract in this repo.
+- Application-root guidance belongs here when it describes:
+  - nested root blocks proven by `application.apx`
+  - flat app-wide defaults such as compatibility, runtime availability,
+    notifications, and deployment-sensitive paths
+  - inheritance pivots such as `globalPage`, theme selection, and the current
+    authentication scheme
+- Reusable shared-component families such as `authentications/`,
+  `authorizations/`, `lists/`, and `lovs/` still own their own component
+  definitions. This family owns only the app-root selection and inheritance
+  side of those relationships.
+
+## Source Priority For Application Definition Guidance
+- `scaffold-example/application.apx` is the concrete minimal app-root scaffold
+  and the executable source of truth for the base app skeleton.
+- `base-app-structure._common.md` is the canonical markdown owner for
+  app-root naming rules, ownership boundaries, and metadata-backed defaults.
+- Shared-component families provide secondary guidance only when the
+  application root references one of their assets, for example the current
+  authentication scheme or navigation lists.
+
+## Safe Baseline vs Reference-Only Guidance
+| Category | Default behavior |
+|----------|------------------|
+| Required runtime app/page/shared-component artifacts | Materialize into the new app output. |
+| App identity and aliases | Replace with run-specific values. |
+| Deployment workspace name | Resolve or ask for the destination workspace name, record it in session context, and replace `deployments/default.json.workspace.name` during materialization. |
+| Optional CSS includes | Omit unless a real app static file exists and the run selects it. |
+| Optional JS blocks | Omit unless the requirements call for page-level JS. |
+| Header/footer text | Omit unless the user or source requirements provide content. |
+| Help text and maintainability comments | Include by default for primary pages and key components using Text Messages, documented sources, or provisional translation-ready copy with a message-key plan. |
+| Inline error text | Omit unless the user or source requirements provide content. |
+| Example prose inside static regions | Do not copy into generated output. Use explicit page templates when real content is required. |
+
+## Template Catalog
+- `base-app-structure._index.md`
+- `base-app-structure._common.md`
+- `base-app-runtime-seed.manifest.json`
+- `base-app-structure.registry.json`
+- `scaffold-example/`
+  - `.apex/apexlang.json`
+  - `application.apx`
+  - `deployments/default.json`
+  - `page-groups.apx`
+  - `pages/`
+  - `p00000-global-page.apx`
+  - `p00001-home.apx`
+  - `p09999-login.apx`
+  - `shared-components/`
+  - `supporting-objects/`
+
+## Maintenance
+- Keep this README synchronized with actual files in the directory.
+- Update catalogs and usage notes whenever templates are added, removed, or
+  renamed.
+- Retain deterministic guarantees for the runtime artifact set under
+  `scaffold-example/`: `.apex/apexlang.json`, `application.apx`,
+  `deployments/default.json`, `page-groups.apx`, the three baseline page
+  seeds, `shared-components/**`, and `supporting-objects/**`.
+- Do not reintroduce legacy scaffold aliases such as `nav`, `navMenu`,
+  `navBar`, `themeNo`, `js`, or `pageNo`.
+- Treat any example content added for documentation purposes as reference-only
+  and call that out explicitly in the family docs.
+- Keep app-root documentation consolidated here rather than creating parallel
+  application-definition folders under `shared-components/`.

package/skills/apexlang/templates/base-app-structure/base-app-runtime-seed.manifest.json

@@ -0,0 +1,43 @@
+{
+  "version": 1,
+  "seed_type": "apexlang-base-app-runtime-seed",
+  "description": "Exact runtime files that may be materialized into a brand new application from the base-app-structure template family.",
+  "source_root": "scaffold-example",
+  "top_level_allowlist": [
+    ".apex",
+    "application.apx",
+    "deployments",
+    "page-groups.apx",
+    "pages",
+    "shared-components",
+    "supporting-objects"
+  ],
+  "materialize_entries": [
+    ".apex/apexlang.json",
+    "application.apx",
+    "deployments/default.json",
+    "page-groups.apx",
+    "pages/p00000-global-page.apx",
+    "pages/p00001-home.apx",
+    "pages/p09999-login.apx",
+    "shared-components/authentications.apx",
+    "shared-components/authorizations.apx",
+    "shared-components/breadcrumbs.apx",
+    "shared-components/build-options.apx",
+    "shared-components/component-settings.apx",
+    "shared-components/lists.apx",
+    "shared-components/lovs.apx",
+    "shared-components/static-files.apx",
+    "shared-components/static-files/icons/app-icon-144-rounded.png",
+    "shared-components/static-files/icons/app-icon-192.png",
+    "shared-components/static-files/icons/app-icon-256-rounded.png",
+    "shared-components/static-files/icons/app-icon-32.png",
+    "shared-components/static-files/icons/app-icon-512.png",
+    "shared-components/themes/universal-theme/theme.apx",
+    "supporting-objects/deinstall-script.sql",
+    "supporting-objects/supporting-objects.apx"
+  ],
+  "forbidden_root_entries": [
+    "scaffold-example"
+  ]
+}

package/skills/apexlang/templates/base-app-structure/base-app-structure._common.md

@@ -0,0 +1,267 @@
+---
+templateId: base-app-structure.common
+componentType: template
+version: 1.0
+imports:
+  - references/policies/memory-bank/10-global/apex.global.md
+description: Canonical contract for whole-application base app structure runtime-artifact seeding.
+---
+
+# Purpose
+
+Define the deterministic runtime-artifact contract for whole-application runs
+that use `base-app-structure/` documentation plus the
+`base-app-structure/scaffold-example/` executable scaffold source for the
+minimum required app, page, and shared-component files before page or
+shared-component customization begins. This family is the canonical
+`26.1.0+3102` scaffold and must emit only the current vocabulary contract.
+
+---
+
+# Generation Rules (MANDATORY)
+
+1. Load `references/policies/memory-bank/10-global/apex.global.md` and this `_common` file before
+   materializing or validating whole-application output.
+2. Materialize only the named runtime artifacts from
+   `templates/base-app-structure/scaffold-example/` into
+   the resolved `applications/app_###/` target before Agent 1 drafts new pages
+   or shared components.
+3. Whole-directory copy from `base-app-structure/` into the app root is
+   forbidden.
+4. Keep `base-app-runtime-seed.manifest.json` at the `base-app-structure/`
+   root. It is runtime seed metadata and must not be moved into
+   `scaffold-example/`.
+5. Keep the root Markdown and JSON files in `base-app-structure/` as
+   template-space docs and metadata only.
+6. Keep `scaffold-example/` as the executable scaffold source in template
+   space only; do not publish the `scaffold-example/` directory itself into the
+   generated app root.
+7. Copy only baseline-required metadata from this family. Optional attributes
+   and example text remain omitted unless the user request, requested structure, or
+   selected component template explicitly requires them.
+8. Preserve the baseline artifact layout unless the user explicitly requests a
+   deviation. Customization happens after baseline provisioning, not by
+   re-synthesizing the skeleton from memory.
+9. Before baseline provisioning of a brand new app, resolve or ask for the
+   destination APEX workspace name and record it in session
+   `context-resolution.json` under `db_context.workspace`. Stop with
+   `Missing Inputs` rather than guessing or reusing a placeholder.
+10. Replace `deployments/default.json.workspace.name` with the exact
+    selected destination APEX workspace name during materialization.
+11. Keep the generated `.apex/apexlang.json`, `application.apx`,
+   `deployments/default.json`, `page-groups.apx`, baseline page seeds,
+   `shared-components/**`, and `supporting-objects/**` output contract
+   synchronized with this family when governance or orchestration docs refer
+   to the whole-app scaffold.
+12. Treat the Markdown and JSON files at `base-app-structure/` root as
+   canonical for routing, guardrails, and materialization metadata.
+13. Treat the runtime scaffold payload under
+   `base-app-structure/scaffold-example/` as the executable skeleton source.
+14. Preserve the canonical scaffold vocabulary in all baseline output files:
+   - `application.apx`: `navigation`, `navigationMenu`, `navigationBar`
+   - `shared-components/themes/**/theme.apx`: `themeNumber`, `javaScript`,
+     `navigationBarList`, `navigationMenuListPosition`,
+     `navigationMenuListTop`, `navigationMenuListSide`
+   - `shared-components/breadcrumbs.apx`: `pageNumber`
+
+---
+
+# Required Inputs
+
+- Resolved application output root (`applications/app_###/`)
+- Destination APEX workspace name in session context for `deployments/default.json.workspace.name`
+- Application identity values to update after baseline provisioning (for example
+  app name,
+  alias, parsing schema, substitutions)
+- Explicit user direction if any baseline page or shared component seed should
+  be omitted or renamed
+- Explicit user direction if optional JS, header/footer text, additional copy,
+  or other non-baseline attributes should be emitted
+- A Text Message plan, documented source, or provisional copy plan for default
+  help text and maintainability comments
+
+---
+
+# Seed Artifact Contract
+
+| Path | Required | Notes |
+|------|----------|-------|
+| `scaffold-example/application.apx` | yes | Executable base application descriptor; customize identifiers after baseline provisioning. |
+| `scaffold-example/.apex/apexlang.json` | yes | Runtime metadata file for the generated app root. |
+| `scaffold-example/deployments/default.json` | yes | Deployment metadata for the generated app root. Replace `workspace.name` with the selected destination workspace name during materialization. |
+| `scaffold-example/page-groups.apx` | yes | Runtime page-group definition file. |
+| `scaffold-example/pages/p00000-global-page.apx` | yes | Global Page seed for Page 0. |
+| `scaffold-example/pages/p00001-home.apx` | yes | Home Page seed for Page 1 with only safe default metadata. |
+| `scaffold-example/pages/p09999-login.apx` | yes | Login Page seed for Page 9999 with only required login metadata. |
+| `scaffold-example/shared-components/**` | yes | Baseline shared components, theme assets, and static files. |
+| `scaffold-example/supporting-objects/**` | yes | Runtime supporting-object descriptors and scripts. |
+
+---
+
+# Application Root Contract
+
+## Proven Root Structure
+
+| Surface | Current doc form | Evidence | Notes |
+|---------|------------------|----------|-------|
+| `app [alias] (...)` | canonical root block | checked-in scaffold | The executable baseline already uses `app`, not `application`. |
+| `name` | top-level scalar | checked-in scaffold | Minimal human-facing app name. |
+| `globalization { ... }` | nested block | checked-in scaffold + metadata | Language-selection concerns and translation strategy. |
+| `logo { ... }` | nested block | metadata-backed app-root contract | Mode-dependent branding block. |
+| `navigation { ... }` | nested block | checked-in scaffold + metadata | Structured app-level home/login links. |
+| `navigationMenu { ... }` | nested block | checked-in scaffold + metadata | App-level navigation-list configuration. |
+| `navigationBar { ... }` | nested block | checked-in scaffold + metadata | App-level navigation-bar configuration. |
+| `authentication { ... }` | nested block | checked-in scaffold + metadata | App-root selection of the default authentication scheme. |
+| flat runtime / availability / error settings | top-level scalars | metadata-backed guidance | Remain flat until a checked-in app-root example proves alternate nesting. |
+
+## Naming Rules For Application-Root Guidance
+
+- Prefer the token already proven by the checked-in scaffold, for example
+  `navigationMenu`.
+- Prefer explicit metadata-backed APEXlang names when the source metadata
+  defines them, for example `usersCanChooseThemeStyle`, `runOnly`, or
+  `runAndBuild`.
+- When no checked-in executable example exists, document app-root surfaces
+  using the current lower-camel property form and treat them as metadata-backed
+  guidance rather than executable proof.
+
+## Domain Guidance
+
+### Globalization and formats
+- `globalization.primaryLanguage` is the authoring language of the app.
+- `globalization.languageDerivedFrom` is metadata-backed and should be treated
+  as an explicit app-root behavior choice rather than an inferred runtime
+  detail.
+- For translation-ready app scaffolds and localization workflow examples, the
+  default `globalization.languageDerivedFrom` should be `browserPreference`
+  unless the user explicitly requests a different runtime derivation mode.
+- Only use the following values for `globalization.languageDerivedFrom`:
+  - `appPreference`
+  - `appPrimaryLanguage`
+  - `browserPreference`
+  - `itemPreference`
+  - `notTranslated`
+  - `sessiond`
+- `globalization.translationMethod` stays at app root because it controls how
+  the whole application resolves translation ownership.
+- App-wide masks such as `appDateFormat`, `appDateTimeFormat`,
+  `appTimestampFormat`, and `appTimestampTzFormat` remain flat root settings.
+- Browser-driven choices such as automatic time zone or CSV encoding should be
+  documented as runtime behavior, not just presentation preferences.
+
+### Branding and chrome
+- `logo { ... }` is the semantic app-root branding surface even when the
+  underlying metadata is still represented as several scalar properties.
+- Treat `logo.text`, `logo.imageUrl`, and `logo.customHtml` as mode-dependent
+  children of that app-root concern.
+- `addBuiltWithLove` and similar footer/chrome toggles are app-wide behavior,
+  not page content.
+- Raw favicon HTML remains an advanced escape hatch. Prefer declarative app
+  files and template-backed branding where possible.
+
+### Navigation
+- `navigation { ... }` owns structured home/login links at app root.
+- `navigationMenu` and `navigationBar` are separate app-root surfaces and
+  should not be collapsed into one generic navigation setting.
+- The app root chooses which shared lists and list templates drive the menu and
+  navigation bar. The shared-component families own the list definitions
+  themselves.
+- Theme support still gates some app-root navigation behavior, so treat theme
+  references and nav references as linked concerns.
+
+### User interface and inheritance
+- Theme, theme style, and global page selection are app-root inheritance pivots.
+- `globalPage` is an inheritance boundary, not a cosmetic convenience.
+- `usersCanChooseThemeStyle` is an app-root behavior switch and should stay
+  distinct from the theme-style definition itself.
+- App-wide success-message behavior belongs here only when it applies across
+  the whole app.
+
+### Authentication boundary
+- The application root chooses the current authentication scheme.
+- Use `authentication.scheme` for the app-root scheme selection. SQLcl 26.1
+  accepts this live-compatible spelling even though the bundled compiler
+  metadata still reports the legacy `authenticationScheme` property name.
+- The shared `AUTHENTICATION` component definition owns plugin type,
+  plugin attributes, remote-server settings, and scheme-specific processing.
+- App-level defaults such as deep linking, rejoin sessions, authorization
+  posture, and session-state protection remain app-root settings rather than
+  nested authentication-plugin configuration.
+
+### Runtime, availability, and notifications
+- `compatibilityMode`, `buildStatus`, and `appAvailability` are behavioral
+  contracts and should remain visible as app-root defaults.
+- Deployment-sensitive settings such as logging, debugging, proxy paths, and
+  file-prefix paths belong in app-root guidance because they affect import and
+  runtime behavior outside page-level authoring.
+- Error display defaults, global notification messaging, and app-wide error
+  handlers remain app-root concerns until a more specific checked-in executable
+  contract proves otherwise.
+
+## Compact Metadata Inventory
+
+| Area | DSL surface | Notes |
+|------|-------------|-------|
+| Globalization | `globalization.*`, `automaticTimeZone`, `automaticCsvEncoding`, app-wide format masks | Mix of proven nested block plus flat metadata-backed runtime defaults. |
+| Branding | `logo.*`, `addBuiltWithLove`, favicon escape hatch | App-root chrome and branding, with template placeholder dependencies such as `#LOGO#`. |
+| Navigation | `navigation.*`, `navigationMenu.*`, `navigationBar.*` | App root selects shared navigation assets and structured link targets. |
+| User interface | current theme/style, user style choice, `globalPage`, success-message behavior | Inheritance pivots tied to the whole application. |
+| Authentication | `authentication { ... }` plus adjacent security/session defaults | App root selects the scheme; shared components own scheme details. |
+| Runtime and availability | compatibility, build status, availability, logging, debugging, proxy/files paths | Metadata-backed flat app-root defaults with deployment/runtime impact. |
+| Errors and notifications | default error display, global notifications, app-wide handler hook | App-wide presentation and error-routing defaults. |
+
+---
+
+# Conditional Rendering Rules
+
+- Use this family only for whole-application runs. Page-only, region-only, and
+  shared-component-only runs should load their own template families instead of
+  treating this family as a universal copy source.
+- If the user explicitly opts out of part of the skeleton, preserve the rest of
+  the seed and record the requested deviation in the change log or critique.
+- If baseline page filenames are refined after baseline provisioning, preserve
+  the page numbers (`p00000-*`, `p00001-*`, `p09999-*`) and keep the
+  corresponding artifacts present unless the user explicitly directs otherwise.
+
+---
+
+# Guardrails
+
+- Do not synthesize seed files from memory or from generated application output.
+- Do not literal-copy documentation placeholders or example-only attributes
+  into generated output. This includes values such as `CUSTOM_FILE_NAME.css`,
+  sample header/footer text, sample help text, sample comments, and sample
+  static-region prose.
+- Do not treat help text or maintainability comments as opt-in extras for new
+  app scaffolds. Supply them by default using Text Messages, documented
+  sources, or provisional translation-ready copy with an explicit message-key
+  plan.
+- Do not replace this family with legacy alias paths or stale page filenames
+  such as `p00001.apx` or `p09999.apx` when documenting the
+  checked-in seed artifacts.
+- Do not emit or preserve legacy scaffold vocabulary such as `nav`, `navMenu`,
+  `navBar`, `themeNo`, `js`, or `pageNo`.
+- Keep references markdown-first: use `_index.md` and `_common.md` for routing,
+  then materialize the actual generated app artifacts and `shared-components/**` assets.
+- For baseline pages, prefer markdown sidecars for optional-section
+  documentation and keep the Markdown baseline examples minimal.
+- Apply identifier and optional copy/layout customization only after baseline
+  provisioning completes.
+- Keep app-root guidance consolidated in this family rather than creating a
+  second application-definition doc family under `shared-components/`.
+- Treat checked-in scaffold syntax as the strongest executable evidence and
+  metadata-backed notes as secondary guidance for flat app-root defaults.
+- Keep shared-component ownership boundaries explicit: app root selects shared
+  assets, while shared-component families own the referenced component
+  definitions.
+
+---
+
+# Related Assets
+
+- Family README: `templates/base-app-structure/README.md`
+- Routing entrypoint: `templates/base-app-structure/base-app-structure._index.md`
+- Seed manifest: `templates/base-app-structure/base-app-runtime-seed.manifest.json`
+- Scaffold source root: `templates/base-app-structure/scaffold-example/`
+- Global preferences: `references/policies/memory-bank/10-global/apex.global.md`
+- Whole-app orchestration: `SKILL.md` (loads `references/workflows/apex-generation.md` for constitutional generation flow)

package/skills/apexlang/templates/base-app-structure/base-app-structure._index.md

@@ -0,0 +1,26 @@
+---
+templateId: base-app-structure.index
+componentType: template
+version: 1.0
+imports:
+  - base-app-structure._common.md
+description: Routing entrypoint for whole-application base app structure templates.
+---
+
+# Purpose
+
+Primary routing entrypoint for `base-app-structure` templates.
+
+# Load Order
+
+1. Load this file.
+2. Load `base-app-structure._common.md`.
+3. Resolve or ask for the destination APEX workspace name, record it in session
+   `context-resolution.json` under `db_context.workspace`, and use it for
+   `deployments/default.json`.
+4. Materialize the required baseline artifacts from `scaffold-example/` into
+   the resolved `applications/app_###/` target.
+5. Customize identifiers and other run-specific attributes only when they are
+   required by the user request, requested structure, or selected template family.
+6. Treat optional example content in this family as reference-only unless the
+   run explicitly asks for it.

package/skills/apexlang/templates/base-app-structure/base-app-structure.registry.json

@@ -0,0 +1,39 @@
+{
+  "version": 1,
+  "entries": [
+    {
+      "slug": "root-readme",
+      "file": "README.md"
+    },
+    {
+      "slug": "root-contract",
+      "index": "base-app-structure._index.md",
+      "common": "base-app-structure._common.md",
+      "manifest": "base-app-runtime-seed.manifest.json",
+      "executable_root": "scaffold-example/"
+    },
+    {
+      "slug": "pages",
+      "path": "scaffold-example/pages/",
+      "files": [
+        "scaffold-example/pages/p00000-global-page.apx",
+        "scaffold-example/pages/p00001-home.apx",
+        "scaffold-example/pages/p09999-login.apx"
+      ]
+    },
+    {
+      "slug": "shared-components",
+      "path": "scaffold-example/shared-components/",
+      "files": [
+        "scaffold-example/shared-components/authentications.apx",
+        "scaffold-example/shared-components/authorizations.apx",
+        "scaffold-example/shared-components/breadcrumbs.apx",
+        "scaffold-example/shared-components/build-options.apx",
+        "scaffold-example/shared-components/component-settings.apx",
+        "scaffold-example/shared-components/lists.apx",
+        "scaffold-example/shared-components/lovs.apx",
+        "scaffold-example/shared-components/static-files.apx"
+      ]
+    }
+  ]
+}

package/skills/apexlang/templates/base-app-structure/scaffold-example/.apex/apexlang.json

@@ -0,0 +1,3 @@
+{
+  "mmdVersion" : "26.1.0+3102"
+}

package/skills/apexlang/templates/base-app-structure/scaffold-example/application.apx

@@ -0,0 +1,57 @@
+app TEST-APP (
+    name: Test App
+    logo {
+        type: text
+        text: &APP_TITLE.
+    }
+    navigation {
+        homeUrl: {
+            page: 1
+        }
+        loginUrl: {
+            page: LOGIN
+        }
+    }
+    navigationMenu {
+        listTemplate: @/side-navigation-menu
+        templateOptions: [
+            #DEFAULT#
+            js-defaultCollapsed
+            js-navCollapsed--hidden
+            t-TreeNav--styleA
+        ]
+        list: @navigation-menu
+    }
+    navigationBar {
+        list: @navigation-bar
+        listTemplate: @/navigation-bar
+        templateOptions: #DEFAULT#
+    }
+    userInterface {
+        currentTheme: @universal-theme
+        globalPage: 0
+        addBuiltWithApexToFooter: false
+    }
+    appFormatMasks {
+        date: DS
+        timestamp: DS
+        timestampTimeZone: DS
+    }
+    authentication {
+        scheme: @oracle-apex-accounts
+    }
+    authorization {
+        sourceForRoleOrGroupSchemes: authenticationScheme
+    }
+    sessionManagement {
+        maxSessionIdleTime: 3600
+        maxSessionLength: 28800
+    }
+    sessionStateProtection {
+        checksumSalt: BE8E26C19CF3511FBFEB1A6F9F79DA741A84B7ED70299369E025F6E56E2FFF65
+    }
+    runtime {
+        allowFeedback: true
+        compatibilityMode: 24.2
+    }
+)

package/skills/apexlang/templates/base-app-structure/scaffold-example/deployments/default.json

@@ -0,0 +1,5 @@
+{
+  "workspace": {
+    "name": "__REQUIRED_WORKSPACE_NAME__"
+  }
+}

package/skills/apexlang/templates/base-app-structure/scaffold-example/page-groups.apx

@@ -0,0 +1,4 @@
+pageGroup administration (
+    name: Administration
+)
+

package/skills/apexlang/templates/base-app-structure/scaffold-example/pages/p00000-global-page.apx

@@ -0,0 +1,4 @@
+page 0 (
+    name: Global Page
+)
+

package/skills/apexlang/templates/base-app-structure/scaffold-example/pages/p00001-home.apx

@@ -0,0 +1,35 @@
+page 1 (
+    name: Home
+    alias: HOME
+    title: Home
+    appearance {
+        pageTemplate: @/standard
+        templateOptions: #DEFAULT#
+    }
+    navigation {
+        cursorFocus: doNotFocusCursor
+    }
+    security {
+        pageAccessProtection: argumentsMustHaveChecksum
+        formAutoComplete: false
+    }
+
+    region app-name (
+        name: Home
+        title: &APP_TITLE.
+        type: staticContent
+        layout {
+            sequence: 10
+            slot: breadcrumbBar
+        }
+        appearance {
+            template: @/hero
+            templateOptions: #DEFAULT#
+        }
+        image {
+            fileUrl: #APP_FILES#icons/app-icon-512.png
+        }
+    )
+
+)
+