@salesforce/afv-skills 1.65.0 → 1.66.0

package/skills/industries-data-space-feature-mappings-configure/SKILL.md

@@ -1,245 +0,0 @@
----
-name: industries-data-space-feature-mappings-configure
-description: "Use this skill when users want to manage Education Cloud feature → Data Cloud data-space mappings. Trigger when users mention data, space, feature, mappings, data space feature mappings."
-metadata:
-  version: "1.0"
----
-
-# Managing Data Space Feature Mappings
-
-## When to Use This Skill
-
-Manage Education Cloud feature → Data Cloud data-space mappings.
-`getDataSpaceFeatures` returns an EDU-scoped choices list
-(STUDENT_SUCCESS, FINANCIAL_AID) — but the create path itself is a
-pass-through to CDP's DataSpaceAwareFeatureType enum and accepts any
-value the delegate recognises (e.g. ECI_EXPERIENCE); prefer the
-choices list to keep the workflow EDU-scoped. Pickable data spaces
-come from `getDataSpaces` (`devName`, matched case-insensitively).
-Single-mapping-per-feature is enforced server-side: create returns
-{status:'400', messageBody:'Duplicate dataSpaceFeatureMapping for
-feature'} if a mapping for the same featureName already exists.
-Both write steps carry in-band {status, messageBody} inside a
-HTTP-200 envelope. Use this SOR (not /ssot/data-space-feature-
-mappings) when the workflow is EDU-scoped — the EDU controller
-adds the duplicate check, multi-feature aggregation, feature
-display-label UDD join, and STUDENT_INSIGHTS product-usage
-telemetry that the bare CDP Connect API doesn't.
-
-## Workflow
-
-Ordering (write path): check-data-space-enabled → get-data-spaces →
-get-data-space-features → create-data-space-feature-mapping → verify
-via get-data-space-features-mapping. Delete path:
-get-data-space-features-mapping (source the mappingId from row.id) →
-delete-data-space-feature-mapping → verify via
-get-data-space-features-mapping. Skip get-data-space-ui-helper when
-driving programmatically — it returns an LWC-only bean handle.
-`feature` on create-data-space-feature-mapping MUST be one of the
-two Education Cloud features returned by get-data-space-features
-(Student Success, Financial Aid) — the create step does not enforce
-this itself, unlike the Setup UI dropdown which only offers those
-two. If asked to map a feature that isn't one of these two, warn
-that it is out of scope for this Education Cloud workflow rather
-than calling create with it. Both write steps carry in-band
-{status, messageBody} inside a HTTP-200 envelope — always inspect
-body.status, not the HTTP code. dataSpace matching is
-case-insensitive. Delete error copy references "featureName" but
-the value passed IS the mappingId.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Org must have Data Cloud (CDP) provisioned and userCanAccessDataCloudAndApp access — the controller's class-level @ServiceComponentAccessGuard rejects unauthorized callers before any method runs. (check: `Data Cloud app access`)
-- At least one Data Space must exist (default or custom) for createDataSpaceFeatureMapping to bind to; getDataSpaces returns the candidate list. Without a provisioned data space, the create call has no valid dataSpace input.
-- Education Cloud licensing/feature must be active in the org — the EDU subset (STUDENT_SUCCESS, FINANCIAL_AID) is only meaningful when those EDU features are licensed; calls succeed structurally but the mapped feature has no consumer otherwise.
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`delete-data-space-feature-mapping`** — Delete one mapping by mappingId (sourced from
-get-data-space-features-mapping[].id). Success→{status:'200',
-messageBody:'DataSpace feature dataSpaceFeatureMapping deleted
-successfully'}. NOT idempotent: re-submitting an already-deleted
-mappingId OR passing an unknown mappingId surfaces {status:'500',
-messageBody:"Error deleting dataspace feature dataSpaceFeatureMapping:
-dataSpace-feature mapping with featureName: <mappingId> doesn't
-exist"} — note the error copy says "featureName:" even though the
-value passed IS the mappingId; that is the CDP delegate's error
-wording and the caller should treat any status:'500' with "doesn't
-exist" as "id already gone".
-AURA-IS-CANONICAL: CDP DELETE /ssot/data-space-feature-mappings/
-{mappingId} bypasses the STUDENT_INSIGHTS telemetry the EDU
-controller emits.
-  - Rollback: No automatic rollback.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `check-data-space-enabled` | read | implemented | `GET /headless/invoke/platform/data-space-feature-mappings` | — |
-| `get-data-spaces` | read | implemented | `GET /headless/invoke/platform/data-space-feature-mappings/get-data-spaces` | `check-data-space-enabled` |
-| `get-data-space-ui-helper` | read | proposed | `GET /headless/invoke/platform/data-space-feature-mappings/get-data-space-uihelper` | — |
-| `get-data-space-features` | read | proposed | `GET /headless/invoke/platform/data-space-feature-mappings/get-data-space-features` | `check-data-space-enabled` |
-| `create-data-space-feature-mapping` | write | proposed | `PATCH /headless/invoke/platform/data-space-feature-mappings/create-data-space-feature-mapping` | `get-data-space-features`, `get-data-spaces` |
-| `get-data-space-features-mapping` | read | proposed | `GET /headless/invoke/platform/data-space-feature-mappings/get-data-space-features-mapping` | `check-data-space-enabled` |
-| `delete-data-space-feature-mapping` | delete | proposed | `DELETE /headless/invoke/platform/data-space-feature-mappings/delete-data-space-feature-mapping` | `get-data-space-features-mapping` |
-
-### Dependency graph
-
-```mermaid
-graph TD
-  check_data_space_enabled["check-data-space-enabled (read)"]
-  get_data_spaces["get-data-spaces (read)"]
-  get_data_space_ui_helper["get-data-space-ui-helper (read)"]
-  get_data_space_features["get-data-space-features (read)"]
-  create_data_space_feature_mapping["create-data-space-feature-mapping (write)"]
-  get_data_space_features_mapping["get-data-space-features-mapping (read)"]
-  delete_data_space_feature_mapping["delete-data-space-feature-mapping (delete)"]
-  check_data_space_enabled --> get_data_spaces
-  check_data_space_enabled --> get_data_space_features
-  get_data_space_features --> create_data_space_feature_mapping
-  get_data_spaces --> create_data_space_feature_mapping
-  check_data_space_enabled --> get_data_space_features_mapping
-  get_data_space_features_mapping --> delete_data_space_feature_mapping
-```
-
-### Read operations
-
-#### `check-data-space-enabled`
-
-Pre-flight boolean: is CDP provisioned AND does the user have access?
-Gate the SOR's write path on this — a false response means the write
-steps will fail. AURA-IS-CANONICAL: no public Connect/Tooling/Metadata
-equivalent returns the composite (hasCDP && userCanAccessDataCloudAndApp)
-boolean; each half is exposed separately but the composite is only
-surfaced by this controller.
-
-**Call:** `GET /headless/invoke/platform/data-space-feature-mappings`   — status: `implemented`
-
-**Output:** true when Data Cloud is provisioned and the calling user has Data Cloud app access; false otherwise. Caller should short-circuit the rest of the SOR on false.
-
-#### `get-data-spaces`
-
-List Data Spaces available to bind a feature to. Use the returned
-`devName` as the `dataSpace` input to create-data-space-feature-mapping.
-dataSpace lookup is CASE-INSENSITIVE at write time (both `"default"` and
-`"Default"` resolve to the same record). AURA-IS-CANONICAL: the public
-Connect grid endpoint returns names only and drops typed fields
-consumers rely on (id, prefix, permSet, isSharingRestricted,
-isPreSelectedSandboxDataspace, status enum).
-
-**Call:** `GET /headless/invoke/platform/data-space-feature-mappings/get-data-spaces`   — status: `implemented`
-
-**Depends on:** `check-data-space-enabled`
-
-**Output:** Array of: {id, devName, name, prefix, createdBy, modifiedDateTime, description, status (ACTIVE|PROCESSING|ERROR), type (DEFAULT|CUSTOM), permSet, definitionId, modifiedByUserName, isSharingRestricted, isPreSelectedSandboxDataspace}. Pass devName as the dataSpace input downstream.
-
-#### `get-data-space-ui-helper`
-
-Agent-skip. Returns an LWC-only Spring bean handle for reflective
-template access — no JSON value pattern an agent can consume.
-AURA-IS-CANONICAL by nature: bean-handle surfaces are not exposed
-via Connect/Tooling/Metadata. Skip when driving the workflow
-programmatically; the step exists only for the LWC's imperative load.
-
-**Call:** `GET /headless/invoke/platform/data-space-feature-mappings/get-data-space-uihelper`   — status: `proposed`
-
-**Output:** A data-space UI bundle exposing the data-space service, packaging data, and the latest datakit deployment status per data space. Not a JSON value object; agents should ignore.
-
-#### `get-data-space-features`
-
-List the EDU-scoped feature CHOICES an admin can bind: {label, value}
-rows filtered to the EDU_DC_FEATURES allowlist (values STUDENT_SUCCESS,
-FINANCIAL_AID; labels from the DataSpaceAwareFeatureType UDD enum). The
-allowlist filter applies HERE at the choices reader — the create path
-itself does NOT re-check the allowlist, so an admin invoking the create
-step with a non-EDU FeatureNameEnum value will succeed structurally.
-Prefer feeding `value` from this response to keep the workflow scoped.
-
-**Call:** `GET /headless/invoke/platform/data-space-feature-mappings/get-data-space-features`   — status: `proposed`
-
-**Depends on:** `check-data-space-enabled`
-
-**Output:** Array of {label: string (display name from UDD enum), value: string (apiValue, one of STUDENT_SUCCESS or FINANCIAL_AID)}. Pass value as the feature input to create-data-space-feature-mapping.
-
-#### `get-data-space-features-mapping`
-
-List existing feature→data-space mappings (flat rows). Controller
-loops FeatureNameEnum values for featureCloud=EducationCloud and joins
-`featureDisplayLabel` from the DataSpaceAwareFeatureType UDD enum;
-the returned rows are whatever mappings exist in CDP for those
-features — including non-EDU-allowlist features an admin (or another
-caller) mapped previously. Each row's `id` IS the CDP mappingId
-consumed by delete-data-space-feature-mapping.
-AURA-IS-CANONICAL: CDP /ssot/data-space-feature-mappings forces N
-round trips (one per featureName) and drops the featureDisplayLabel
-UDD-enum join.
-
-**Call:** `GET /headless/invoke/platform/data-space-feature-mappings/get-data-space-features-mapping`   — status: `proposed`
-
-**Depends on:** `check-data-space-enabled`
-
-**Output:** Array of {id (CDP mappingId for use in delete), featureName (apiValue: STUDENT_SUCCESS|FINANCIAL_AID|other), dataSpace (devName), featureVersion (e.g. '1'), featureDisplayLabel (display name from UDD enum, falls back to featureName when not found)}. Each row is a live mapping; missing features mean no mapping exists for that feature.
-
-### Write operations
-
-#### `create-data-space-feature-mapping`
-
-Bind one feature to one Data Space. `feature` MUST be one of the two
-Education Cloud features: Student Success (STUDENT_SUCCESS) or
-Financial Aid (FINANCIAL_AID) — matches the Setup UI's Feature
-dropdown, which only offers these two by design. Other Salesforce
-clouds have their own features that also technically pass this API,
-but they are NOT part of Education Cloud and will not behave as an
-Education Cloud admin expects. The server does not reject them
-outright: an out-of-scope-but-otherwise-valid feature creates a real
-mapping (silently wrong for this workflow); a truly unrecognized
-value fails with a server error. Always call get-data-space-features
-first and use its response for `feature`; treat any value it didn't
-return as unsuitable for this workflow, and warn rather than proceed
-if an agent is about to pass one.
-
-**Call:** `PATCH /headless/invoke/platform/data-space-feature-mappings/create-data-space-feature-mapping`   — status: `proposed`
-
-**Inputs:**
-
-- `feature` *(`String`)* — Value for the feature field.
-- `dataSpace` *(`String`)* — Value for the data space field.
-
-**Depends on:** `get-data-space-features`, `get-data-spaces`
-
-**Output:** On success: {status:'200', messageBody:'DataSpace feature dataSpaceFeatureMapping created successfully', mappingId: <CDP mappingId for use in delete>}. On duplicate: {status:'400', messageBody:'Duplicate dataSpaceFeatureMapping for feature'}. On other error: {status:'500', messageBody:'Error creating dataspace feature mapping: <cause>'}. Caller MUST check the body's status field — HTTP envelope is always 200.
-
-### Destructive operations
-
-#### `delete-data-space-feature-mapping`
-
-Delete one mapping by mappingId (sourced from
-get-data-space-features-mapping[].id). Success→{status:'200',
-messageBody:'DataSpace feature dataSpaceFeatureMapping deleted
-successfully'}. NOT idempotent: re-submitting an already-deleted
-mappingId OR passing an unknown mappingId surfaces {status:'500',
-messageBody:"Error deleting dataspace feature dataSpaceFeatureMapping:
-dataSpace-feature mapping with featureName: <mappingId> doesn't
-exist"} — note the error copy says "featureName:" even though the
-value passed IS the mappingId; that is the CDP delegate's error
-wording and the caller should treat any status:'500' with "doesn't
-exist" as "id already gone".
-AURA-IS-CANONICAL: CDP DELETE /ssot/data-space-feature-mappings/
-{mappingId} bypasses the STUDENT_INSIGHTS telemetry the EDU
-controller emits.
-
-**Call:** `DELETE /headless/invoke/platform/data-space-feature-mappings/delete-data-space-feature-mapping`   — status: `proposed`
-
-**Inputs:**
-
-- `mappingId` *(`String`)*
-
-**Depends on:** `get-data-space-features-mapping`
-
-**Output:** On success: {status:'200', messageBody:'DataSpace feature dataSpaceFeatureMapping deleted successfully'}. On error: {status:'500', messageBody:'Error deleting dataspace feature dataSpaceFeatureMapping: <cause>'}. HTTP envelope is always 200; check body status.

package/skills/industries-decision-matrix-builder-configure/SKILL.md

@@ -1,78 +0,0 @@
----
-name: industries-decision-matrix-builder-configure
-description: "Use this skill when users want to manage Decision Matrix versions in Industries Business Rules Engine. Trigger when users mention wizard, ui, industries, interaction, decisionmatrix, components."
-metadata:
-  version: "1.0"
----
-
-# Managing Wizard Ui Industries Interaction Decisionmatrix Components
-
-## When to Use This Skill
-
-Manage Decision Matrix versions in Industries Business Rules Engine. This setup wizard allows an admin to activate a decision matrix version, export it as a DMN file, create new versions, and validate column completeness. Use this SOR when a user needs to manage the lifecycle of a Decision Matrix definition — versioning, activation, export, or pre-activation validation.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Industries Cloud / Business Rules Engine licensing must be provisioned on the org — backed by CalculationMatrixStandardEntity / CalculationMatrixVersionStandardEntity (industries.interaction.calculation UDD). (check: `None`)
-- A parent Decision Matrix Definition record (DecisionMatrixDefinition / CalculationMatrix) must already exist before any version-lifecycle step runs; create-new-DM-version, activate, export, and is-missing-columns all take a Decision Matrix Version Id, which presupposes the version (and therefore its parent definition) is present. (check: `None`)
-- For the get-decision-matrix-definition-id step, the calling user must satisfy Decision Matrix user access — the only method-level access guard on this controller. (check: `Decision Matrix user access`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `decision-matrix-version-controller-is-missing-columns-in-d-m` | validate | implemented | `GET /headless/invoke/industries/industries-interaction-decisionmatrix/is-missing-columns-in-dm` | — |
-| `decision-matrix-version-controller-create-new-d-m-version` | write | implemented | `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/create-new-dmversion` | — |
-| `decision-matrix-version-controller-activate-d-m-version` | write | implemented | `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/activate-dmversion` | `decision-matrix-version-controller-is-missing-columns-in-d-m` |
-| `decision-matrix-version-controller-export-as-d-m-n-file` | read | implemented | `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/export-as-dmnfile` | — |
-| `decision-matrix-version-controller-get-decision-matrix-definition-id` | read | implemented | `/headless/invoke/industries/industries-interaction-decisionmatrix/get-decision-matrix-definition-id` | — |
-
-### Read operations
-
-#### `decision-matrix-version-controller-export-as-d-m-n-file`
-
-Serializes the Version to DMN (Decision Model and Notation) XML, delivered via file-download channel; JSON body is empty (void). AURA-IS-CANONICAL: no public DMN-export surface; client-side serialization would push DMN namespace + element-generation rules to the agent.
-
-**Call:** `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/export-as-dmnfile`   — status: `implemented`
-
-#### `decision-matrix-version-controller-get-decision-matrix-definition-id`
-
-Returns the parent DecisionMatrixDefinitionId for a given CalculationMatrix Id via SOQL with system-elevation. Navigation pre-step before listing or creating versions. AURA-IS-CANONICAL: SOQL substitution drops the userHasDecisionMatrixUserAccess guard and the pushFullAccessRights FLS elevation.
-
-**Call:** `/headless/invoke/industries/industries-interaction-decisionmatrix/get-decision-matrix-definition-id`   — status: `implemented`
-
-**Inputs:**
-
-- `decisionMatrixId` *(`string`)* — Id of the Decision Matrix (CalculationMatrix) record to look up; must be a valid entity Id.
-
-**Output:** String. The parent Decision Matrix Definition record Id (15- or 18-character Salesforce Id).
-
-### Write operations
-
-#### `decision-matrix-version-controller-create-new-d-m-version`
-
-Clones a new Version under the same parent Definition as decisionMatrixVersionId; isCarryForward=true copies source rows, false starts empty; versionDetailsMap keys must be in the allowlist or InvalidVersionDetails throws. AURA-IS-CANONICAL: raw sObject INSERT drops carry-forward, the keys allowlist gate, and the per-row error array.
-
-**Call:** `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/create-new-dmversion`   — status: `implemented`
-
-#### `decision-matrix-version-controller-activate-d-m-version`
-
-Promotes the version to active and atomically deactivates the previously-active sibling on the parent Definition. AURA-IS-CANONICAL: raw sObject UPDATE leaves two versions active and breaks BRE evaluation; no Connect/Tooling activate primitive exists.
-
-**Call:** `PATCH /headless/invoke/industries/industries-interaction-decisionmatrix/activate-dmversion`   — status: `implemented`
-
-**Depends on:** `decision-matrix-version-controller-is-missing-columns-in-d-m`
-
-### Other operations
-
-#### `decision-matrix-version-controller-is-missing-columns-in-d-m`
-
-Returns true when the version is missing required columns vs its parent Definition's schema; gates activation. AURA-IS-CANONICAL: no public surface for the version-vs-definition column-schema diff that Decision Matrix Column Check owns.
-
-**Call:** `GET /headless/invoke/industries/industries-interaction-decisionmatrix/is-missing-columns-in-dm`   — status: `implemented`

package/skills/industries-decision-table-hbase-configure/SKILL.md

@@ -1,87 +0,0 @@
----
-name: industries-decision-table-hbase-configure
-description: "Use this skill when users want to use this composite when a CME/Industries skill needs to activate a source-object Decision Table headlessly (e.g. Trigger when users mention decision, table, hbase, activate, tables, decision tables."
-metadata:
-  version: "1.0"
-  accessCheck: "UserPermissions.BREDecisionTableAdmin"
----
-
-# Managing Decision Table Hbase Activate
-
-## When to Use This Skill
-
-Use this composite when a CME/Industries skill needs to activate a source-object Decision Table headlessly (e.g. AttributeDetailsConfigDT, AttributePicklistConfigDT). NOT for CSV/versioned DTs — use `decision-table-rows-load` instead.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User must have BREDecisionTableAdmin permission (check: `UserPermissions.BREDecisionTableAdmin`)
-- Org must have BusinessRulesEngine feature enabled
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `clone-template` | write | implemented | `POST /connect/business-rules/decision-table/templates/instantiate` | — |
-| `get-current-definition` | read | implemented | `GET /connect/business-rules/decision-table/definitions/{decisionTableId}` | `clone-template` |
-| `activate-definition` | write | implemented | `PATCH /connect/business-rules/decision-table/definitions/{decisionTableId}` | `get-current-definition` |
-| `refresh-cache` | write | implemented | `POST /connect/decision-table/refresh` | `activate-definition` |
-
-### Read operations
-
-#### `get-current-definition`
-
-Read the full DT definition to preserve every required field for the subsequent full-body PATCH. Partial PATCH fails with "Required field is missing: fullName / sourceObject".
-
-**Call:** `GET /connect/business-rules/decision-table/definitions/{decisionTableId}`   — status: `implemented`
-
-**Inputs:**
-
-- `decisionTableId` — From clone-template output
-
-**Depends on:** `clone-template`
-
-### Write operations
-
-#### `clone-template`
-
-Instantiate the HBASE DecisionTable from the template. The template's auto-populate query pulls rows directly from the source SObject — no admin row input required. Request-body field for the new DT's developer name is `decisionTableName` (NOT `apiName`) — POST fails JSON_PARSER_ERROR on `apiName`. Same wire-body key as the CSV versioned instantiate call.
-
-**Call:** `POST /connect/business-rules/decision-table/templates/instantiate`   — status: `implemented`
-
-**Inputs:**
-
-- `templateName` — templateName input to this composite
-- `decisionTableName` — Wired from this composite's `apiName` input — the request-body key is `decisionTableName`.
-
-#### `activate-definition`
-
-Mutate the returned definition map — set `status = "Active"` — and PATCH the whole map back. Body MUST include ALL of setupName, fullName, sourceObject, sourceType, type, usageType, executionType, conditionCriteria, conditionType, decisionResultPolicy, collectOperator, rowLevelOverrideType, doesConsiderNullValue, isIncrementalSyncEnabled, status, description.
-
-**Call:** `PATCH /connect/business-rules/decision-table/definitions/{decisionTableId}`   — status: `implemented`
-
-**Inputs:**
-
-- `decisionTableId` — From clone-template output
-- `body` — get-current-definition.definition with status overridden to "Active". Do NOT partial-PATCH.
-
-**Depends on:** `get-current-definition`
-
-**Rollback:** DELETE /connect/business-rules/decision-table/definitions/{decisionTableId} removes the DT. Use with care.
-
-#### `refresh-cache`
-
-Refresh the DT cache. `postDecisionTableRefresh` returns `Queued`; poll `DecisionTable.RefreshStatus` until it reads `Completed`. HBASE DTs return `versions: []` in the refresh response — this is the EXPECTED Completed shape (versions endpoint doesn't apply). Do NOT assert `versions[*].refreshStatus == Completed`.
-
-**Call:** `POST /connect/decision-table/refresh`   — status: `implemented`
-
-**Inputs:**
-
-- `decisionTableId` — From clone-template output
-
-**Depends on:** `activate-definition`

package/skills/industries-decision-table-version-configure/SKILL.md

@@ -1,74 +0,0 @@
----
-name: industries-decision-table-version-configure
-description: "Use this skill when users want to use this composite when a skill needs a CSV/versioned Decision Table cloned from a template with its initial version activated but NO rows loaded — e.g. Trigger when users mention decision, table, version, activate, tables, decision tables."
-metadata:
-  version: "1.0"
-  accessCheck: "UserPermissions.BREDecisionTableAdmin"
----
-
-# Managing Decision Table Version Activate
-
-## When to Use This Skill
-
-Use this composite when a skill needs a CSV/versioned Decision Table cloned from a template with its initial version activated but NO rows loaded — e.g. the Tariff Comparison feature-setup path that only asks "create the DTs from the templates". NOT for source-object (HBASE) DTs (use `decision-table-hbase-activate`) and NOT for cases where rows are required at setup time (use `decision-table-rows-load`).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User must have BREDecisionTableAdmin permission (check: `UserPermissions.BREDecisionTableAdmin`)
-- Org must have BusinessRulesEngine feature enabled
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `clone-template` | write | implemented | `POST /connect/business-rules/decision-table/templates/instantiate` | — |
-| `activate-version` | write | implemented | `PATCH /connect/business-rules/decision-table/definitions/{decisionTableId}/versions/{versionNumber}` | `clone-template` |
-| `refresh-cache` | write | implemented | `POST /connect/decision-table/refresh` | `activate-version` |
-
-### Write operations
-
-#### `clone-template`
-
-Instantiate a new DecisionTable from the namespace-qualified template. Application Usage defaults to `Default`. Template instantiation automatically creates an initial ExpressionSetVersion (versionNumber 1) in `Draft` status with the template's column definitions but zero rows. Request-body field for the new DT's developer name is `decisionTableName` (NOT `apiName`) — POST fails JSON_PARSER_ERROR on `apiName`.
-
-**Call:** `POST /connect/business-rules/decision-table/templates/instantiate`   — status: `implemented`
-
-**Inputs:**
-
-- `templateName` — templateName input to this composite
-- `decisionTableName` — Wired from this composite's `apiName` input — the request-body key is `decisionTableName`.
-
-**Rollback:** DELETE /connect/business-rules/decision-table/definitions/{decisionTableId} removes the DT and its version. Use with care.
-
-#### `activate-version`
-
-Activate the initial version (versionStatus = Active) with no row load. The DT is queryable and returns zero rows until a downstream flow loads them via `postDecisionTableRows`. Activation on an empty version is accepted — the endpoint does NOT require a minimum row count. Use the version-scoped URI (`.../versions/{versionNumber}`) — the collection URI (`.../versions`) rejects the update with MISSING_ARGUMENT because it expects a full definition body.
-
-**Call:** `PATCH /connect/business-rules/decision-table/definitions/{decisionTableId}/versions/{versionNumber}`   — status: `implemented`
-
-**Inputs:**
-
-- `decisionTableId` — From clone-template output
-- `versionNumber` — versionNumber input to this composite
-- `versionStatus`
-
-**Depends on:** `clone-template`
-
-#### `refresh-cache`
-
-Refresh the DT cache so the activated (empty) version is served by the runtime. `postDecisionTableRefresh` returns `Queued`; poll `DecisionTable.RefreshStatus` until it reads `Completed`.
-
-**Call:** `POST /connect/decision-table/refresh`   — status: `implemented`
-
-**Inputs:**
-
-- `decisionTableId` — From clone-template output
-- `versionNumber` — versionNumber input to this composite
-
-**Depends on:** `activate-version`