pi-apexlang 0.1.0

package/skills/apexlang/references/domains/shared-components/reusable-prompts/translations.md

@@ -0,0 +1,40 @@
+# Oracle APEX Translation Workflow Prompt
+
+Default prompt scaffold for plain-language translation requests
+- "Translate application `<App Alias or Name>`.
+  language: `<language name or code>`
+  scope: `<app | page | ask user>`
+  page: `<page number or alias when scope is page>`
+  auto_translate: true
+  update_globalization_block: true
+  log_path: `APEXLANG_OUTPUT_ROOT/logs/translations`
+  Note: Convert user-facing literals into shared text-message keys and replace component copy with substitution references. Do not inline translated literals into labels, titles, help text, confirmations, breadcrumbs, or static content."
+
+Canonical plain-language example
+- Input: `Translate my app to Spanish`
+- Output mode: `discovery`
+- Artifact: `shared-components/messages.apx`
+- Consumption: rewire translated page/component copy to `&APP_TEXT$...` substitutions
+
+Simple follow-up prompts
+- If scope is unclear, ask: "Do you want me to translate the whole app or just one page?"
+- If the user chooses one page, ask: "Which page do you want me to translate?"
+
+Explicit bundle scaffold
+- "Translate text messages for application `<App Alias or Name>`.
+  message_keys: [KEYS]
+  source_text: [BASE STRINGS]
+  languages: [fr, es, ...]
+  auto_translate: false
+  update_globalization_block: false
+  log_path: `APEXLANG_OUTPUT_ROOT/logs/translations`
+  Note: When target components are in scope, update them to substitutions rather than direct literals."
+
+Usage notes
+- Preserve placeholders, tokens, and markup exactly.
+- For plain requests like `translate my app` or `add another language to this app`, start in discovery mode that converts user-facing literals into text-message keys instead of translating component copy in place.
+- If the prompt explicitly asks for a page control such as a button/menu/selector, do not assume localization. Clarify whether the user wants runtime language switching or text-message localization.
+- Ask for keys or source text only when the user is doing an explicit bundle update.
+- Report Missing Inputs if the target language is missing or if explicit bundle inputs are incomplete.
+- Do not finalize localization runs with direct translated literals left in translated component attributes.
+- Do not generate helper source files for translation requests unless the user explicitly asked for tooling work.

package/skills/apexlang/references/domains/shared-components/templates.md

@@ -0,0 +1,58 @@
+# Template & Rule References — Shared Components
+
+## Purpose
+- Canonical bridge from the shared-components skill package to the actual template families under `templates/shared-components/`.
+- Use this file when the package has already been selected and the next step is deciding which shared-component family to load.
+
+## 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.logic.md`
+- `references/policies/memory-bank/20-data/apex.sql.md`
+- `references/policies/memory-bank/40-components/apex.items.md`
+- `assets/rules-mapping.json`
+
+## Canonical Template Sources
+- Catalog entrypoint: `templates/shared-components/README.md`
+- Machine-readable catalog: `templates/shared-components/shared-components.registry.json`
+- New-app shared-component seed source: `templates/base-app-structure/scaffold-example/shared-components/**`
+- The rest of `base-app-structure/` remains template input only. Do not publish template-family docs or registries into generated app roots.
+
+## Family Map
+- Navigation metadata:
+  - `templates/shared-components/lists/*.md`
+  - `templates/shared-components/breadcrumbs/*.md`
+- Shared LOV metadata:
+  - `templates/shared-components/lovs/*.md`
+  - Pair with `references/policies/memory-bank/40-components/apex.items.md` for LOV consumption rules.
+- Shared security metadata:
+  - `templates/shared-components/authorizations/*.md`
+  - `templates/shared-components/acl-roles/*.md`
+  - `templates/shared-components/authentications/*.md`
+- App-level configuration metadata:
+  - `templates/shared-components/app-processes/*.md`
+  - `templates/shared-components/app-computations.md`
+  - `templates/shared-components/app-items.md`
+  - `templates/shared-components/build-options.md`
+  - `templates/shared-components/component-settings/*.md`
+- Reusable communication and workflow assets:
+  - `templates/shared-components/translations/*.md`
+  - `templates/shared-components/email-templates/*.md`
+  - `templates/shared-components/task-definitions/*.md`
+- Integration and assistant assets:
+  - `templates/shared-components/rest-data-sources/*.md`
+  - `templates/shared-components/ai-agents/*.md`
+
+## Workflow Add-ons
+- `references/domains/universal-attr-config/workflow-page-sequencing.md` for navigation and breadcrumb append operations.
+- `references/domains/universal-attr-config/workflow-server-side-conditions-batch.md` when SSC tokens must be applied across shared components.
+- `references/domains/shared-components/workflow-translations.md` for single translation/localization runs.
+- `references/domains/shared-components/workflow-translations-batch.md` for batch translation/localization runs.
+- `references/domains/shared-components/reusable-prompts/translations.md` for human-readable translation prompt scaffolds.
+
+## Loading Contract
+- Start with `templates/shared-components/README.md` unless the prompt already names a specific family.
+- Open the narrowest family files needed for the request; do not load unrelated shared-component families.
+- For translations, keep the family templates and the workflow docs in sync; the workflow docs define process, while the template family defines artifact shape.
+- Use `assets/rules-mapping.json` to load policy files only when the request needs them.

package/skills/apexlang/references/domains/shared-components/workflow-translations-batch.md

@@ -0,0 +1,82 @@
+# Workflow: Translations — Batch Apply
+
+Purpose
+- Apply a bundle of APEX text message translations across multiple languages and keys in one run while respecting placeholder discipline.
+- Treat whole-app or page-level localization asks as batch text-message conversion work, not as permission to inline translated literals throughout component definitions.
+- Required output shape for app/page localization runs:
+  - `shared-components/messages.apx`
+  - `application.apx` with `globalization { translationMethod: textMessages }`
+  - component rewiring to `&APP_TEXT$KEY.`
+
+Required inputs
+- Discovery mode for app/page translation intents:
+  - `target_app`: current app context or explicit app path / alias.
+  - `language`: target locale name or code.
+  - `scope`: `app` or `page`.
+  - `page`: required only when `scope: page`.
+  - Discovery mode means scanning the requested scope for user-facing literals that must be converted into shared text-message keys and component substitution references.
+- Explicit bundle mode:
+  - `operation`: replace | merge | append (default `replace`).
+  - `translation_bundle`: object keyed by message key → language code → translated text.
+  - `fallback_language`: default source language when a translation is missing.
+  - `languages`: list of language codes to confirm coverage (optional when bundle enumerates all languages).
+  - `targets`: optional list mapping message keys to component references (page/region/item/button/static region).
+  - Optional single-target convenience input: `target` (same structure as one `targets` entry; normalized to a one-item list).
+  - Backward compatibility: accept `apply_to` and normalize it to `targets`.
+  - `auto_translate`: optional flag to request AI assistance for missing entries.
+  - `log_path`: optional override for translation logs.
+
+Clarify — progressive prompts
+- If the prompt explicitly asks for a page control such as a button/menu/selector together with translation or language wording, ask whether the user wants runtime language switching or text-message localization before continuing.
+- If the user intent is translation but scope is unclear, ask in simple English: `Do you want me to translate the whole app or just one page?`
+- If page scope is chosen, ask in simple English: `Which page do you want me to translate?`
+- Confirm the number of keys and languages contained in the bundle only when the user supplied a bundle.
+- Validate that every translation preserves placeholder tokens (e.g., `#USER#`, `&APP_NAME.`).
+- For AI-assisted fills, confirm which languages require machine translation and whether manual review is needed before finalizing.
+- For each key, confirm whether existing messages should be replaced, merged, or appended (defaults to `operation: replace`).
+
+Never do this
+- Do not replace page titles, region names, labels, help text, breadcrumbs, `messages.whenNoDataFound`, confirmations, or static HTML with direct translated literals when the run is app/page localization.
+- Do not treat `shared-components/messages.apx` as optional for app/page localization output.
+- Do not leave the translated scope without `&APP_TEXT$...` substitutions.
+
+Load
+- references/policies/memory-bank/00-guard/ai.guard.md
+- references/policies/memory-bank/10-global/apex.global.md
+- assets/domains/shared-components/translations/languages.json (language definitions)
+- assets/domains/shared-components/translations/prompts.json (placeholder guidance)
+- templates/shared-components/translations/translations._index.md
+- templates/shared-components/translations/translations.text-messages._common.md
+- templates/shared-components/translations/translations.text-messages.consumption.example.md
+- Tier 1 single translation workflow `references/domains/shared-components/workflow-translations.md`
+
+Execution model
+- Normalize `target`/`apply_to` -> `targets`.
+- In discovery mode, scan the targeted app or page for user-facing literals, derive message keys, and construct a generated translation bundle before applying updates.
+- Discovery mode must produce both:
+  - shared `textMessage` entries for the requested language variants
+  - component rewiring so titles, labels, help text, confirmations, breadcrumbs, and static content consume substitutions instead of literal translated text
+- When discovery mode adds or updates the application globalization block and the user did not specify a derivation strategy, default to `languageDerivedFrom: browserPreference`.
+- Iterate through each message key in the bundle.
+  - For each language in `languages` (or bundle keys), invoke the single translation workflow with the provided text.
+  - Record Missing Inputs when a translation is absent and `auto_translate` is false.
+  - When `auto_translate` true, call the translation prompt, log prompts/responses, and mark the entry as AI-generated.
+  - When `targets` includes component references, schedule updates to those components (labels, titles, help text, static content) to reference the substitution string.
+- Update `shared-components/messages.apx` entries grouped by language.
+- Keep one canonical message key per translation across all variants; keep the `textMessage` identifier stable and use nested `message.language` as the only language discriminator.
+- Do not ship app/page localization runs with direct translated literals left in user-facing component attributes when those attributes are in scope for translation.
+- Do not generate helper source files or other non-APEXlang artifacts unless the user explicitly asked for tooling work.
+- Maintain a consolidated change log and translation log for audit.
+
+Completion
+- Revision writes updated shared-components/messages.apx, updates referenced components (pages/regions/items/buttons/static HTML) to use substitution strings, and applies any globalization block changes requested.
+- Unless the user explicitly overrides the derivation mode, globalization changes emitted by this workflow should use `languageDerivedFrom: browserPreference`.
+- Logs stored under `log_path` with batch identifier, `operation`, and timestamp.
+
+Notes
+- Batch workflow orchestrates single-key translation updates; it does not introduce new templates.
+- Enforce placeholder preservation: critique must fail if HTML tokens or substitution strings differ.
+- Critique must hard-fail `missing_messages_artifact` when app/page localization is in scope and `shared-components/messages.apx` is missing.
+- Critique must also hard-fail `missing_conversion`, `invalid_consumption`, and `missing_globalization_setup` for app/page localization runs when applicable.
+- Critique must hard-fail `non_apexlang_output` when the run emits unrelated helper files.
+- Provide summary output listing keys/languages processed, missing translations, and AI-assisted entries.

package/skills/apexlang/references/domains/shared-components/workflow-translations.md

@@ -0,0 +1,72 @@
+# Workflow: Translations
+
+Purpose
+- Seed, review, and maintain text message translations using the canonical `shared-components/translations/` family while emitting `shared-components/messages.apx`.
+- For plain-language localization asks such as `translate my app` or `make this app available in another language`, the expected outcome is text-message localization, not direct replacement of component copy with translated literals.
+- Required output shape for app/page localization runs:
+  - `shared-components/messages.apx`
+  - `application.apx` with `globalization { translationMethod: textMessages }`
+  - component rewiring to `&APP_TEXT$KEY.`
+- If a prompt explicitly asks for a page control such as a button/menu/selector together with translation or language wording, do not auto-route here until runtime-switch versus localization intent is clarified.
+
+Required inputs
+- Discovery mode (default for plain-language prompts):
+  - `target_app`: current app context or explicit app path / alias.
+  - `language`: target locale name or code referencing translations.languages.json.
+  - `scope`: `app` or `page`.
+  - `page`: required only when `scope: page`.
+  - Discovery mode means: find user-facing literals that must become shared text-message keys, generate localized message variants, and rewire component attributes to substitution syntax.
+- Explicit-input mode (advanced):
+  - `message_keys`: list of substitution string identifiers (e.g., `ADMINISTRATION`, `HELP`).
+  - `source_text`: base language text for each key; HTML and placeholder tokens must remain intact.
+  - `languages`: target locale codes referencing translations.languages.json.
+  - `apply_to`: optional list of component references (page, region, item, button, static region) where the message key should replace hard-coded text.
+
+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.page.md (ensures substitution usage standards)
+
+Assets
+- assets/domains/shared-components/translations/languages.json — authoritative runtime language list.
+- templates/shared-components/translations/translations._index.md — canonical translation entrypoint.
+- templates/shared-components/translations/translations.text-messages._common.md — message authoring contract.
+- templates/shared-components/translations/translations.text-messages.consumption.example.md — apply-to-components examples.
+- assets/domains/shared-components/translations/prompts.json — prompt templates describing placeholder preservation requirements.
+
+Options
+- `auto_translate`: true by default for discovery mode. Record prompts used when AI assistance is active.
+- `update_globalization_block`: true by default for discovery mode. Insert or verify `translationMethod: textMessages` and the configured runtime language derivation within application.apx.
+- Default runtime language derivation for translation/localization runs is `languageDerivedFrom: browserPreference` unless the user explicitly requests a different derivation strategy.
+- `scope_prompt_policy`: follow `assets/domains/shared-components/translations/default-config.json`; when scope is unclear, ask the configured simple-English question and do not invent scope.
+- `log_path`: defaults to ``APEXLANG_OUTPUT_ROOT/logs/translations``; controls where prompt/response metadata is written for audit.
+- Generated outputs for this workflow must stay within APEXlang artifacts plus standard workflow logs. Do not create helper source files unless the user explicitly requested tooling work.
+
+Never do this
+- Do not replace page titles, region names, labels, help text, breadcrumbs, `messages.whenNoDataFound`, confirmations, or static HTML with direct translated literals when the run is app/page localization.
+- Do not treat `shared-components/messages.apx` as optional for app/page localization output.
+- Do not leave the translated scope without `&APP_TEXT$...` substitutions.
+
+Execution
+- In discovery mode, identify hard-coded user-facing text from the targeted app or page, generate message keys, and replace targeted literals with text-message substitutions.
+- Do not leave localized literals in labels, titles, help text, confirmations, breadcrumbs, static content, or similar user-facing component attributes when those values can be sourced from shared text messages.
+- If a literal cannot be converted safely because the target location, source text, or key mapping is ambiguous, record Missing Inputs and block completion rather than emitting localized literals directly in the component.
+- Updated `shared-components/messages.apx` with localized `textMessage` entries grouped by language, keeping placeholders and HTML identical to source.
+- Emit `message.text` as a direct scalar `text: "..."` value inside each `textMessage`. Do not generate fenced ````text` blocks for `message.text`.
+- Reuse the same translation message key across all language variants of a logical message; keep the `textMessage` identifier stable and let nested `message.language` distinguish variants.
+- Optional patch to `application.apx` globalization block when requested.
+  - When this workflow adds or updates the globalization block without an explicit user override, default to `languageDerivedFrom: browserPreference`.
+- Translation log under `log_path/{artifact}-{timestamp}.json` capturing workflow inputs, prompts issued to LLMs, returned translations, manual notes, and any Missing Inputs.
+
+Acceptance
+- Plain-language translation requests pass only when user-facing component text is consumed through text-message substitutions and the translated payload lives in `textMessage` entries.
+- Critique must hard-fail translation runs with:
+  - `missing_messages_artifact`: app/page localization was in scope but `shared-components/messages.apx` was not emitted.
+  - `missing_conversion`: user-facing literals were detected but not converted to message keys.
+  - `invalid_consumption`: components still use direct text instead of substitution references.
+  - `missing_globalization_setup`: translation artifacts exist but `translationMethod: textMessages` was not enabled when the app is intended to localize by text messages.
+  - `non_apexlang_output`: the run generated non-APEXlang helper files without explicit user direction.
+
+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`.
+- When `apply_to` is provided, ensure the relevant component definitions reference the substitution string (labels, titles, help text, static content, etc.).

package/skills/apexlang/references/domains/template-components/registry.md

@@ -0,0 +1,13 @@
+# Component Registry Excerpts — Template Components
+
+| Keyword | Workflow / Component | Notes |
+|---------|----------------------|-------|
+| `button` | `button` / `button-actions-batch` | Button templates, confirmations |
+| `button template` | `template-button` | Maps to `40-components/apex.templates.md` |
+| `content row` | `region-template-content-row` | Layout slot adjustments |
+| `metric card` | `region-template-metric-card` | KPI / summary card layouts via `themeTemplateComponent/metricCard` |
+| `cards` | `cards` | Use for UT card templates |
+| `alerts` | `alerts` | Alert template options |
+| `help-text-batch` | `references/domains/universal-attr-config/workflow-help-text-batch.md` | Inline help for template-driven items |
+
+Use `components.registry.json` to locate synonyms and associated templates.

package/skills/apexlang/references/domains/template-components/templates.md

@@ -0,0 +1,29 @@
+# Template & Rule References — Template Components
+
+## 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/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`
+- `assets/rules-mapping.json`
+
+## Operational References
+## Templates
+- `templates/template-components/content-row/content-row._common.md`
+- `templates/template-components/content-row/content-row._index.md`
+- `templates/template-components/content-row/content-row.report-minimal.md`
+- `templates/template-components/content-row/content-row._index.md`
+- `templates/template-components/button/button._common.md`
+- `templates/template-components/button/button._index.md`
+- `templates/template-components/metric-card/metric-card._common.md`
+- `templates/template-components/metric-card/metric-card._index.md`
+- `templates/items/select-list/select-list._index.md`
+- `templates/items/text-field/text-field._index.md`
+- `templates/buttons/buttons._index.md`
+
+For content-row page or region creation, load `content-row._common.md` first, then `content-row._index.md`, and default to `content-row.report-minimal.md` unless the prompt explicitly requests richer features. When badge iconography or placement is requested, use `plugin-badge.icon` and `plugin-badge.position` from the Content Row contract.
+
+Consult `assets/rules-mapping.json` to load only the listed rules per request.

package/skills/apexlang/references/domains/template-components/workflow-items-templates.md

@@ -0,0 +1,37 @@
+# Workflow: Items & Templates
+
+Purpose
+- Configure items and templates with validated attributes and LOVs.
+
+Required inputs
+- Item types, validation needs, LOV sources, template targets.
+
+Clarify — progressive prompts
+- Do any items or templates require a server-side condition? (Answer "none" to skip.)
+- If yes, identify the component scope (item, button, region, process, or dynamic action) and name.
+- Provide the desired condition type or business rule. Acceptable types are listed in references/policies/memory-bank/20-data/apex.logic.md.
+- Collect the required attributes for that type (item reference, comparison 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/40-components/apex.items.md
+- references/policies/memory-bank/40-components/apex.templates.md
+- references/policies/memory-bank/20-data/apex.sql.md (for LOV SQL/format masks)
+
+Policy
+- Never invent attribute/value pairs; follow templates and rule examples.
+- For content-row page or region generation, use `content-row.report-minimal.md` as the default starting scenario.
+- Only layer `report-avatar-badge`, `report-link-positions`, `report-primary-actions-menu`, `report-grouping-selection`, or `report-appearance-variants` when those capabilities are explicitly requested.
+- For Content Row avatar rendering, use `settings.displayAvatar`; keep `plugin-avatar` for avatar configuration only, including `description` and `size` when needed.
+- For Content Row badge rendering, use `settings.displayBadge`; keep `plugin-badge` for badge configuration only.
+- When the prompt asks for badge visual treatment, use `plugin-badge.style`, `plugin-badge.shape`, `plugin-badge.icon`, and `plugin-badge.position` for supported values such as `subtle`, `rounded`, `fa-city`, and `end`.
+- Ensure `primaryActions` examples use valid `action ... (` components closed with `)`.
+
+References
+- references/policies/governance/00-governance.md
+- assets/rules-mapping.json
+
+Completion
+- After Revision, gather ``db_connection_name`, `app_path`, and `application_id` if missing, run `references/ops/runtime-gates/02-direct-sqlcl-validate-gate.md`, then route to `references/ops/runtime-gates/01-direct-sqlcl-import.md`.
+- Fail the workflow if a requested server-side condition does not resolve to a catalog type or lacks required attributes.

package/skills/apexlang/references/domains/universal-attr-config/reusable-prompts/help_text.md

@@ -0,0 +1,22 @@
+# APEX Help Text — Reusable Prompts
+
+This guide standardizes prompt inputs to request, preview, and validate help text across APEX components.
+
+## 1. Page-level help
+- Prompt scaffold:
+  - "Provide page help for `<PAGE>` using Text Message `<TM_KEY>`; summarize purpose and required steps."
+
+## 2. Item inline help
+- Prompt scaffold:
+  - "Draft inline help for `<ITEM>` describing acceptable input. Use TM `<TM_KEY>`."
+
+## 3. Item detailed help dialog
+- Prompt scaffold:
+  - "Provide detailed help text for `<ITEM>` explaining validation/dependencies. Use TM `<TM_KEY>`."
+
+## Checklist
+- Prefer Text Messages/shared components (avoid hard-coded literals).
+- Inline help <= 60 chars; detailed help <= 400 chars unless governance changes.
+- Avoid PII/secrets and avoid decorative HTML unless template requires it.
+
+For structured preview payload conventions, follow workflow and template contracts.

package/skills/apexlang/references/domains/universal-attr-config/templates.md

@@ -0,0 +1,16 @@
+# Template & Rule References — Universal Attribute Config
+
+## Authoritative Policies
+- `references/policies/governance/00-governance.md`
+- `references/policies/memory-bank/00-guard/ai.guard.md`
+- `assets/rules-mapping.json`
+- `references/policies/memory-bank/10-global/apex.global.md`
+- `references/policies/memory-bank/20-data/apex.logic.md`
+- `references/policies/memory-bank/30-pages/apex.page.md`
+- `references/policies/memory-bank/40-components/apex.items.md`
+
+## Operational References
+- `references/domains/universal-attr-config/workflow-help-text-batch.md`
+- `references/domains/universal-attr-config/workflow-server-side-conditions-batch.md`
+- `references/domains/universal-attr-config/workflow-page-sequencing.md`
+- `references/domains/universal-attr-config/reusable-prompts/help_text.md`

package/skills/apexlang/references/domains/universal-attr-config/workflow-help-text-batch.md

@@ -0,0 +1,48 @@
+# Workflow: Help Text — Batch Draft
+
+Purpose
+- Collect, preview, and validate help text updates across pages, regions, items, buttons, and validations without applying finals.
+
+Required inputs
+- `operation`: draft | apply | revert (default `draft`).
+- `scope`: page | item | button | validation.
+- `targets`: list of component identifiers (`Pnn_COMPONENT`, region/process alias).
+- Optional single-target convenience input: `target` (same structure as one `targets` entry; normalized to a one-item list).
+- `source_type`: text_message | column_comment | manual_review.
+- `text_message_key`: required when source_type = text_message.
+- `authoritative_source`: reference (column comment, SOP, ticket) when source_type ≠ text_message.
+- `inline_help`: short hint (≤60 characters) when applicable.
+- `detailed_help`: full help text (≤400 characters) when applicable.
+- `localization`: languages requesting translation (ISO codes) or `none`.
+
+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.page.md (page/regional help)
+- references/policies/memory-bank/30-pages/apex.form.md (form items)
+- references/policies/memory-bank/40-components/apex.items.md
+- references/domains/universal-attr-config/reusable-prompts/help_text.md
+
+Execution model
+- Normalize `target` -> `targets`.
+- Validate scope/component compatibility (e.g., inline help only for items supporting it; regions lack intrinsic help attributes).
+- For each target:
+  - Confirm source_type alignment (Text Message preferred; column comments must be production-ready).
+  - Merge shared inputs with per-target overrides (custom TM keys, copy tweaks).
+  - Generate preview entry capturing intent, inline help, detailed help, Text Message references, and localization notes.
+  - Enforce guardrails: text length limits, no hard-coded literals, professional tone, no PII/credentials, alignment with section 8 when `plsqlExpression` is referenced.
+  - Record violations as Missing Inputs or Required Revisions; block drafts when critical data is absent.
+- Persist a compact run summary to `the temp-runtime logs directory under `APEXLANG_OUTPUT_ROOT/logs/`` only when the workflow explicitly needs durable evidence.
+- `operation: draft` does not apply direct app-file changes yet.
+
+Completion
+- Output status summary (ready vs blocked targets). Highlight missing TM keys or translation tasks.
+- `operation: draft`: keep help text changes in the transient temp workspace until approval.
+- `operation: apply`: revision applies approved help text and records a compact status entry only when needed.
+- `operation: revert`: revision restores the previous state using the recorded run context when durable evidence exists.
+
+Notes
+- Inline help must remain ≤60 characters; detailed help ≤400 characters unless governance updates say otherwise.
+- Encourage Text Messages for localization; when using column comments/manual review, schedule translation key creation.
+- Content must differentiate user-facing help from developer comments; comments block remains for internal notes.
+- Pair with translation workflows when `localization` includes languages beyond the default.

package/skills/apexlang/references/domains/universal-attr-config/workflow-page-sequencing.md

@@ -0,0 +1,18 @@
+# Workflow: Region Sequencing & Comments (Derived from Page Scaffolding)
+
+Purpose
+- Adjust region sequencing, comments, and universal attributes on a page.
+
+Derivation
+- Consolidated from legacy page scaffolding guidance; now focused on layout ordering, breadcrumbs, and navigation sequencing.
+
+Inputs
+- Region identifiers with desired display sequence
+- Comments or developer notes per region
+- Optional breadcrumbs/navigation adjustments (coordinate with Page Patterns skill)
+
+Guardrails
+- Maintain accessibility order; primary content should remain early in the page structure.
+- Record developer comments in a compact run summary only when the workflow explicitly persists durable evidence.
+
+Use this reference alongside `references/domains/page-components/page-patterns.md` when sequencing or attributing regions.

package/skills/apexlang/references/domains/universal-attr-config/workflow-server-side-conditions-batch.md

@@ -0,0 +1,42 @@
+# Workflow: Server-Side Conditions — Batch Draft
+
+Purpose
+- Collect and preview server-side condition updates across multiple components/pages without applying finals.
+
+Required inputs
+- `operation`: draft | apply | revert (default `draft`).
+- `mode`: token-based or explicit catalog type.
+- `token`: server-side condition design token (when mode = token).
+- `condition_type`: catalog type from 20-data/apex.logic.md (when mode = explicit).
+- `attributes`: required fields for the chosen type (item, value/list, request value, plsqlExpression, sqlQuery, etc.).
+- `targets`: list of page/component references (`Pnn_COMPONENT_TYPE.ID`).
+- Optional single-target convenience input: `target` (same structure as one `targets` entry; normalized to a one-item list).
+- Optional per-target overrides: alternative item/value/list, notes, apply=false flag.
+- When `condition_type` = plsqlExpression, require the generator to apply the guardrails in 20-data/apex.logic.md section 8 (bind syntax, null safety, no DML/dynamic SQL) and capture the intent + expression in the preview.
+
+Load
+- 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.logic.md
+- Component/page rules resolved per target component type (e.g., `30-pages/apex.form.md`, `40-components/apex.items.md`).
+
+Execution model
+- Normalize `target` -> `targets`.
+- Resolve the SSC definition (token or explicit type/attributes) against the catalog.
+- For each target component:
+  - Confirm the component supports `serverSideCondition {}`.
+  - Merge shared SSC data with per-target overrides.
+  - Collect a preview entry describing the component, resolved condition, and any missing attributes.
+- Persist a compact run summary to `the temp-runtime logs directory under `APEXLANG_OUTPUT_ROOT/logs/`` only when the workflow explicitly needs durable evidence.
+- Do NOT apply direct app-file changes. Flag Missing Inputs when catalog requirements are incomplete.
+
+Completion
+- `operation: draft`: preview only; notify callers to re-run with approval to apply changes.
+- `operation: apply`: revision applies approved entries and logs `state: applied`.
+- `operation: revert`: revision restores entries from the referenced log record and logs `state: reverted`.
+- Revision records the action reference in the compact run evidence when the workflow persists durable logs.
+
+Notes
+- Applies to buttons, items, regions, page processes, dynamic actions, validations, and other SSC-capable components.
+- Maintain progressive disclosure; load only component rules relevant to targets.
+- Multi-token runs require separate executions to keep change logs focused.

package/skills/apexlang/references/ops/one-message-router-contract.md

@@ -0,0 +1,97 @@
+# One‑Message Routers — Pattern and Conventions (Authoritative)
+
+Purpose
+- Establish a consistent pattern for one‑message, natural‑language routers that dispatch to “master” workflows.
+- Keep routers small, deterministic, and independent (no duplication of workflow logic).
+- Accept free-form user input by default: fragments, shorthand, broken grammar, terse phrases, and mixed natural-language commands must still be routable.
+
+Load order
+- Keep router contracts inside domain entrypoint skills: `skills/<domain>/SKILL.md`.
+- Numeric prefixes determine order; use distinct Match keywords to avoid collisions.
+
+Router contract (machine‑parseable headers)
+- Router: true
+- Kind: one-message
+- TargetWorkflow: <path to workflow md>
+- Match: case‑insensitive keywords list that trigger the router
+- Optional shared behavior fields:
+  - `prompt_normalization: enabled`
+  - `clarification_rounds_max: 1`
+  - `clarification_style: simple_english`
+  - `ambiguity_policy: ask_then_stop`
+
+Routing behavior
+- If a single incoming message contains any Match keyword(s) and NO explicit structured inputs block:
+  - Invoke TargetWorkflow with Defaults (merged with any simple key: value overrides present in the same message).
+- If structured inputs are present, DO NOT route (let the workflow consume them directly).
+- Never re‑route to another router or to the constitutional master unless you are the master router.
+
+Prompt-normalization contract
+- Treat sparse input as valid by default. Examples: noun lists, shorthand like `source report lookup filter`, broken grammar, partial identifiers, or mixed imperative fragments.
+- Normalize whatever is explicit in the prompt before asking anything else.
+- Ask follow-up questions only for critical blockers that materially change the workflow, target, or safety gates.
+- Follow-ups must be short, plain-English prompts. Prefer concrete options or one missing identifier request over broad re-interviewing.
+- Allow at most one clarification round per unresolved ambiguity cluster.
+- If critical ambiguity remains after that round, emit `Missing Inputs` and stop; do not guess or require the user to restate the request as a structured payload.
+
+Defaults (safe)
+- Defaults must be minimal and safe for “Plan mode” execution.
+- Example fields (only if relevant to the TargetWorkflow):
+  - apex_export_path: applications/app_###/
+  - app_ids: []
+  - prereq_source: unresolved
+  - db_mode: unresolved
+  - db_connection_name: ""          # needed with APEX workspace name if running live DB steps
+  - apex_workspace_name: ""         # corresponding APEX workspace for live DB steps
+- environment: dev
+- dry_run: true
+- Merge rule: user overrides in the same one‑liner message replace Default values; do not invent missing fields.
+- Routers should follow `references/policies/governance/prompt-normalization.md`, prefer permissive defaults such as `prompt_normalization: enabled`, and keep clarification behavior explicit instead of rejecting informal prompts.
+
+Safeguards and gates
+- Secrets hygiene: never log secrets or full connect strings.
+- dry_run must remain true unless BOTH dry_run: false AND environment: dev are provided.
+- For DB-backed domains, prefer the schema-first prerequisite gate: inspect `assets/workspace-intelligence.json`, use an eligible offline schema dictionary when available, then traverse saved SQLcl connections before the final clarification prompt.
+- If DB work is requested and live DB context is still required after the prerequisite gate, allow the TargetWorkflow’s Pre‑Agent 0 to halt with Missing Inputs rather than fabricating a connection.
+- For interactive DB-backed runs, inspect offline schema metadata and scan saved SQLcl connections before asking the user anything about DB mode.
+- Use deterministic saved SQLcl connection discovery to suggest aliases before asking; require the user to specify `db_connection_name` and the corresponding APEX workspace name before live DB work. Use `Provide db_connection_name and the corresponding APEX workspace name for this workflow.` as the last clarification fallback after discovery leaves live DB context unresolved.
+- No changes to templates/ content in plan-only runs; write artifacts to the temp-runtime logs directory under `APEXLANG_OUTPUT_ROOT/logs/`**.
+
+File naming and structure
+- One router contract section per domain skill:
+-   - `SKILL.md`
+-   - `external:oracle-db/plsql`
+-   - `external:oracle-db/schema-modeling`
+- Keep router contracts small and declarative; avoid copying workflow logic or artifacts lists (the workflow owns those).
+
+Keyword design (Match)
+- Use unambiguous, domain‑specific phrases that users naturally type.
+- Avoid broad terms that collide across domains.
+- Examples:
+  - APEX Generation: [build page, interactive report, form, dashboard, application, apex generate, …]
+  - PL/SQL Maintenance: [plsql maintenance, package consolidation, consolidate plsql, check plsql, …]
+
+Examples (single message)
+- Snippet class: `illustrative_prompt`. Replace any `{{...}}` variables before use; do not treat them as schema evidence.
+- APEX generation (constitutional master):
+  build a page with an interactive report on {{source.table}} and a form to edit; refresh report after submit
+- PL/SQL maintenance (standalone):
+  check entire app for all plsql code and see what can be packaged and consolidated
+- PL/SQL maintenance with overrides:
+  check entire app for all plsql code and see what can be packaged and consolidated
+  dry_run: true
+
+Consistency checklist (for any new “master” workflow)
+- [ ] Add a `Router Contract` section to `skills/<domain>/SKILL.md`
+- [ ] Set Router:true, Kind:one-message, TargetWorkflow:<path>
+- [ ] Define specific Match keywords for the domain
+- [ ] Provide safe Defaults appropriate for plan-only execution
+- [ ] Declare or inherit the governance prompt-normalization contract (`prompt_normalization`, one clarification round, simple-English follow-up, ask-then-stop ambiguity policy)
+- [ ] For DB-backed domains, declare `prereq_source`, schema-first prerequisite routing, and the canonical connection/offline prompt as the final fallback
+- [ ] Add Safeguards mirroring governance (00-governance.md)
+- [ ] Include concise Examples to illustrate one-liner usage
+
+Notes
+- Routers are independent of the constitutional master unless they explicitly target it (as with APEX generation).
+- Keep token usage minimal: routers should reference, not duplicate, workflow content and artifacts.
+- See `SKILL.md`, `references/workflows/apex-generation.md`, and `external:oracle-db/plsql` for concrete implementations.

package/skills/apexlang/references/ops/reusable-prompts/orchestration-master-generic.md

@@ -0,0 +1,21 @@
+# Constitutional Orchestration Master — Generic Prompt
+
+Purpose
+- Reusable generic orchestration prompt for multi-agent planning/execution pipelines.
+- Deterministic artifact expectations, explicit missing-input prompts, and domain-specific execution defaults.
+
+Source
+- Migrated from previous docs reusable prompt set.
+- Use this as a generic scaffold, not a replacement for domain `SKILL.md` contracts.
+
+Core defaults
+- `dry_run: true`
+- ask for execution approval only when the host environment requires it, phrased as a short task-level prompt rather than environment mechanics
+- do not add a separate deploy/import confirmation when the active domain contract defines online auto-deploy as the default
+- ask for missing inputs, do not fabricate
+- minimal context loading
+
+See domain masters for runtime contracts:
+- `SKILL.md`
+- `external:oracle-db/plsql`
+- `external:oracle-db/schema-modeling`