@salesforce/afv-skills 1.65.0 → 1.65.1

package/skills/data360-experiment-create/SKILL.md

@@ -1,82 +0,0 @@
----
-name: data360-experiment-create
-description: "Use this skill when users want to execute Data Cloud IExperimentService operations via the Data 360 MCP facade. Trigger when users mention data360/experiment, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/experiment
-
-## When to Use This Skill
-
-Execute Data Cloud IExperimentService operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Critical Constraints
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`personalization-setup-experiment-delete`** — Delete an A/B/n experiment by its ID or name.
-  - 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 |
-|-----------|---------|--------|------|------------|
-| `personalization-setup-experiment-create` | write | implemented | `execute_personalization-setup-experiment-create` | — |
-| `personalization-setup-experiment-delete` | delete | implemented | `execute_personalization-setup-experiment-delete` | — |
-| `personalization-setup-experiment-get` | read | implemented | `execute_personalization-setup-experiment-get` | — |
-| `personalization-setup-experiment-update` | write | implemented | `execute_personalization-setup-experiment-update` | — |
-
-### Read operations
-
-#### `personalization-setup-experiment-get`
-
-Get a specific A/B/n experiment by its ID or name. Returns the full experiment definition 
-
-**Call:** `execute_personalization-setup-experiment-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_personalization_setup_experiment_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_personalization-setup-experiment-get) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `personalization-setup-experiment-create`
-
-Create a new A/B/n experiment for personalization. Specify cohorts with allocation weights, 
-
-**Call:** `execute_personalization-setup-experiment-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_personalization_setup_experiment_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_personalization-setup-experiment-create) for the param schema and, where available, a worked example.
-
-#### `personalization-setup-experiment-update`
-
-Update an A/B/n experiment by its ID or name. Use the action parameter to perform a 
-
-**Call:** `execute_personalization-setup-experiment-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_personalization_setup_experiment_update (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_personalization-setup-experiment-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `personalization-setup-experiment-delete`
-
-Delete an A/B/n experiment by its ID or name.
-
-**Call:** `execute_personalization-setup-experiment-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_personalization_setup_experiment_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_personalization-setup-experiment-delete) for the param schema and, where available, a worked example.

package/skills/data360-goal-based-campaign-create/SKILL.md

@@ -1,192 +0,0 @@
----
-name: data360-goal-based-campaign-create
-description: "Use this skill when users want to execute Data Cloud GoalBasedCampaign operations via the Data 360 MCP facade. Trigger when users mention data360/goal, based, campaign, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/goal Based Campaign
-
-## When to Use This Skill
-
-Execute Data Cloud GoalBasedCampaign operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Critical Constraints
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`mes-campaign-delete`** — Delete an MES campaign by ID.
-  - 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 |
-|-----------|---------|--------|------|------------|
-| `mes-campaign-activate` | write | implemented | `execute_mes-campaign-activate` | — |
-| `mes-campaign-analytics-metadata` | read | implemented | `execute_mes-campaign-analytics-metadata` | — |
-| `mes-campaign-approve` | write | implemented | `execute_mes-campaign-approve` | — |
-| `mes-campaign-baselines` | read | implemented | `execute_mes-campaign-baselines` | — |
-| `mes-campaign-create` | write | implemented | `execute_mes-campaign-create` | — |
-| `mes-campaign-delete` | delete | implemented | `execute_mes-campaign-delete` | — |
-| `mes-campaign-get` | read | implemented | `execute_mes-campaign-get` | — |
-| `mes-campaign-list` | read | implemented | `execute_mes-campaign-list` | — |
-| `mes-campaign-plan` | write | implemented | `execute_mes-campaign-plan` | — |
-| `mes-campaign-plan-save` | write | implemented | `execute_mes-campaign-plan-save` | — |
-| `mes-campaign-prune-arm` | write | implemented | `execute_mes-campaign-prune-arm` | — |
-| `mes-campaign-revise` | write | implemented | `execute_mes-campaign-revise` | — |
-| `mes-campaign-segments` | read | implemented | `execute_mes-campaign-segments` | — |
-| `mes-campaign-summary` | read | implemented | `execute_mes-campaign-summary` | — |
-
-### Read operations
-
-#### `mes-campaign-analytics-metadata`
-
-Get campaign metadata and analytics configuration for the MES attribution card, including name, dates, budget, goal, semantic model ID, and data space.
-
-**Call:** `execute_mes-campaign-analytics-metadata`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_analytics_metadata (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-analytics-metadata) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-baselines`
-
-Get email and SMS click-through-rate baselines for an MES campaign, computed from the last 30 days (excluding today). Pass the campaignId, semanticModelId, and dataSpaceApiName from the analytics-metadata response.
-
-**Call:** `execute_mes-campaign-baselines`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_baselines (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-baselines) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-get`
-
-Get an MES campaign by ID. Use to poll for plan generation status after creating or revising a plan.
-
-**Call:** `execute_mes-campaign-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-get) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-list`
-
-List all MES marketing expert campaigns in the current org.
-
-**Call:** `execute_mes-campaign-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-list) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-segments`
-
-List active segments eligible for an MES campaign in a data space, filtered to the configured PersonalizationDataGraph's root DMO when available.
-
-**Call:** `execute_mes-campaign-segments`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_segments (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-segments) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-summary`
-
-Get a natural-language performance summary for an MES campaign, including overall performance, key trends, risks, and opportunities.
-
-**Call:** `execute_mes-campaign-summary`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_summary (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-summary) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `mes-campaign-activate`
-
-Activate an approved MES campaign — creates and activates the operational campaign and flows. Returns immediately with Processing status; poll d360_mes_campaign_get for completion.
-
-**Call:** `execute_mes-campaign-activate`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_activate (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-activate) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-approve`
-
-Send an MES campaign plan for approval. Campaign must be in PlanReady state.
-
-**Call:** `execute_mes-campaign-approve`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_approve (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-approve) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-create`
-
-Create a new MES marketing expert campaign with a name, business unit, and optional description.
-
-**Call:** `execute_mes-campaign-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-create) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-plan`
-
-Create a new execution plan for an MES campaign from the provided change intent and channels. Returns immediately with GeneratingPlan status; poll d360_mes_campaign_get for completion.
-
-**Call:** `execute_mes-campaign-plan`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_plan (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-plan) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-plan-save`
-
-Save wizard inputs onto an MES campaign's existing plan without triggering LLM regeneration. Status is unchanged and no new plan is created. Only valid before the campaign has been revised; use d360_mes_campaign_revise to change a plan with natural-language intent.
-
-**Call:** `execute_mes-campaign-plan-save`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_plan_save (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-plan-save) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-prune-arm`
-
-Prune an underperforming campaign arm by setting its allocation to zero and redistributing weight to remaining arms.
-
-**Call:** `execute_mes-campaign-prune-arm`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_prune_arm (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-prune-arm) for the param schema and, where available, a worked example.
-
-#### `mes-campaign-revise`
-
-Revise an existing MES campaign plan via natural-language input. Updates audience, channels, budget, content, duration, or goal. Returns immediately with Processing status; poll d360_mes_campaign_get for completion.
-
-**Call:** `execute_mes-campaign-revise`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_revise (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-revise) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `mes-campaign-delete`
-
-Delete an MES campaign by ID.
-
-**Call:** `execute_mes-campaign-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_mes_campaign_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_mes-campaign-delete) for the param schema and, where available, a worked example.

package/skills/data360-harmonization-process-history-get/SKILL.md

@@ -1,38 +0,0 @@
----
-name: data360-harmonization-process-history-get
-description: "Use this skill when users want to execute Data Cloud HarmonizationProcessHistory operations via the Data 360 MCP facade. Trigger when users mention data360/harmonization, process, history, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Querying Data360/harmonization Process History
-
-## When to Use This Skill
-
-Execute Data Cloud HarmonizationProcessHistory operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `ek-harmonization-status` | read | implemented | `execute_ek-harmonization-status` | — |
-
-### Read operations
-
-#### `ek-harmonization-status`
-
-poll harmonization process history/status to a terminal state.
-
-**Call:** `execute_ek-harmonization-status`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ek_harmonization_status (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ek-harmonization-status) for the param schema and, where available, a worked example.

package/skills/data360-harmonized-unstructured-dmo-create/SKILL.md

@@ -1,84 +0,0 @@
----
-name: data360-harmonized-unstructured-dmo-create
-description: "Use this skill when users want to execute Data Cloud HarmonizedUnstructuredDmo operations via the Data 360 MCP facade. Trigger when users mention data360/harmonized, unstructured, dmo, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/harmonized Unstructured Dmo
-
-## When to Use This Skill
-
-Execute Data Cloud HarmonizedUnstructuredDmo operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `ek-harmonization-config-create` | write | implemented | `execute_ek-harmonization-config-create` | — |
-| `ek-harmonization-config-list` | read | implemented | `execute_ek-harmonization-config-list` | — |
-| `ek-harmonization-trigger` | write | implemented | `execute_ek-harmonization-trigger` | — |
-| `ek-harmonized-content-get` | read | implemented | `execute_ek-harmonized-content-get` | — |
-| `ek-knowledge-harmonization-config-create` | write | implemented | `execute_ek-knowledge-harmonization-config-create` | — |
-
-### Read operations
-
-#### `ek-harmonization-config-list`
-
-lists all unstructured harmonization configs (HUDMOs) in the org; use to discover configApiName/processingId to feed d360_ek_harmonization_status or d360_ek_harmonization_trigger.
-
-**Call:** `execute_ek-harmonization-config-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ek_harmonization_config_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ek-harmonization-config-list) for the param schema and, where available, a worked example.
-
-#### `ek-harmonized-content-get`
-
-fetch harmonized unstructured DMO (HUDMO) content for a record by hudmoName + recordId.
-
-**Call:** `execute_ek-harmonized-content-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ek_harmonized_content_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ek-harmonized-content-get) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `ek-harmonization-config-create`
-
-creates the unstructured harmonization config (HUDLO+HUDMO) and runs harmonization synchronously; on completion poll d360_ek_harmonization_status by configApiName/processingId — do NOT retry create.
-
-**Call:** `execute_ek-harmonization-config-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ek_harmonization_config_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ek-harmonization-config-create) for the param schema and, where available, a worked example.
-
-#### `ek-harmonization-trigger`
-
-RECOVERY ONLY — re-trigger harmonization for an existing config; not a normal forward step.
-
-**Call:** `execute_ek-harmonization-trigger`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ek_harmonization_trigger (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ek-harmonization-trigger) for the param schema and, where available, a worked example.
-
-#### `ek-knowledge-harmonization-config-create`
-
-creates the structured Knowledge Article harmonization config (HDLO+HDMO, optional attachment DLO/DMO) and runs harmonization synchronously; on completion poll d360_ek_harmonization_status by configApiName/processingId — do NOT retry create.
-
-**Call:** `execute_ek-knowledge-harmonization-config-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ek_knowledge_harmonization_config_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ek-knowledge-harmonization-config-create) for the param schema and, where available, a worked example.

package/skills/data360-identity-resolution-create/SKILL.md

@@ -1,115 +0,0 @@
----
-name: data360-identity-resolution-create
-description: "Use this skill when users want to execute Data Cloud IdentityResolution operations via the Data 360 MCP facade. Trigger when users mention data360/identity, resolution, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/identity Resolution
-
-## When to Use This Skill
-
-Execute Data Cloud IdentityResolution operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Critical Constraints
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`ir-delete`** — Delete an identity resolution ruleset by id. Existing unified profiles remain until the unification DMO is also removed.
-  - 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 |
-|-----------|---------|--------|------|------------|
-| `ir-create` | write | implemented | `execute_ir-create` | — |
-| `ir-delete` | delete | implemented | `execute_ir-delete` | — |
-| `ir-get` | read | implemented | `execute_ir-get` | — |
-| `ir-list` | read | implemented | `execute_ir-list` | — |
-| `ir-publish` | write | implemented | `execute_ir-publish` | — |
-| `ir-run` | write | implemented | `execute_ir-run` | — |
-| `ir-update` | write | implemented | `execute_ir-update` | — |
-
-### Read operations
-
-#### `ir-get`
-
-Get a specific identity resolution ruleset by id. Returns full match rules, source DMOs, and unification target.
-
-**Call:** `execute_ir-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ir_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ir-get) for the param schema and, where available, a worked example.
-
-#### `ir-list`
-
-List all identity resolution rulesets configured in the org. Use d360_ir_get to fetch a specific one by id.
-
-**Call:** `execute_ir-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ir_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ir-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `ir-create`
-
-Create a new identity resolution ruleset. Specify match rules, source DMOs, and unification target DMO. Use d360_ir_publish followed by d360_ir_run to materialize unified profiles.
-
-**Call:** `execute_ir-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ir_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ir-create) for the param schema and, where available, a worked example.
-
-#### `ir-publish`
-
-Publish an identity resolution ruleset by id. Promotes the draft to active so it can be executed via d360_ir_run.
-
-**Call:** `execute_ir-publish`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ir_publish (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ir-publish) for the param schema and, where available, a worked example.
-
-#### `ir-run`
-
-Trigger an on-demand run of a published identity resolution ruleset by id. Materializes unified profile records into the unification target DMO.
-
-**Call:** `execute_ir-run`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ir_run (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ir-run) for the param schema and, where available, a worked example.
-
-#### `ir-update`
-
-Update an existing identity resolution ruleset by id. Use to modify match rules, source DMOs, or unification target. Republish (d360_ir_publish) and rerun (d360_ir_run) to materialize changes.
-
-**Call:** `execute_ir-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ir_update (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ir-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `ir-delete`
-
-Delete an identity resolution ruleset by id. Existing unified profiles remain until the unification DMO is also removed.
-
-**Call:** `execute_ir-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ir_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ir-delete) for the param schema and, where available, a worked example.