pi-apexlang 0.1.0

package/skills/apexlang/assets/domains/business-logic/validations-prompt.md

@@ -0,0 +1,30 @@
+# Sample Prompts for APEX Page Validations
+### A. Basic “required value” prompts
+
+1. “Add validations so that page items `P20_FIRST_NAME` and `P20_LAST_NAME` must both be populated before submit.”
+2. “Check that `P50_AMOUNT` is provided—return the message ‘Amount is required’ when it’s missing.”
+
+### B. Expression-based comparisons / ranges
+
+3. “Create a validation ensuring `P80_END_DATE` is on or after `P80_START_DATE`, with the error ‘End Date must not precede Start Date’.”
+4. “Require that `P35_QUANTITY` is between 1 and 999. Use a single expression validation.”
+
+### C. Function body with conditional logic
+
+5. “If `P40_STATUS` is not null, make `P40_DECISION_DATE` mandatory; otherwise skip. Return a clear message when it fails.”
+6. “Validate `P60_CODE`: it must be at least three characters and not contain spaces. Return an error message describing the rule.”
+
+### D. Regex/format checks
+
+7. “Enforce email format on `P10_EMAIL` using `REGEXP_LIKE`—message ‘Enter a valid corporate email address’.”
+8. “Add a validation for `P25_PHONE` to accept only digits and optional plus sign.”
+
+### E. Lookup / existence check (functionBody)
+
+9. “Ensure `P70_CUSTOMER_ID` exists in CUSTOMER_MASTER; if not, return ‘Customer ID not found’.”
+10. “Validate `P15_DEPT_CODE` by calling `APP_VALIDATION.check_dept(:P15_DEPT_CODE)`; surface any returned message.”
+
+### F. Multi-step / sequenced tests
+
+11. “Add a sequence 10 validation for ‘required’, sequence 20 for ‘minimum length’, and sequence 30 for ‘custom business logic’ on `P90_SERIAL`.”
+12. “Combine two validations on `P45_USER`: first check not null, then ensure value differs from `P45_OLD_USER`.”

package/skills/apexlang/assets/domains/page-components/buttons/button-actions.md

@@ -0,0 +1,19 @@
+# Button Action Batch Workflow
+
+## Summary
+- apply: `references/domains/page-components/buttons/workflow-button-batch.md`
+- target_type: `button-actions-batch`
+- Inputs: operation (`apply|remove`), action_type (for apply), layout/appearance/behavior defaults (for apply), and canonical `targets` (single or batch; legacy `target_button`/`target_buttons` accepted).
+- Output: compact run summary under `the temp-runtime logs directory under `APEXLANG_OUTPUT_ROOT/logs/`` when needed, plus button changes staged in the transient temp workspace outside the repo until publish.
+
+## Template Reference
+- `templates/buttons/buttons._index.md` — canonical dispatcher.
+- `templates/buttons/buttons._common.md` — shared contract and guardrails.
+- `templates/buttons/buttons.*.md` — action-specific variants.
+
+## Usage Notes
+- Validate slot/region combinations using apex.templates.md.
+- Submit buttons still rely on `references/domains/business-logic/processes/workflow-page-processes-batch.md` for invokeApi processes.
+- TriggerAction entries must specify nested settings (PL/SQL or download metadata).
+- Menu entries should be structured as an array of label/layout/behavior blocks.
+- Remove mode performs hard delete with dependency checks and blocks removals that leave dangling references.

package/skills/apexlang/assets/domains/page-components/buttons/buttons.md

@@ -0,0 +1,17 @@
+# Button Prompts
+
+## Purpose
+Standard prompts to gather inputs for button generation and batch updates.
+
+## Prompts
+- "Create a primary submit button with confirmation and DML action".
+- "Add a disabled primary button that triggers downloadable SQL".
+- "Generate a button menu with redirect and PL/SQL execution entries".
+- "Replicate this redirect button across pages 5, 10, 12".
+
+## Checklist
+- Identify action type (submitPage, redirect*, triggerAction, menu).
+- Capture layout (region, slot, sequence) per target.
+- Capture appearance intent (primary, disabled, icon) and map primary styling to `hot: true` in DSL output.
+- Capture behavior specifics (target, databaseAction, confirmation message/style).
+- Note server-side conditions, security schemes, itemsToSubmit/Return.

package/skills/apexlang/assets/domains/page-components/page-patterns/server-side-conditions-prompt.md

@@ -0,0 +1,141 @@
+# Oracle APEX Server-Side Conditions — Reusable Prompts
+
+These prompt snippets help AI tooling emit consistent, guardrail-compliant server-side conditions across component types. Align questions with the orchestration workflows and memory-bank rules before execution.
+
+## 1. Request/Value-Based Conditions
+- **Use when:** Toggling behavior by APEX request value or feature flag token.
+- **Inputs to collect:** request value(s), target components.
+- **Prompt scaffold:**
+  - “Apply request-value condition `<REQUEST>` to [component list]; fail if catalog attributes missing.”
+- **Example draft summary:**
+
+```
+Summary: Apply `ssc.feature.flagEnabled("SALES")` to P10_SAVE button and P20_PROCESS_ORDER process
+
+- Intent: Show Save button only when SALES flag enabled.
+- Condition: `:REQUEST = 'FEATURE_SALES_ENABLED'`
+- Note: Request value derives from feature toggle mapping; no null handling required.
+```
+
+## 2. Item Equality / Inequality Conditions
+- **Use when:** Show/hide components based on item value comparisons.
+- **Inputs to collect:** item name, target values, null handling preference.
+- **Prompt scaffold:**
+  - “Guard [component] when `:Pnn_ITEM` equals `<VALUE>`; ensure NVL handling if nulls allowed.”
+- **Example draft summary:**
+
+```
+Summary: Guard Delete button when status is not active
+
+- Intent: Hide Delete when record is inactive.
+- Condition: `NVL(:P50_STATUS, 'INACTIVE') != 'ACTIVE'`
+- Note: Null fallback prevents null comparison issues.
+```
+
+## 3. List Membership Conditions
+- **Use when:** Component availability depends on item-in-list rules.
+- **Inputs to collect:** item, allowed values, case sensitivity expectations.
+- **Prompt scaffold:**
+  - “Render [component] only when `:Pnn_STATUS` in `<VAL1:VAL2:VAL3>` list.”
+- **Example draft summary:**
+
+```
+Summary: Permit Submit button for new-or-pending statuses
+
+- Intent: Show Submit when status is NEW or PENDING.
+- Condition: `:P15_STATUS IN ('NEW', 'PENDING')`
+- Note: Item is varchar2; upstream logic enforces uppercase.
+```
+
+## 4. Numeric Guard Conditions
+- **Use when:** Require numeric fields to be present and within thresholds.
+- **Inputs to collect:** item, minimum/maximum bounds, zero/negative tolerance.
+- **Prompt scaffold:**
+  - “Allow processing when `:Pnn_AMOUNT` > `<threshold>`; block null/zero cases.”
+- **Example draft summary:**
+
+```
+Summary: Enable Process Order when amount entered
+
+- Intent: Proceed only when order amount is positive.
+- Condition: `:P35_ORDER_AMOUNT IS NOT NULL AND :P35_ORDER_AMOUNT > 0`
+- Note: Item is number; null check precedes numeric comparison.
+```
+
+## 5. Date Window Conditions
+- **Use when:** Start/end dates must be provided and ordered.
+- **Inputs to collect:** start item, end item, inclusive/exclusive expectations.
+- **Prompt scaffold:**
+  - “Render report only when both dates present and start <= end.”
+- **Example draft summary:**
+
+```
+Summary: Render P30_REPORT region when valid date range supplied
+
+- Intent: Display report when start/end dates provided and in range.
+- Condition:
+  :P30_START_DATE IS NOT NULL
+  AND :P30_END_DATE IS NOT NULL
+  AND :P30_START_DATE <= :P30_END_DATE
+- Note: Items are DATE; comparison safe after null checks.
+```
+
+## 6. EXISTS Ownership Checks
+- **Use when:** Visibility depends on data ownership or contextual row existence.
+- **Inputs to collect:** table/view, join columns, security predicate.
+- **Prompt scaffold:**
+  - “Allow action when current user owns the referenced record via EXISTS query; require bind variables.”
+- **Example draft summary:**
+
+```
+Summary: Permit approval when user owns the order
+
+- Intent: Allow approval only for orders owned by current user.
+- Condition:
+  EXISTS (
+    SELECT 1
+    FROM orders o
+    WHERE o.order_id = :P45_ORDER_ID
+    AND o.created_by = :APP_USER
+  )
+- Note: ORDER_ID item is numeric and required upstream.
+```
+
+## 7. PL/SQL Expression Conditions (section 8 guardrails)
+- **Use when:** Condition type is `plsqlExpression` and boolean logic extends beyond catalog shortcuts.
+- **Mandatory guardrails:** bind syntax, explicit null handling, no DML/dynamic SQL, datatype alignment (see references/policies/memory-bank/20-data/apex.logic.md §8).
+- **Prompt scaffold:**
+  - “Draft plsqlExpression with one-line intent + expression; enforce section 8 guardrails and block on violations.”
+- **Example draft summary:**
+
+```
+Summary: Validate availability window for scheduled job region
+
+- Intent: Render job status region only within active schedule window.
+- Condition:
+  :P60_ACTIVE_FLAG = 'Y'
+  AND :P60_START_TS IS NOT NULL
+  AND :P60_END_TS IS NOT NULL
+  AND :P60_START_TS <= SYSTIMESTAMP
+  AND SYSTIMESTAMP <= :P60_END_TS
+- Note: Timestamp items required; no nulls allowed once active flag is Y.
+```
+
+### Guardrail Fail Example
+
+```
+Summary: Proposed predicate rejected (missing bind and null safety)
+
+- Intent: Hide Delete when record is inactive.
+- Proposed: `P50_STATUS != 'ACTIVE'`
+- Violations:
+  - Missing colon prefix on item reference.
+  - Null-unsafe inequality; requires `NVL(:P50_STATUS, 'INACTIVE') != 'ACTIVE'`.
+- Action: Mark entry as `state: blocked` and request correction.
+```
+
+---
+
+**Usage tips**
+- Pair these snippets with the SSC batch workflow to capture intent, condition, and notes in run summaries before applying direct app-file changes.
+- Reference references/policies/memory-bank/20-data/apex.logic.md §8 for enforcement details and reviewer checklist.

package/skills/apexlang/assets/domains/shared-components/translations/default-config.json

@@ -0,0 +1,19 @@
+{
+  "version": 1,
+  "intentMode": "discover-and-generate",
+  "autoTranslate": true,
+  "updateGlobalizationBlock": true,
+  "scopePromptEnabled": true,
+  "scopePromptPolicy": "when_ambiguous",
+  "defaultScope": "app",
+  "followupPromptStyle": "simple_english",
+  "scopePromptText": "Do you want me to translate the whole app or just one page?",
+  "scopePromptOptions": [
+    "Whole app",
+    "One page"
+  ],
+  "pagePromptText": "Which page do you want me to translate?",
+  "logPath": "`APEXLANG_OUTPUT_ROOT/logs/translations`",
+  "discoveryModeNote": "Discovery-mode translation converts user-facing literals into shared text-message keys, rewires component attributes to &APP_TEXT$... substitutions, and writes shared-components/messages.apx. It does not replace component attributes with direct translated literals.",
+  "auditLogFilename": ""
+}

package/skills/apexlang/assets/domains/shared-components/translations/languages.json

@@ -0,0 +1,147 @@
+{
+  "version": 1,
+  "source": "Oracle APEX language support documentation",
+  "notes": "Supported runtime languages for message translation workflows. Use ISO locale codes when expanding entries.",
+  "languages": [
+    {
+      "name": "Arabic",
+      "code": "ar"
+    },
+    {
+      "name": "Brazilian Portuguese",
+      "code": "pt-BR"
+    },
+    {
+      "name": "Croatian",
+      "code": "hr"
+    },
+    {
+      "name": "Czech",
+      "code": "cs"
+    },
+    {
+      "name": "Danish",
+      "code": "da"
+    },
+    {
+      "name": "Dutch",
+      "code": "nl"
+    },
+    {
+      "name": "English",
+      "code": "en"
+    },
+    {
+      "name": "Finnish",
+      "code": "fi"
+    },
+    {
+      "name": "French",
+      "code": "fr"
+    },
+    {
+      "name": "French - Canada",
+      "code": "fr-CA"
+    },
+    {
+      "name": "German",
+      "code": "de"
+    },
+    {
+      "name": "Greek",
+      "code": "el"
+    },
+    {
+      "name": "Hebrew",
+      "code": "he"
+    },
+    {
+      "name": "Hungarian",
+      "code": "hu"
+    },
+    {
+      "name": "Icelandic",
+      "code": "is"
+    },
+    {
+      "name": "Italian",
+      "code": "it"
+    },
+    {
+      "name": "Japanese",
+      "code": "ja"
+    },
+    {
+      "name": "Korean",
+      "code": "ko"
+    },
+    {
+      "name": "Norwegian",
+      "code": "no"
+    },
+    {
+      "name": "Polish",
+      "code": "pl"
+    },
+    {
+      "name": "Portuguese (Portugal)",
+      "code": "pt-PT"
+    },
+    {
+      "name": "Romanian",
+      "code": "ro"
+    },
+    {
+      "name": "Russian",
+      "code": "ru"
+    },
+    {
+      "name": "Serbian - Cyrillic",
+      "code": "sr-Cyrl"
+    },
+    {
+      "name": "Serbian - Latin",
+      "code": "sr-Latn"
+    },
+    {
+      "name": "Simplified Chinese",
+      "code": "zh-Hans"
+    },
+    {
+      "name": "Slovak",
+      "code": "sk"
+    },
+    {
+      "name": "Slovenian",
+      "code": "sl"
+    },
+    {
+      "name": "Spanish",
+      "code": "es"
+    },
+    {
+      "name": "Swedish",
+      "code": "sv"
+    },
+    {
+      "name": "Thai",
+      "code": "th"
+    },
+    {
+      "name": "Traditional Chinese",
+      "code": "zh-Hant"
+    },
+    {
+      "name": "Turkish",
+      "code": "tr"
+    },
+    {
+      "name": "Ukrainian",
+      "code": "uk"
+    },
+    {
+      "name": "Vietnamese",
+      "code": "vi"
+    }
+  ]
+}

package/skills/apexlang/assets/domains/shared-components/translations/prompts.json

@@ -0,0 +1,29 @@
+{
+  "version": 1,
+  "notes": "Prompt templates for AI-assisted translation of APEX text messages.",
+  "defaults": {
+    "tone": "formal",
+    "includePlaceholders": true,
+    "respectHtml": true
+  },
+  "prompts": {
+    "translation": {
+      "instruction": "Translate the provided Oracle APEX text messages into the requested target language while preserving token placeholders such as %0, %1, text-message substitution references such as &APP_TEXT$KEY., and embedded HTML markup (including <br>, <strong>, etc.). Do not translate substitution tokens. These translations are for shared text-message payloads and must not be used to justify direct replacement of component attributes with localized literals. Return JSON with keys: targetLanguage, translations[]. Each translation entry must include key, sourceText, translatedText, reviewNotes (empty string if none).",
+      "examples": [
+        {
+          "targetLanguage": "fr",
+          "messages": [
+            {
+              "key": "ADMINISTRATION",
+              "sourceText": "Administration"
+            },
+            {
+              "key": "HELP",
+              "sourceText": "Help"
+            }
+          ]
+        }
+      ]
+    }
+  }
+}

package/skills/apexlang/assets/domains/template-components/button-actions-prompt.md

@@ -0,0 +1,18 @@
+# Button Action Batch Workflow
+
+## Summary
+- apply: `references/domains/page-components/buttons/workflow-button-batch.md`
+- target_type: `button-actions-batch`
+- Inputs: action_type, layout defaults, appearance defaults, behavior defaults, target buttons (per page).
+- Output: compact run summary under `the temp-runtime logs directory under `APEXLANG_OUTPUT_ROOT/logs/`` when needed, plus button changes staged in the transient temp workspace outside the repo until publish.
+
+## Template Reference
+- `templates/buttons/buttons._index.md` — canonical dispatcher.
+- `templates/buttons/buttons._common.md` — shared contract and guardrails.
+- `templates/buttons/buttons.*.md` — action-specific variants.
+
+## Usage Notes
+- Validate slot/region combinations using apex.templates.md.
+- Submit buttons still rely on `references/domains/business-logic/processes/workflow-page-processes-batch.md` for invokeApi processes.
+- TriggerAction entries must specify nested settings (PL/SQL or download metadata).
+- Menu entries should be structured as an array of label/layout/behavior blocks.

package/skills/apexlang/assets/domains/template-components/help-text-prompt.md

@@ -0,0 +1,73 @@
+# APEX Help Text — Reusable Prompts
+
+This guide standardizes how AI tooling requests, previews, and validates help text across Oracle APEX components.
+
+## 1. Page-Level Help
+- **Intent:** Populate the page Help dialog (accessible via the theme menu).
+- **Inputs to collect:** source (column comment/text message key), audience, translation needs.
+- **Prompt scaffold:**
+  - “Provide page help for `<PAGE>` using Text Message `<TM_KEY>`; summarize purpose and required steps.”
+- **Preview format:**
+```
+Summary: Page-level help for HOME (TM: APP.PAGE.HOME)
+- Intent: Explain Home dashboard layout and available shortcuts.
+- Help Text:
+  Home aggregates department KPIs, pending approvals, and quick links.
+  Use the action buttons to navigate to detailed reports.
+- Note: Content references Text Message APP.PAGE.HOME for localization.
+```
+
+## 2. Item-Level Inline Help
+- **Intent:** Provide a concise hint beneath the item label.
+- **Inputs:** item name, data type, validation requirements, length (~3–6 words).
+- **Prompt scaffold:**
+  - “Draft inline help for `<ITEM>` so users know acceptable input (max 40 chars). Use TM `<TM_KEY>`.”
+- **Preview:**
+```
+Summary: Inline help for P1_CB_SS (TM: ITEM.P1_CB_SS.INLINE)
+- Intent: Remind users to pick a preset value or reveal manual entry.
+- Inline Help: Choose a preset or open manual entry.
+- Note: Short hint; no HTML.
+```
+
+## 3. Item-Level Detailed Help Dialog
+- **Intent:** Show detailed instructions when users click field help icon.
+- **Inputs:** item name, business rule, example values, translation key.
+- **Prompt scaffold:**
+  - “Provide detailed help text for `<ITEM>` explaining validation and sources. Use TM `<TM_KEY>`.”
+- **Preview:**
+```
+Summary: Help dialog for P1_CB_SS (TM: ITEM.P1_CB_SS.HELP)
+- Intent: Explain combobox usage and manual-entry workflow.
+- Help Text:
+  Use the dropdown to pick a standard option. If the value isn’t listed,
+  click Manual Entries and provide the request code supplied by operations.
+  Required fields are marked with *. Values sync to the Ordering API.
+- Note: Reviewed for length (<400 chars); uses Text Message ITEM.P1_CB_SS.HELP.
+```
+
+## 4. Help Text Checklist (apply to every prompt)
+- Reference Text Messages/shared components (no hard-coded literals).
+- Keep inline help ≤ 60 characters; detailed help ≤ 400 characters unless justified.
+- Avoid repeating label text; focus on “why/how”.
+- Mention related validation or dependencies (e.g., item must exist before manual entries).
+- Strip HTML unless the template explicitly supports it.
+- Confirm translation keys exist or schedule them via translation workflow.
+
+- For the structured preview JSON used by help-text batches, see `templates/region-components/help-text/help-text.standard.md` (section D).
+
+## 6. Guardrail Fail Example
+```
+Summary: Proposed inline help rejected
+- Intent: Clarify acceptable date range.
+- Proposed Text: “Enter valid date plz!!!”
+- Violations:
+  - Informal language.
+  - No Text Message reference.
+  - Fails length/clarity requirements.
+- Action: Reject and request corrected input.
+```
+
+---
+
+Pair these prompts with the forthcoming Help Text Batch Workflow to gather, preview, and validate help content before applying updates.

package/skills/apexlang/assets/domains/universal-attr-config/help_text.md

@@ -0,0 +1,73 @@
+# APEX Help Text — Reusable Prompts
+
+This guide standardizes how AI tooling requests, previews, and validates help text across Oracle APEX components.
+
+## 1. Page-Level Help
+- **Intent:** Populate the page Help dialog (accessible via the theme menu).
+- **Inputs to collect:** source (column comment/text message key), audience, translation needs.
+- **Prompt scaffold:**
+  - “Provide page help for `<PAGE>` using Text Message `<TM_KEY>`; summarize purpose and required steps.”
+- **Preview format:**
+```
+Summary: Page-level help for HOME (TM: APP.PAGE.HOME)
+- Intent: Explain Home dashboard layout and available shortcuts.
+- Help Text:
+  Home aggregates department KPIs, pending approvals, and quick links.
+  Use the action buttons to navigate to detailed reports.
+- Note: Content references Text Message APP.PAGE.HOME for localization.
+```
+
+## 2. Item-Level Inline Help
+- **Intent:** Provide a concise hint beneath the item label.
+- **Inputs:** item name, data type, validation requirements, length (~3–6 words).
+- **Prompt scaffold:**
+  - “Draft inline help for `<ITEM>` so users know acceptable input (max 40 chars). Use TM `<TM_KEY>`.”
+- **Preview:**
+```
+Summary: Inline help for P1_CB_SS (TM: ITEM.P1_CB_SS.INLINE)
+- Intent: Remind users to pick a preset value or reveal manual entry.
+- Inline Help: Choose a preset or open manual entry.
+- Note: Short hint; no HTML.
+```
+
+## 3. Item-Level Detailed Help Dialog
+- **Intent:** Show detailed instructions when users click field help icon.
+- **Inputs:** item name, business rule, example values, translation key.
+- **Prompt scaffold:**
+  - “Provide detailed help text for `<ITEM>` explaining validation and sources. Use TM `<TM_KEY>`.”
+- **Preview:**
+```
+Summary: Help dialog for P1_CB_SS (TM: ITEM.P1_CB_SS.HELP)
+- Intent: Explain combobox usage and manual-entry workflow.
+- Help Text:
+  Use the dropdown to pick a standard option. If the value isn’t listed,
+  click Manual Entries and provide the request code supplied by operations.
+  Required fields are marked with *. Values sync to the Ordering API.
+- Note: Reviewed for length (<400 chars); uses Text Message ITEM.P1_CB_SS.HELP.
+```
+
+## 4. Help Text Checklist (apply to every prompt)
+- Reference Text Messages/shared components (no hard-coded literals).
+- Keep inline help ≤ 60 characters; detailed help ≤ 400 characters unless justified.
+- Avoid repeating label text; focus on “why/how”.
+- Mention related validation or dependencies (e.g., item must exist before manual entries).
+- Strip HTML unless the template explicitly supports it.
+- Confirm translation keys exist or schedule them via translation workflow.
+
+- For the structured preview JSON used by help-text batches, see `templates/region-components/help-text/help-text.standard.md` (section D).
+
+## 6. Guardrail Fail Example
+```
+Summary: Proposed inline help rejected
+- Intent: Clarify acceptable date range.
+- Proposed Text: “Enter valid date plz!!!”
+- Violations:
+  - Informal language.
+  - No Text Message reference.
+  - Fails length/clarity requirements.
+- Action: Reject and request corrected input.
+```
+
+---
+
+Pair these prompts with the forthcoming Help Text Batch Workflow to gather, preview, and validate help content before applying updates.

package/skills/apexlang/assets/domains/universal-attr-config/translations.prompts.json

@@ -0,0 +1,29 @@
+{
+  "version": 1,
+  "notes": "Prompt templates for AI-assisted translation of APEX text messages.",
+  "defaults": {
+    "tone": "formal",
+    "includePlaceholders": true,
+    "respectHtml": true
+  },
+  "prompts": {
+    "translation": {
+      "instruction": "Translate the provided Oracle APEX text messages into the requested target language while preserving token placeholders such as %0, %1, substitution syntax like &{KEY}, and embedded HTML markup (including <br>, <strong>, etc.). Do not translate substitution tokens. Return JSON with keys: targetLanguage, translations[]. Each translation entry must include key, sourceText, translatedText, reviewNotes (empty string if none).",
+      "examples": [
+        {
+          "targetLanguage": "fr",
+          "messages": [
+            {
+              "key": "ADMINISTRATION",
+              "sourceText": "Administration"
+            },
+            {
+              "key": "HELP",
+              "sourceText": "Help"
+            }
+          ]
+        }
+      ]
+    }
+  }
+}

package/skills/apexlang/assets/orchestration.manifest.json

@@ -0,0 +1,18 @@
+{
+  "version": 1,
+  "description": "Registry of orchestration masters used by routers.",
+  "masters": [
+    {
+      "id": "apex-generation",
+      "workflow": "SKILL.md"
+    },
+    {
+      "id": "plsql",
+      "workflow": "external:oracle-db/plsql"
+    },
+    {
+      "id": "schema-modeling",
+      "workflow": "external:oracle-db/schema-modeling"
+    }
+  ]
+}

package/skills/apexlang/assets/routing-assets-index.json

@@ -0,0 +1,36 @@
+{
+  "version": 2,
+  "package_profile": "public-product",
+  "entries": [
+    {
+      "id": "public-router",
+      "kind": "catalog",
+      "path": "assets/routing-catalog-main.json",
+      "owner": "public-product"
+    },
+    {
+      "id": "public-load-policies",
+      "kind": "catalog",
+      "path": "assets/routing-load-policy.json",
+      "owner": "public-product"
+    },
+    {
+      "id": "workspace-intelligence",
+      "kind": "context-contract",
+      "path": "assets/workspace-intelligence.json",
+      "owner": "public-product"
+    },
+    {
+      "id": "context-schema",
+      "kind": "context-contract",
+      "path": "assets/context-schema.json",
+      "owner": "public-product"
+    },
+    {
+      "id": "context-adapters",
+      "kind": "context-contract",
+      "path": "assets/context-adapters.json",
+      "owner": "public-product"
+    }
+  ]
+}