@salesforce/afv-skills 1.55.0 → 1.56.0

package/skills/sales-call-scoring-configure/scripts/toggle-competency.sh

@@ -0,0 +1,112 @@
+#!/bin/bash
+
+# Activate or deactivate a Coaching Competency by DeveloperName or Id.
+# Toggles IsActive via Tooling API PATCH.
+#
+# Deactivation preserves historical EnablementCompetencyEval scores (per the
+# entity XML comment on IsActive).
+#
+# Usage: ./toggle-competency.sh <org-alias> <name-or-id> <activate|deactivate>
+
+set -euo pipefail
+
+export NO_COLOR=1
+export FORCE_COLOR=0
+
+ORG_ALIAS="${1:-}"
+IDENT="${2:-}"
+ACTION="${3:-}"
+
+if [[ -z "$ORG_ALIAS" || -z "$IDENT" || -z "$ACTION" ]]; then
+  echo "Usage: $0 <org-alias> <name-or-id> <activate|deactivate>"
+  exit 1
+fi
+
+if [[ "$ACTION" != "activate" && "$ACTION" != "deactivate" ]]; then
+  echo "Action must be 'activate' or 'deactivate'"
+  exit 1
+fi
+
+TARGET=$([[ "$ACTION" == "activate" ]] && echo "true" || echo "false")
+
+# ---------------------------------------------------------------------------
+# Auth
+# ---------------------------------------------------------------------------
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+# shellcheck source=shared/auth.sh
+source "$SCRIPT_DIR/shared/auth.sh"
+# shellcheck source=shared/soql.sh
+source "$SCRIPT_DIR/shared/soql.sh"
+
+resolve_org_auth "$ORG_ALIAS" || exit 1
+
+TOOLING_BASE="services/data/v68.0/tooling"
+
+# ---------------------------------------------------------------------------
+# Resolve identifier → Id + current state
+# ---------------------------------------------------------------------------
+# Ids start with 1nA (keyPrefix). Anything else is treated as DeveloperName or MasterLabel.
+if [[ "$IDENT" =~ ^1nA[0-9a-zA-Z]{12,15}$ ]]; then
+  WHERE="Id='${IDENT}'"
+else
+  SAFE=$(soql_escape "$IDENT")
+  WHERE="DeveloperName='${SAFE}' OR MasterLabel='${SAFE}'"
+fi
+
+QUERY="SELECT+Id,MasterLabel,IsActive+FROM+EnablementCompetencyDef+WHERE+$(printf '%s' "$WHERE" | jq -sRr @uri)"
+LOOKUP=$(sf api request rest "${TOOLING_BASE}/query/?q=${QUERY}" --target-org "$ORG_ALIAS" 2>/dev/null) || true
+
+RECORD_COUNT=$(echo "$LOOKUP" | jq -r '.totalSize // 0')
+if [[ "$RECORD_COUNT" == "0" ]]; then
+  echo "No competency found matching: $IDENT"
+  exit 1
+fi
+if [[ "$RECORD_COUNT" != "1" ]]; then
+  echo "Multiple competencies matched '$IDENT' — refusing to bulk-toggle."
+  echo "$LOOKUP" | jq -r '.records[] | "   \(.Id)  \(.MasterLabel)"'
+  exit 1
+fi
+
+REC_ID=$(echo "$LOOKUP" | jq -r '.records[0].Id')
+REC_LABEL=$(echo "$LOOKUP" | jq -r '.records[0].MasterLabel')
+REC_STATE=$(echo "$LOOKUP" | jq -r '.records[0].IsActive')
+
+echo "$REC_LABEL ($REC_ID) — currently IsActive=$REC_STATE"
+
+# Idempotency
+if [[ "$REC_STATE" == "$TARGET" ]]; then
+  echo "Already $ACTION'd — no-op."
+  exit 0
+fi
+
+# Enforce 8-active cap when activating.
+if [[ "$ACTION" == "activate" ]]; then
+  ACTIVE_COUNT=$( (sf api request rest \
+    "${TOOLING_BASE}/query/?q=SELECT+COUNT()+FROM+EnablementCompetencyDef+WHERE+IsActive=true" \
+    --target-org "$ORG_ALIAS" 2>/dev/null || true) | jq -r '.totalSize // 0' 2>/dev/null)
+  ACTIVE_COUNT="${ACTIVE_COUNT:-0}"
+  if [[ "$ACTIVE_COUNT" -ge 8 ]]; then
+    echo "Cannot activate: org already has $ACTIVE_COUNT active competencies (max 8)."
+    echo "   Deactivate one first, then retry."
+    exit 1
+  fi
+fi
+
+# ---------------------------------------------------------------------------
+# PATCH
+# ---------------------------------------------------------------------------
+PAYLOAD=$(jq -n --argjson v "$TARGET" '{IsActive: $v}')
+
+if RESP_BODY=$(sf api request rest "${TOOLING_BASE}/sobjects/EnablementCompetencyDef/${REC_ID}" \
+  --target-org "$ORG_ALIAS" \
+  --method PATCH \
+  --header 'Content-Type: application/json' \
+  --body "$PAYLOAD" \
+  2>/dev/null); then
+  echo "${ACTION}d $REC_LABEL — IsActive now $TARGET"
+  exit 0
+else
+  echo "Error: PATCH failed"
+  echo "   $RESP_BODY"
+  exit 1
+fi

package/skills/sales-call-scoring-configure/scripts/toggle-custom-competency.sh

@@ -0,0 +1,125 @@
+#!/bin/bash
+# sales_call_scoring: story="custom-competency-crud" owner="W-CUSTOM-CRUD"
+#
+# Activate or deactivate a Coaching Competency by DeveloperName or Id.
+# Toggles IsActive via Tooling API PATCH.
+#
+# Deactivation preserves historical EnablementCompetencyEval scores (per the
+# entity XML comment on IsActive) so a rehired competency picks up its
+# existing evaluation history.
+#
+# Companion of create-custom-competency.sh — parallel to toggle-competency.sh
+# so the custom-CRUD story can iterate the activate/deactivate surface
+# independently.
+#
+# Usage: ./toggle-custom-competency.sh <org-alias> <name-or-id> <activate|deactivate>
+
+set -euo pipefail
+
+export NO_COLOR=1
+export FORCE_COLOR=0
+
+ORG_ALIAS="${1:-}"
+IDENT="${2:-}"
+ACTION="${3:-}"
+
+if [[ -z "$ORG_ALIAS" || -z "$IDENT" || -z "$ACTION" ]]; then
+  echo "Usage: $0 <org-alias> <name-or-id> <activate|deactivate>"
+  exit 1
+fi
+
+if [[ "$ACTION" != "activate" && "$ACTION" != "deactivate" ]]; then
+  echo "Action must be 'activate' or 'deactivate'"
+  exit 1
+fi
+
+TARGET=$([[ "$ACTION" == "activate" ]] && echo "true" || echo "false")
+
+# ---------------------------------------------------------------------------
+# Auth
+# ---------------------------------------------------------------------------
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+# shellcheck source=shared/auth.sh
+source "$SCRIPT_DIR/shared/auth.sh"
+# shellcheck source=shared/soql.sh
+source "$SCRIPT_DIR/shared/soql.sh"
+
+resolve_org_auth "$ORG_ALIAS" || exit 1
+
+TOOLING_BASE="services/data/v68.0/tooling"
+
+# ---------------------------------------------------------------------------
+# Resolve identifier
+# ---------------------------------------------------------------------------
+if [[ "$IDENT" =~ ^1nA[0-9a-zA-Z]{12,15}$ ]]; then
+  WHERE="Id='${IDENT}'"
+else
+  SAFE=$(soql_escape "$IDENT")
+  WHERE="DeveloperName='${SAFE}' OR MasterLabel='${SAFE}'"
+fi
+
+QUERY="SELECT+Id,MasterLabel,IsActive+FROM+EnablementCompetencyDef+WHERE+$(printf '%s' "$WHERE" | jq -sRr @uri)"
+LOOKUP=$(sf api request rest "${TOOLING_BASE}/query/?q=${QUERY}" --target-org "$ORG_ALIAS" 2>/dev/null || true)
+
+RECORD_COUNT=$(echo "$LOOKUP" | jq -r '.totalSize // 0' 2>/dev/null || echo "0")
+if [[ "$RECORD_COUNT" == "0" ]]; then
+  echo "No competency found matching: $IDENT"
+  exit 1
+fi
+if [[ "$RECORD_COUNT" != "1" ]]; then
+  echo "Multiple competencies matched '$IDENT' — refusing to bulk-toggle."
+  echo "$LOOKUP" | jq -r '.records[] | "   \(.Id)  \(.MasterLabel)"'
+  exit 1
+fi
+
+REC_ID=$(echo "$LOOKUP" | jq -r '.records[0].Id')
+REC_LABEL=$(echo "$LOOKUP" | jq -r '.records[0].MasterLabel')
+REC_STATE=$(echo "$LOOKUP" | jq -r '.records[0].IsActive')
+
+echo "$REC_LABEL ($REC_ID) — currently IsActive=$REC_STATE"
+
+# Idempotency
+if [[ "$REC_STATE" == "$TARGET" ]]; then
+  echo "Already $ACTION'd — no-op."
+  exit 0
+fi
+
+# Enforce 8-active cap when activating. Refuse with a rich report — the
+# activate path can't auto-fallback because "activate to inactive" is a
+# no-op; the admin must actively free a slot.
+if [[ "$ACTION" == "activate" ]]; then
+  # shellcheck source=shared/cap.sh
+  source "$SCRIPT_DIR/shared/cap.sh"
+
+  ACTIVE_COUNT=$(query_active_count "$ORG_ALIAS")
+  if [[ "$ACTIVE_COUNT" -ge "$MAX_ACTIVE_COMPETENCIES" ]]; then
+    echo "Cannot activate '$REC_LABEL' — org is at the 8-active competency cap."
+    print_cap_report "$ORG_ALIAS" "activating '$REC_LABEL'"
+    echo "    Once a slot is free, retry:"
+    echo ""
+    echo "      $0 $ORG_ALIAS $REC_ID activate"
+    echo ""
+    exit 1
+  fi
+fi
+
+# ---------------------------------------------------------------------------
+# PATCH
+# ---------------------------------------------------------------------------
+PAYLOAD=$(jq -n --argjson v "$TARGET" '{IsActive: $v}')
+
+# sf api request rest exits non-zero on HTTP failure; success on Tooling
+# PATCH is HTTP 204 (empty body). Capture both stdout and exit status.
+if RESP_BODY=$(sf api request rest "${TOOLING_BASE}/sobjects/EnablementCompetencyDef/${REC_ID}" \
+    --target-org "$ORG_ALIAS" \
+    --method PATCH \
+    --header 'Content-Type: application/json' \
+    --body "$PAYLOAD" \
+    2>&1); then
+  echo "${ACTION}d $REC_LABEL — IsActive now $TARGET"
+  exit 0
+else
+  echo "Error: PATCH failed"
+  echo "   $RESP_BODY"
+  exit 1
+fi

package/skills/sales-call-scoring-configure/scripts/verify-ootb-competencies.sh

@@ -0,0 +1,116 @@
+#!/bin/bash
+
+# Verify that a set of expected Coaching Competencies exist and are active,
+# displaying each one's name + EvaluationInstructions in a markdown table so
+# the admin can review what's actually configured. Defaults to the 6 OOTB
+# competencies (assets/ootb-competencies.json); pass explicit names to verify
+# a custom subset instead (e.g. after the admin chose only some of the OOTB
+# set, or created custom competencies).
+#
+# Exit 0 only if every expected name exists AND is active. Exit 1 otherwise,
+# listing what's missing or inactive.
+#
+# Usage:
+#   ./verify-ootb-competencies.sh <org-alias>                       # verify full OOTB set
+#   ./verify-ootb-competencies.sh <org-alias> "Name One" "Name Two" # verify specific names
+
+set -euo pipefail
+
+export NO_COLOR=1
+export FORCE_COLOR=0
+
+ORG_ALIAS="${1:-}"
+shift || true
+
+if [[ -z "$ORG_ALIAS" ]]; then
+  echo "Error: Missing org alias"
+  echo "Usage: $0 <org-alias> [\"Competency Name\" ...]"
+  exit 1
+fi
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+ASSETS_FILE="$SCRIPT_DIR/../assets/ootb-competencies.json"
+
+# ---------------------------------------------------------------------------
+# Expected names: caller-supplied args, else the full OOTB set.
+# ---------------------------------------------------------------------------
+EXPECTED_NAMES=()
+if [[ "$#" -gt 0 ]]; then
+  EXPECTED_NAMES=("$@")
+else
+  if [[ ! -f "$ASSETS_FILE" ]]; then
+    echo "Cannot find $ASSETS_FILE"
+    exit 1
+  fi
+  while IFS= read -r name; do
+    EXPECTED_NAMES+=("$name")
+  done < <(jq -r '.competencies[].MasterLabel' "$ASSETS_FILE")
+fi
+
+echo "Verifying Coaching Competencies on org: $ORG_ALIAS"
+echo ""
+echo "   Expecting ${#EXPECTED_NAMES[@]} competenc$([[ ${#EXPECTED_NAMES[@]} == 1 ]] && echo "y" || echo "ies"):"
+for n in "${EXPECTED_NAMES[@]}"; do
+  echo "     - $n"
+done
+echo ""
+
+# ---------------------------------------------------------------------------
+# Fetch all existing competencies once, then check expected names against them.
+# Auth is handled internally by `sf api request rest` (no token extraction).
+# ---------------------------------------------------------------------------
+EXISTING_RAW=$(sf api request rest \
+  "services/data/v68.0/tooling/query/?q=SELECT+Id,DeveloperName,MasterLabel,Description,EvaluationInstructions,IsActive,EvaluationScope,SourceCompetencyTemplate+FROM+EnablementCompetencyDef" \
+  --target-org "$ORG_ALIAS" 2>/dev/null)
+
+if ! echo "$EXISTING_RAW" | jq -e 'has("records")' >/dev/null 2>&1; then
+  echo "Error: Tooling API query failed. Is the org authenticated?"
+  echo "$EXISTING_RAW" | jq -r '.[0].message // .message // .' 2>/dev/null || echo "$EXISTING_RAW"
+  exit 1
+fi
+
+MISSING=()
+INACTIVE=()
+OK=()
+ROWS=()
+
+for NAME in "${EXPECTED_NAMES[@]}"; do
+  MATCH=$(echo "$EXISTING_RAW" | jq -c --arg n "$NAME" '.records[] | select(.MasterLabel == $n)' | head -1)
+
+  if [[ -z "$MATCH" ]]; then
+    MISSING+=("$NAME")
+    ROWS+=("missing | $NAME | _not found on this org_")
+    continue
+  fi
+
+  IS_ACTIVE=$(echo "$MATCH" | jq -r '.IsActive')
+  INSTRUCTIONS=$(echo "$MATCH" | jq -r '.EvaluationInstructions // "(none)"' | tr '\n' ' ' | sed 's/|/\\|/g')
+
+  if [[ "$IS_ACTIVE" == "true" ]]; then
+    OK+=("$NAME")
+    STATUS_ICON="OK"
+  else
+    INACTIVE+=("$NAME")
+    STATUS_ICON="--"
+  fi
+
+  ROWS+=("$STATUS_ICON | $NAME | $INSTRUCTIONS")
+done
+
+echo "Results:"
+echo ""
+echo "| | Competency | Evaluation Instructions |"
+echo "|---|---|---|"
+for ROW in "${ROWS[@]}"; do
+  echo "| $ROW |"
+done
+echo ""
+
+echo "Summary: ${#OK[@]} ok, ${#INACTIVE[@]} inactive, ${#MISSING[@]} missing (of ${#EXPECTED_NAMES[@]} expected)"
+
+if [[ "${#MISSING[@]}" -gt 0 || "${#INACTIVE[@]}" -gt 0 ]]; then
+  exit 1
+fi
+
+echo "All expected competencies exist and are active."
+exit 0

package/skills/service-concierge-portal-generate/references/portal-deploy-runbook.md

@@ -43,6 +43,7 @@ At the end of the run, print the live customer-facing portal URL for the operato
 >
 > | # | Step | Command / surface | Verify |
 > |---|---|---|---|
+> | 0 | **MCP authorization pre-check** | Confirm the `metadata-experts` MCP server (tool `execute_metadata_action`) is authorized *before* asking §A's branding questions — Stage 6 below hard-depends on it to author `sfdc_cms__brandingSet/*/content.json` (no reliable static fallback for the exhaustive branding-token schema). If the server is unauthorized, tell the operator now and ask whether to (a) pause here and authorize it via `claude mcp` / `/mcp`, or (b) proceed and stop before Stage 6 once colors are already collected. Do not silently discover this at Stage 6. | MCP tool call succeeds, or operator has explicitly chosen how to proceed |
 > | 1 | Collect branding + access | §A `AskUserQuestion` × 7 | User confirms values |
 > | 2 | Prerequisite check | §B — `GET /connect/communities` returns 200 | JSON has `communities` array |
 > | 3 | Provision the site | §C — `POST /connect/communities` | Returns `id` (Network Id) |

package/skills/service-de-channel-activate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: service-de-channel-activate
-description: "Activate an Enhanced `MessagingChannel` (WhatsApp / Apple / Facebook / SMS / RCS) by PATCHing `MessagingChannelUsage.DeploymentStatus` from `Disabled` to `Provisioning` via the standard REST sobject endpoint. The UDD save-hook fires on the REST write, dispatches by `MessageType` for the external callout (`WHATS_APP` → Meta `/register`, `FACEBOOK` → `subscribeFacebookPage`, `TEXT` → `registerCsotSms`; Apple, LINE, and others need no external call), writes the terminal `Active` or `Error`, and flips `MessagingChannel.IsActive`. The chain is synchronous on the HTTP response — WhatsApp returns 204 only after Meta confirms registration (~15-21s); channels with no external callout are near-instant (~1s on Apple). No Aura RPC; no CSRF cookies. Use this skill when the user needs to activate an already-inserted Enhanced messaging channel headlessly via REST."
+description: "Activate an Enhanced `MessagingChannel` (WhatsApp/Apple/Facebook/SMS/RCS) by PATCHing `MessagingChannelUsage.DeploymentStatus` from `Disabled` to `Provisioning` via the REST sobject endpoint. The UDD save-hook dispatches by `MessageType` for the external callout (`WHATS_APP`→Meta `/register`, `FACEBOOK`→`subscribeFacebookPage`, `TEXT`→`registerCsotSms`; Apple/LINE need none), writes the terminal `Active`/`Error`, and flips `IsActive`. Synchronous on the HTTP response — WhatsApp returns 204 after Meta confirms (~15-21s); no-callout channels are near-instant. No Aura RPC, no CSRF cookies. Use to activate an already-inserted Enhanced channel headlessly via REST. Do not use for full end-to-end setup — use `service-de-headless-channel-configure`."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"
@@ -13,9 +13,10 @@ metadata:
     - tool: ["sf"]
       semver: ">=2.0.0"
   relatedSkills:
-    - "service-de-channel-consent-configure"
     - "service-de-channel-create"
     - "service-de-channel-routing-configure"
+    - "service-de-channel-settings-configure"
+    - "service-de-headless-channel-configure"
 ---
 
 # Activating a Messaging Channel
@@ -88,7 +89,7 @@ Unlike the old Aura-based version of this skill, there are no `{POLL_TIMEOUT_S}`
 **Failure — validator or server-side provisioning error:**
 ```json
 {"ok": false, "kind": "readiness-failed", "errorCode": "FIELD_INTEGRITY_EXCEPTION",
- "message": "...", "hint": "validateChannelReadinessOnProvisioning rejected the write — most commonly missing consent; run service-de-channel-consent-configure first"}
+ "message": "...", "hint": "validateChannelReadinessOnProvisioning rejected the write — most commonly missing consent; run service-de-channel-settings-configure first"}
 {"ok": false, "kind": "provisioning-error", "mcuId": "0gL...", "errorReason": "MetaRegistrationFailed", "errorDetails": "..."}
 {"ok": false, "kind": "verification-failed", "hint": "WhatsApp phone number verification failed or was declined by user"}
 {"ok": false, "kind": "verification-request-failed", "errorCode": "...", "message": "...", "hint": "Could not request verification code from Meta"}
@@ -170,7 +171,7 @@ Classify by HTTP status:
 | Message fragment | Meaning | Envelope |
 | --- | --- | --- |
 | "invalid deployment status transition" | The current status doesn't allow `→ Provisioning` (e.g. MCU is already `Active` — Stage 1 should have caught this, but there's a race window). | Re-read MCU; if now `Active`, emit success-noop. If `Provisioning`, Stage 3 poll. Otherwise emit `{ok:false, kind:"readiness-failed", ...}`. |
-| "consent" / "keyword" / mentions of STOP/HELP | `validateChannelReadinessOnProvisioning` rejected — channel doesn't have required consent configured. | `{ok:false, kind:"readiness-failed", errorCode:"FIELD_INTEGRITY_EXCEPTION", message, hint:"channel requires a ConsentType and a matching MsgChannelLanguageKeyword record (opt-out keyword + confirmation) before activation — run service-de-channel-consent-configure"}`. |
+| "consent" / "keyword" / mentions of STOP/HELP | `validateChannelReadinessOnProvisioning` rejected — channel doesn't have required consent configured. | `{ok:false, kind:"readiness-failed", errorCode:"FIELD_INTEGRITY_EXCEPTION", message, hint:"channel requires a ConsentType and a matching MsgChannelLanguageKeyword record (opt-out keyword + confirmation) before activation — run service-de-channel-settings-configure"}`. |
 | "routing" / "queue" / "SessionHandler" | Routing precondition (Stage 1 should have caught, but the validator re-checks). | `{ok:false, kind:"no-routing", message, hint:"run service-de-channel-routing-configure first"}`. |
 | other | Unrecognized validator error. | `{ok:false, kind:"readiness-failed", errorCode, message}`. |
 
@@ -252,7 +253,7 @@ If this skill is the leaf (user invoked it directly), render:
 - `Info: Already active — MessagingChannel {CHANNEL_ID} is IsActive=true. No changes.` (no-op path)
 - `Error: Routing not configured — run 'service-de-channel-routing-configure' skill first.` (no-routing)
 - `Error: No MessagingChannelUsage row — run the insertion skill first.` (no-mcu)
-- `Error: Readiness check failed: {message} — if it mentions consent/keywords, run 'service-de-channel-consent-configure' first.` (readiness-failed)
+- `Error: Readiness check failed: {message} — if it mentions consent/keywords, run 'service-de-channel-settings-configure' first.` (readiness-failed)
 - `Error: Activation failed: {errorReason} — {errorDetails}` (provisioning-error)
 - `Error: WhatsApp phone number verification failed: {hint}` (verification-failed)
 - `Error: Could not request verification code: {message}` (verification-request-failed)

package/skills/service-de-channel-create/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: service-de-channel-create
-description: "**INTERNAL USE ONLY — invoked by `service-de-headless-channel-configure` orchestrator.** Insert an Enhanced messaging `MessagingChannel` record (plus its child `MessagingChannelUsage` as a free server-side side-effect) of any supported type — WhatsApp, LINE, Apple Business Chat, Facebook, or SMS (Text). Given a `{MESSAGE_TYPE}` and the corresponding type-specific inputs, runs the shared preflight → Connect-insert → verify flow and branches only where a type genuinely differs (request body, prerequisites, error classes). Uses the sanctioned `POST /services/data/v{V}/connect/livemessage/channels` Connect REST endpoint — no Aura session, no token extracted into shell state. **Users should always invoke `service-de-headless-channel-configure` instead — it handles insert → route → activate in one flow.** Use this skill when inserting a messaging channel of any type; it replaces the four former per-type creation skills."
+description: "**INTERNAL USE ONLY — invoked by `service-de-headless-channel-configure`.** Insert an Enhanced messaging `MessagingChannel` (plus child `MessagingChannelUsage` as a free side-effect) of any type — WhatsApp, LINE, Apple Business Chat, Facebook, or SMS. Given a `{MESSAGE_TYPE}` and its inputs, runs the shared preflight → Connect-insert → verify flow, branching only where a type differs. Uses `POST /services/data/v{V}/connect/livemessage/channels` — no Aura session, no shell-stored token. **Invoke `service-de-headless-channel-configure` instead** — it handles insert → route → activate in one flow; replaces the four former per-type creation skills."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"
@@ -14,8 +14,8 @@ metadata:
       semver: ">=2.0.0"
   relatedSkills:
     - "service-de-channel-activate"
-    - "service-de-channel-consent-configure"
     - "service-de-channel-routing-configure"
+    - "service-de-channel-settings-configure"
     - "service-de-headless-channel-configure"
     - "service-de-waba-integrate"
 ---
@@ -349,7 +349,7 @@ Rendered (when invoked directly rather than by the orchestrator):
 - `Error: {kind}: {message or hint}`
 
 On success the caller can immediately invoke `service-de-channel-routing-configure` with the
-returned `channelId`, then `service-de-channel-consent-configure`, then
+returned `channelId`, then `service-de-channel-settings-configure`, then
 `service-de-channel-activate`. Those three are message-type-agnostic (they operate on
 `MessagingChannel.Id` + `MessagingChannelUsage.Id`), so there's no downstream dispatch concern.
 

package/skills/service-de-channel-routing-configure/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: service-de-channel-routing-configure
-description: "Configure routing on a newly-inserted Enhanced `MessagingChannel` so that activation will accept it. Given a `{CHANNEL_ID}`, walks the user through picking a routing type (Omni-Channel Queue, Omni-Flow, Agentforce Service Agent, Digital Worker, or direct User), locates or provisions the routing target, then PATCHes the channel's `SessionHandlerId` (plus `FallbackQueueId` where required) to it. Use between the insertion skill and the activation skill — activation fails server-side with `nullQueueId` / `LiveMessageSetupException` if no valid `SessionHandlerId` is set on the channel."
+description: "Configure routing on a newly-inserted Enhanced `MessagingChannel` so activation will accept it. Given a `{CHANNEL_ID}`, walks through picking a routing type (Omni-Channel Queue, Omni-Flow, Agentforce Service Agent, Digital Worker, or direct User), locates or provisions the target, then PATCHes `SessionHandlerId` (plus `FallbackQueueId` where required). Use between insertion and activation — activation fails server-side with `nullQueueId`/`LiveMessageSetupException` if no valid `SessionHandlerId` is set. Do not use for full end-to-end setup — use `service-de-headless-channel-configure`."
 metadata:
   version: "1.1"
   minApiVersion: "67.0"
@@ -14,8 +14,8 @@ metadata:
       semver: ">=2.0.0"
   relatedSkills:
     - "service-de-channel-activate"
-    - "service-de-channel-consent-configure"
     - "service-de-channel-create"
+    - "service-de-channel-settings-configure"
     - "service-de-headless-channel-configure"
 ---
 
@@ -27,7 +27,7 @@ Ensures a `MessagingChannel` has valid routing configured before activation. The
 
 These skills create **Enhanced** channels (`PlatformType=Enhanced`, SCRT2). All five SessionHandler domains are writable on Enhanced channels. (A Standard/SCRT1 channel would only accept a Flow as SessionHandler — the server rejects any other domain with "Only flows of type Omni-Channel are supported". These skills never create Standard channels, so that path isn't handled here.)
 
-**Where this fits:** the channel is inserted by `service-de-channel-create` (or a per-type leaf); this skill sets routing; `service-de-channel-consent-configure` sets consent; then `service-de-channel-activate` flips it live — activation requires both routing and consent. The `service-de-headless-channel-configure` orchestrator runs all four in sequence.
+**Where this fits:** the channel is inserted by `service-de-channel-create` (or a per-type leaf); this skill sets routing; `service-de-channel-settings-configure` sets consent; then `service-de-channel-activate` flips it live — activation requires both routing and consent. The `service-de-headless-channel-configure` orchestrator runs all four in sequence.
 
 Supported routing types — all set `SessionHandlerId`, some also set `FallbackQueueId`: