@salesforce/afv-skills 1.65.0 → 1.66.0

package/skills/service-itsm-agentic-setup-incident-sla-configure/references/workflow.md

@@ -11,34 +11,65 @@ tools. Call shapes / templates / response envelope / gotchas live in `references
 Each Phase 3a read carries a **skip-if-already-known** clause: skip only when the same fact was
 produced **this session** by a successful `dispatch_readonly` on the current org and unwritten since —
 a user statement is never cache-eligible. Cacheable: IT Service Management enablement (Phase 1a,
-only if `ENABLED`), master Incident Mgmt pref (step 1, only if
-`ENABLED`), SLA feature + Versioning (Phase 1b), Incident describe (3, incl. the `Incident.Priority`
+only if `ENABLED`), master Incident Mgmt pref (Phase 1b, only if
+`ENABLED`), SLA feature + Versioning (Phase 1c), Incident describe (3, incl. the `Incident.Priority`
 picklist), the priority-matrix flag (Phase 2 step 2), `BusinessHoursId` (4), SLA Connect ops (2). (Step 5 resolves no Account — Incident has
 none.) **When in doubt, re-check.**
 
 ## Phase 1a — IT Service Management enablement gate
 
-**Resolve this gate first, before Phase 1b and before the Master Incident Mgmt pref below.**
+**Resolve this gate first. The Incident Management gate (Phase 1b) is resolved immediately after it and before Phase 1c.**
 "IT Service Management" (`service-cloud-itsm-setup`) is a higher-level org gate — it sits above every per-feature ITSM master toggle, including Master
 Incident Management. Read via the Setup Discovery Connect API
-(`GET .../connect/setup/discovery/features`), filtered client-side to the **exact** apiName
-`service-cloud-itsm-setup` — never a look-alike. It has two states, `ENABLED` /
-`NOT_ENABLED` (no `NOT_AVAILABLE` — treat any unexpected value as a halt).
-
-- `ENABLED` → proceed to Phase 1b.
-- `NOT_ENABLED` → tell the user plainly that IT Service Management is not enabled, then a single
-  `AskUserQuestion`: enable it now (note it's **reversible** — it can be disabled again later) or
-  stop.
-  - **Enable** → dispatch the enable route **directly** — there is no owning SOR to delegate this
-    write to yet (unlike the Master Incident Mgmt gate below, which delegates to
-    `service-itsm-incident-mgmt-configure`); this is a scoped, temporary exception to "delegate
-    every write," flagged for a future delegate swap once a dedicated SOR exists. Halt and surface
-    the raw error on any failure. Re-read to confirm `ENABLED` before continuing.
-  - **Stop** → halt, point to Setup for manual enablement.
+(`GET /services/data/v{version}/connect/setup/discovery/features`, using the org's full API version with its
+minor such as v68.0; if the read fails, stop and do not retry other version strings), filtered client-side to the **exact** apiName
+`service-cloud-itsm-setup` — never a look-alike. Exact `ENABLED` passes immediately. Only exact
+`NOT_ENABLED` with no blocked reasons is eligible for confirmed enablement.
+
+- `ENABLED` → continue to Phase 1b (Incident Management gate), then Phase 1c.
+- Exact `NOT_ENABLED` with no blocked reasons → ask every time, never as plain text, with a single
+  `AskUserQuestion` (single-select, exactly two options: Yes and No): **“IT Service Enablement is off —
+  enable it now?”** The options are exactly “Yes” and “No”, with no other text in the question
+  or options. Do not preview later steps before it is answered.
+  - **Yes** → delegate to the `IncidentMgmt` SOR, explicitly stating that the user already
+    confirmed this exact change in this conversation so it does not ask again. Run its
+    `read-itsm-setup-feature-status`, `enable-itsm-setup-feature`, and
+    `verify-itsm-setup-feature-status` steps. Halt on blocked reasons, an error, a missing entry, or
+    any verify result other than exact `ENABLED`.
+    Delegating means the MCP tools, not a Claude Code skill: `describe` the `IncidentMgmt` SOR, read
+    its steps by `id`, and `dispatch` each step exactly as the SOR defines it. Never call `Skill` for
+    it and never invent an enable URL.
+  - **No** → halt, point to Setup for manual enablement.
+- Missing entry, error, blocked reasons, or any other status → halt and point to Setup; do not ask
+  to enable and do not delegate.
 
 Shapes: `references/mcp-invocation.md` (Phase 1a).
 
-## Phase 1b — SLA Management for IT Service prerequisite gate
+## Phase 1b — Incident Management prerequisite gate
+
+**Resolve this gate right after Phase 1a and before Phase 1c; it is a separate question from the SLA Management acks.**
+`service-cloud-itsm-incident` is the master ITSM Incident Management pref that every Incident SLA artifact
+depends on. Read via the same Setup Discovery Connect API as Phase 1a, filtered client-side to the
+**exact** apiName `service-cloud-itsm-incident` — never a look-alike (`service-cloud-incident-management`
+is generic Case-based Incident Management, not our target). Skip the read only when the cache clause in
+“Before you start” applies. Read `status`:
+
+- `ENABLED` → continue to Phase 1c.
+- `NOT_AVAILABLE` (license missing) → **halt and surface it** — cannot be enabled here, no delegate/ack.
+- `NOT_ENABLED` (empty blocked reasons) → ask “Incident Management is off — enable it now?” every time with a single
+  `AskUserQuestion` (single-select, exactly two options: Yes and No), never as plain text, and never auto-enable as an
+  implied SLA dependency.
+  - **Yes** → delegate to the `IncidentMgmt` SOR, stating that the user already confirmed this exact change so it must
+    not ask again. Run its `read-itsm-incident-feature-status`, `enable-itsm-incident-feature` and
+    `verify-itsm-incident-feature-status` steps; require exact `ENABLED`. Delegating means the MCP tools, not a Claude
+    Code skill: `describe` the `IncidentMgmt` SOR, read its steps by `id`, and `dispatch` each step exactly as the SOR
+    defines it. Never call `Skill` for it and never invent an enable URL.
+  - **No** → halt and point to Setup; every SLA artifact depends on the master being on.
+- Blocked reasons, error, missing entry or any other status → halt with a plain explanation and no question.
+
+Full shape + why setup-org-preferences 404s here: `references/mcp-invocation.md` (Phase 1b).
+
+## Phase 1c — SLA Management for IT Service prerequisite gate
 
 **Resolve this gate first, on its own. Reads are safe up front; confirm the org before any write.**
 "SLA Management for IT Service" is enabled only when **both** Simplified SLA Setup **and** SLA
@@ -50,13 +81,15 @@ settings surface) — discover → describe → dispatch rather than re-deriving
 Shapes / preconditions / `enableBlockedReasons` / ack wording: `references/mcp-invocation.md`.
 
 - **Read both** (`dispatch_readonly`); proceed to Phase 2 **only when both are on**.
-- **On an OFF org, read the master license first** (Phase 3a step 1, `service-cloud-itsm-incident`):
-  `NOT_AVAILABLE` → **HALT** — don't flip the permanent Versioning switch where Incident SLA can't run.
-- **Two separate `AskUserQuestion` acks — never merge.** (a) master Incident Mgmt `NOT_ENABLED` → ask
-  to enable it first (reversible, no permanence warning). (b) a *distinct* permanence ack: completing
-  the gate also turns on **SLA Versioning** (a **separate** write), which **can't be turned off** (SLA
-  Management disables later but Versioning stays on). Offer **enable**/**stop** — no "versioning-off";
-  a bare "enable SLA" is **not** consent.
+- **The master license was already resolved in Phase 1b** (`service-cloud-itsm-incident`): `NOT_AVAILABLE` halted there, so
+  the permanent Versioning switch is never flipped where Incident SLA can't run.
+- **Two separate `AskUserQuestion`s before any write — never merge, never skip.** (Q1) SLA Management
+  off → ask “SLA Management for IT Service is off — enable it now?” (Yes/No, no permanence warning; skip
+  only when SLA Management already reads on). (Q2) a *distinct* permanence ack: completing the gate also
+  turns on **SLA Versioning** (a **separate** write), which **can't be turned off** (SLA Management
+  disables later but Versioning stays on). Offer **enable**/**stop** — no "versioning-off". A Yes at
+  Phase 1a/1b, a bare "enable SLA" or the original request is **not** consent for either write; do not
+  preview later steps before each question is answered. Incident Management was already asked at Phase 1b.
 - **Decline (b), non-empty `enableBlockedReasons`, or a re-read mismatch → HALT** — enable no SLA
   Mgmt/Versioning, don't proceed to Phase 2/3a (a reversible master enable from (a) stands). **After
   any write, re-read both and report the REAL state** — never trust `201`/`204`.
@@ -65,7 +98,7 @@ Shapes / preconditions / `enableBlockedReasons` / ack wording: `references/mcp-i
 
 Once the gate passes, offer the OOB policy **before** any custom-flow questions. **Incident only.**
 
-1. **Prerequisite + detect.** Confirm master Incident Mgmt pref `ENABLED` (Phase 3a step 1). Then
+1. **Prerequisite + detect.** Confirm master Incident Mgmt pref `ENABLED` (Phase 1b). Then
    `dispatch_readonly` `GET /headless/invoke/platform/slasettings` (get-existing-checkbox-states) —
    its lowercase-keyed map's `incident` value is the authoritative "is the OOB default seeded?"
    answer (this is the seeder's own dedup read; it maps to display name **"Standard Support for
@@ -93,7 +126,7 @@ Once the gate passes, offer the OOB policy **before** any custom-flow questions.
    matrix flag). The predefined policy is priority-tiered, and with the matrix **off** every Incident
    gets the org's default priority, so only that tier's milestones fire. If it is off, say so plainly
    in the fork prompt (when the fork is skipped, on the Priority-tiered option of the strategy
-   question instead) and point to `service-itsm-incident-priority-configure` to turn it on. This is a
+   question instead) and point to the Priority Matrix setting in Setup to turn it on. This is a
    warning, not a gate — never enable the matrix from this skill.
    **Business Hours note (only when the user specified hours).** The seeder takes **no** Business Hours
    input — it always attaches the org's active **default** Business Hours (`IsDefault = true`), or none
@@ -120,15 +153,7 @@ Once the gate passes, offer the OOB policy **before** any custom-flow questions.
 
 **On any `401` / `403` / `404` from a step below, halt and surface the raw error** — the org/client is misconfigured. `401` → MCP auth (ECA/token). `403` → user perm OR ITSM Incident Management license/pref missing. `404` → `headless-360` not activated OR Entitlement Management not enabled for Incident.
 
-1. **Master Incident Management pref — direct read** *(skip conditions in “Before you start”)*.
-   `dispatch_readonly` `GET .../connect/setup/discovery/features`, filter `features[]` to the **exact**
-   `apiName == "service-cloud-itsm-incident"` — never a look-alike (`service-cloud-incident-management`
-   is generic Case-based Incident Management, not our target). Read `status`: `ENABLED` → proceed;
-   `NOT_AVAILABLE` (license missing) → **halt and surface it** — cannot be enabled here, no delegate/ack;
-   `NOT_ENABLED` → **explicit `AskUserQuestion` ack first (never auto-enable as an implied SLA
-   dependency)**, then delegate to `service-itsm-incident-mgmt-configure` inline — that ack is the
-   delegate's confirm-to-write, so never ask twice — and re-read; if declined, halt — every SLA artifact below depends on the master being on. Full shape + why
-   setup-org-preferences 404s here: `references/mcp-invocation.md` (Preflight A).
+1. **Master Incident Management pref** — already gated in Phase 1b; reuse that result. Do not re-ask or re-read unless a write happened since *(skip conditions in “Before you start”)*.
 2. **Discover the Connect operations** — *(skip if already verified this session — see “Before you start”)*.
    `mcp__headless-360__discover(query="sla-management milestone")` to confirm the SLA Management
    Connect API is indexed, then `mcp__headless-360__describe(id=<operation_id>)`
@@ -212,7 +237,7 @@ selection expands to N creates in Phase 4A step 4 (one delegation per milestone,
 
 ## Phase 3c — Confirm before mutating
 
-1. **Confirm the plan** — present the resolved config (target **org**, **SLA Policy** name,
+1. **Confirm the plan** — print the plan as text in the reply **first**, then ask; the `AskUserQuestion` must never refer to a plan that has not already been shown. Present the resolved config (target **org**, **SLA Policy** name,
    **Business Hours: `<name>`** (and, if Phase 3a step 4 planned a create, its time zone + weekly windows and
    that it will be **created** — a new record this skill does not remove later), the **engagement model** (per-Incident via `EntitlementId` — **no
    Account**, since Incident has no Account field), and the **full per-milestone list** — never
@@ -348,7 +373,7 @@ IST business-hours note: `references/mcp-invocation.md` (Milestone Actions).
     but the derived `Priority` is still the order-1 tier after **one** `Impact`/`Urgency` adjustment,
     stop creating test Incidents. Either way, report that the SLA engages but the other tiers were not
     checked, say why (matrix off / matrix maps these inputs to that tier), and point to
-    `service-itsm-incident-priority-configure`. Narrate by `IncidentNumber`, never the Id.
+    the Priority Matrix setting in Setup. Narrate by `IncidentNumber`, never the Id.
 3. **Verify engagement + tiering** — SOQL that an `EntityMilestone` landed on the **correct tier**
     (a Moderate/Low Incident → the 240/960 tier, NOT 30/120) with a `TargetDate` — that row is the
     reliable engagement proof. `Incident.SlaStartDate` is populated when you set `EntitlementId` at

package/skills/agentforce-gpt-email-generation-configure/SKILL.md

@@ -1,312 +0,0 @@
----
-name: agentforce-gpt-email-generation-configure
-description: "Use this skill when users want to manage the GPT Email Generation (Sales Email Assistant) setup page. Trigger when users mention gptemail, generation, gptemail generation."
-metadata:
-  version: "1.0"
----
-
-# Managing Gpt Email Generation
-
-## When to Use This Skill
-
-Manage the GPT Email Generation (Sales Email Assistant) setup page. Reads/writes the EinsteinGPTSalesEmails master pref plus 8 related ECI/Sales-Signals/Coaching feature toggles. Also exposes a composite getState aggregator (28+ keys: pref values, feature-access flags, Hawking ML-platform tenant provisioning status, Conversation Mining provisioning status, CDP/Genie status, Signals2DC status, computed UI-state enum ENABLED/DISABLED/IN_PROGRESS/HAWKING_TENANT_ERROR) and a refresh action that kicks off Conversation Mining background work. All toggles return Boolean (resulting pref/perm value); some have value-add behavior agents must know about — sales-email enable atomically also flips OnlyUseBuilderPrompts so open-prompt is on by default; open-prompt's enabled=true means OnlyUseBuilderPrompts=false (semantic inversion).
-
-## Workflow
-
-Read get-state first to discover current pref/perm/provisioning state and the computed UI-state enum (ENABLED/DISABLED/IN_PROGRESS/HAWKING_TENANT_ERROR). Toggle ordering: when enabling Sales Email Assistant via toggle-sales-email-pref, run toggle-open-prompt AFTER if you want explicit open-prompt control (enabling sales-email auto-flips OnlyUseBuilderPrompts to false in legacy-discovery-off orgs). For Conversation Mining: toggle-sales-conversation-mining-pref must run before toggle-sales-conversation-mining-apd360-perm and refresh-sales-mining (the perm and refresh sit on top of the feature pref). Each write returns Boolean (the resulting pref/perm value); follow with the paired verify-* step to read back via get-state and confirm. Note that toggle-sales-email-pref's enable path performs an atomic dual-pref bulk write (EinsteinGPTSalesEmails=true + OnlyUseBuilderPrompts=false); a single failure rolls back both. Hawking ML-platform tenant must be ready (getState.isHawkingTenantReady) before the UI state reaches ENABLED.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User must have ConversationalIntelligence AccessConversationMiningSettings access (gates conversation-mining/signals2dc/refresh-sales-mining toggles). (check: `Conversation Mining Settings access`)
-- User must have SalesEmailAssistant ModifyOpenPromptAccess access (gates toggle-open-prompt only). (check: `Modify Sales Email prompt access`)
-- User must have SfaGenerative AccessSalesRecordSummaries access (gates call-explorer / APD360-perm / sales-rep-feedback / generative-insights toggles). (check: `Sales Record Summaries access`)
-- Setup admin permission (View Setup + Setup admin) is required ONLY on the single-pref and perm writes — a non-admin gets NoAccessException on those. That covers: signals2dc, sales-rep-feedback, generative-insights, the APD360 perm, and the discovery-framework-OFF single-pref writes (call-summarization / call-explorer / conversation-mining, and sales-email DISABLE). It does NOT cover the sales-email ENABLE bulk-pref path (no admin check) or ANY discovery-framework-ON path (no admin check) — those enforce their own feature-scoped access instead.
-- Einstein GPT platform must be enabled at the org level — getState surfaces this as hasEinsteinGPTSetupDisabled (true means the platform is OFF and the page renders disabled).
-- For sales-email enablement to reach UI state ENABLED: the Hawking ML-platform tenant must be in PROVISION_SUCCESS — getState surfaces this as isHawkingTenantReady. PROVISION_FAILED resets the pref to false; PROVISIONING surfaces UI state IN_PROGRESS.
-- Einstein Conversation Insights (ECI) must be enabled — call-summarization, call-explorer, and conversation-mining feature access requires hasECIEnabled = ORG_PERMISSION_CONVERSATION_PILOT + ORG_PREFERENCE_CONVERSATION_PILOT_PREF + ORG_PERMISSION_CALL_COACHING_READY (getState computes this combined flag).
-- For Signals2DC: CDP/Genie must be enabled (Data Cloud enabled) for the salesConversationMiningDataCloudStatus to reflect a real provisioning state; otherwise getState returns -1 indicating CDP/Genie unavailable.
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `toggle-sales-email-pref`: call `verify-toggle-sales-email-pref` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `toggle-open-prompt`: call `verify-toggle-open-prompt` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `toggle-sales-call-summarization-pref`: call `verify-toggle-sales-call-summarization-pref` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `toggle-sales-call-explorer-pref`: call `verify-toggle-sales-call-explorer-pref` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `toggle-sales-conversation-mining-pref`: call `verify-toggle-sales-conversation-mining-pref` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `toggle-signals2dc-pref`: call `verify-toggle-signals2dc-pref` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `toggle-sales-conversation-mining-apd360-perm`: call `verify-toggle-sales-conversation-mining-apd360-perm` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `toggle-sales-rep-feedback-pref`: call `verify-toggle-sales-rep-feedback-pref` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `toggle-sales-call-generative-insights-pref`: call `verify-toggle-sales-call-generative-insights-pref` (`GET /headless/invoke/platform/gptemail-generation`)
-- After `refresh-sales-mining`: call `verify-refresh-sales-mining` (`GET /headless/invoke/platform/gptemail-generation`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `toggle-sales-email-pref` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-email-pref-toggle` | — |
-| `toggle-open-prompt` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-open-prompt-toggle` | `toggle-sales-email-pref` |
-| `toggle-sales-call-summarization-pref` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-summarization-pref-toggle` | — |
-| `toggle-sales-call-explorer-pref` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-explorer-pref-toggle` | — |
-| `toggle-sales-conversation-mining-pref` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-conversation-mining-pref-toggle` | — |
-| `toggle-signals2dc-pref` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-signals2-dcpref-toggle` | — |
-| `toggle-sales-conversation-mining-apd360-perm` | write | implemented | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-conversation-mining-apd360-perm-toggle` | `toggle-sales-conversation-mining-pref` |
-| `toggle-sales-rep-feedback-pref` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-rep-feedback-pref-toggle` | — |
-| `toggle-sales-call-generative-insights-pref` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-generative-insights-pref-toggle` | — |
-| `get-state` | read | implemented | `GET /headless/invoke/platform/gptemail-generation` | — |
-| `refresh-sales-mining` | write | proposed | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-mining-refresh` | `toggle-sales-conversation-mining-pref` |
-| `verify-toggle-sales-email-pref` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-sales-email-pref` |
-| `verify-toggle-open-prompt` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-open-prompt` |
-| `verify-toggle-sales-call-summarization-pref` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-sales-call-summarization-pref` |
-| `verify-toggle-sales-call-explorer-pref` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-sales-call-explorer-pref` |
-| `verify-toggle-sales-conversation-mining-pref` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-sales-conversation-mining-pref` |
-| `verify-toggle-signals2dc-pref` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-signals2dc-pref` |
-| `verify-toggle-sales-conversation-mining-apd360-perm` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-sales-conversation-mining-apd360-perm` |
-| `verify-toggle-sales-rep-feedback-pref` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-sales-rep-feedback-pref` |
-| `verify-toggle-sales-call-generative-insights-pref` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `toggle-sales-call-generative-insights-pref` |
-| `verify-refresh-sales-mining` | verify | — | `GET /headless/invoke/platform/gptemail-generation` | `refresh-sales-mining` |
-
-### Dependency graph
-
-```mermaid
-graph TD
-  toggle_sales_email_pref["toggle-sales-email-pref (write)"]
-  toggle_open_prompt["toggle-open-prompt (write)"]
-  toggle_sales_call_summarization_pref["toggle-sales-call-summarization-pref (write)"]
-  toggle_sales_call_explorer_pref["toggle-sales-call-explorer-pref (write)"]
-  toggle_sales_conversation_mining_pref["toggle-sales-conversation-mining-pref (write)"]
-  toggle_signals2dc_pref["toggle-signals2dc-pref (write)"]
-  toggle_sales_conversation_mining_apd360_perm["toggle-sales-conversation-mining-apd360-perm (write)"]
-  toggle_sales_rep_feedback_pref["toggle-sales-rep-feedback-pref (write)"]
-  toggle_sales_call_generative_insights_pref["toggle-sales-call-generative-insights-pref (write)"]
-  get_state["get-state (read)"]
-  refresh_sales_mining["refresh-sales-mining (write)"]
-  verify_toggle_sales_email_pref["verify-toggle-sales-email-pref (verify)"]
-  verify_toggle_open_prompt["verify-toggle-open-prompt (verify)"]
-  verify_toggle_sales_call_summarization_pref["verify-toggle-sales-call-summarization-pref (verify)"]
-  verify_toggle_sales_call_explorer_pref["verify-toggle-sales-call-explorer-pref (verify)"]
-  verify_toggle_sales_conversation_mining_pref["verify-toggle-sales-conversation-mining-pref (verify)"]
-  verify_toggle_signals2dc_pref["verify-toggle-signals2dc-pref (verify)"]
-  verify_toggle_sales_conversation_mining_apd360_perm["verify-toggle-sales-conversation-mining-apd360-perm (verify)"]
-  verify_toggle_sales_rep_feedback_pref["verify-toggle-sales-rep-feedback-pref (verify)"]
-  verify_toggle_sales_call_generative_insights_pref["verify-toggle-sales-call-generative-insights-pref (verify)"]
-  verify_refresh_sales_mining["verify-refresh-sales-mining (verify)"]
-  toggle_sales_email_pref --> toggle_open_prompt
-  toggle_sales_conversation_mining_pref --> toggle_sales_conversation_mining_apd360_perm
-  toggle_sales_conversation_mining_pref --> refresh_sales_mining
-  toggle_sales_email_pref --> verify_toggle_sales_email_pref
-  toggle_open_prompt --> verify_toggle_open_prompt
-  toggle_sales_call_summarization_pref --> verify_toggle_sales_call_summarization_pref
-  toggle_sales_call_explorer_pref --> verify_toggle_sales_call_explorer_pref
-  toggle_sales_conversation_mining_pref --> verify_toggle_sales_conversation_mining_pref
-  toggle_signals2dc_pref --> verify_toggle_signals2dc_pref
-  toggle_sales_conversation_mining_apd360_perm --> verify_toggle_sales_conversation_mining_apd360_perm
-  toggle_sales_rep_feedback_pref --> verify_toggle_sales_rep_feedback_pref
-  toggle_sales_call_generative_insights_pref --> verify_toggle_sales_call_generative_insights_pref
-  refresh_sales_mining --> verify_refresh_sales_mining
-```
-
-### Read operations
-
-#### `get-state`
-
-Read the composite Sales Email Assistant + Conversation Intelligence setup state. Returns a Map<String,Object> aggregating: the computed UI-state enum (ENABLED/DISABLED/IN_PROGRESS/HAWKING_TENANT_ERROR), per-feature access flags, every controller-managed pref/perm value, Hawking ML-platform tenant provisioning status, conversation-mining provisioning status, CDP/Genie status, signalsDC status + details, and a SIQ-in-migration flag. The UI-state enum derives from sales-email pref + Hawking provisioning status; on PROVISION_FAILED with the pref enabled, getState ALSO resets the pref to false (side-effect). Read this first for state discovery and for verify-* steps confirming pref/perm writes.
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`   — status: `implemented`
-
-**Output:** Map<String,Object> with ~28 keys: state (computed UI-state enum: ENABLED/DISABLED/IN_PROGRESS/HAWKING_TENANT_ERROR), hasSalesEmailAssistant (boolean), isSalesEmailAssistantPrefEnabled (boolean), isOpenPromptEnabled (boolean — already-inverted; true means open-prompt allowed), hasSalesCallSummarization, isSalesCallSummarizationPrefEnabled, hasSalesCallExplorer, isSalesCallExplorerPrefEnabled, hawkingTenantStatus (ProvisioningStatusEnum: PROVISION_SUCCESS/PROVISIONING/PROVISION_FAILED), isHawkingTenantReady, hasEinsteinGPTSetupDisabled (true means Einstein GPT platform pref is OFF), hasSalesRepFeedback, isSalesRepFeedbackPrefEnabled, hasSalesCallGenerativeInsights, isSalesCallGenerativeInsightsPrefEnabled, isSIQInMigration, isECIToCoreMigrationInProgress, isSalesConversationMiningPermEnabled, isSalesConversationMiningPrefEnabled, isSalesConversationMiningAPD360PermEnabled, salesConversationMiningProvisioningStatus (ConversationMiningProvisioningStatusEnum stringified), salesConversationMiningDataCloudStatus (number; -1 indicates CDP/Genie unavailable), salesConversationMiningAPD360ECIStatus (string), salesConversationMiningStatus (ConversationMiningStatus object — populated only when conversation-mining pref is on), eciSignals2DCFeatureAccess (boolean), eciSignals2DCPref (boolean), signalsDCStatus (string), signalsDCDetails (string).
-
-### Write operations
-
-#### `toggle-sales-email-pref`
-
-Toggle the EinsteinGPTSalesEmails org pref. On enable in legacy-discovery-off orgs performs an atomic dual-pref bulk write that also flips OnlyUseBuilderPrompts=false (open-prompt on by default); a SaveResult failure on either pref returns false and rolls back. On enable in discovery-on orgs the write routes through the Discovery Framework path for the Sales Email feature, which runs pre-enablement validation. Returns the resulting EinsteinGPTSalesEmails value. No public Connect/Tooling/Metadata alternative replicates the dual-pref atomic batch.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-email-pref-toggle`   — status: `proposed`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-#### `toggle-open-prompt`
-
-Toggle open-prompt mode for Sales Email Assistant by writing the OnlyUseBuilderPrompts org pref to the INVERSE of `enabled` (enabled=true → OnlyUseBuilderPrompts=false → open prompts allowed). Returns whether open-prompt is enabled after the write (also inverted). Gated by Modify Sales Email prompt access. No public Connect/Tooling alternative; raw OrgPreferences write of OnlyUseBuilderPrompts is technically possible but semantic inversion makes substitution error-prone.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-open-prompt-toggle`   — status: `proposed`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-**Depends on:** `toggle-sales-email-pref`
-
-#### `toggle-sales-call-summarization-pref`
-
-Toggle the CallSummarization org pref (Conversational Intelligence). Dual-mode: legacy-discovery-off orgs do a direct pref write; discovery-on orgs route through the Discovery Framework path for the Call Summarization feature. Returns the resulting pref value. Public alternative `POST /connect/setup/discovery/feature/sales-cloud-call-summaries/{enable,disable}` exists but splits one toggle into two endpoints — substituting changes SOR shape; controller is the unified-toggle public surface.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-summarization-pref-toggle`   — status: `proposed`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-#### `toggle-sales-call-explorer-pref`
-
-Toggle the CallExplorerEnabled org pref (Conversational Intelligence). Dual-mode: legacy direct pref write, or discovery-on orgs route through the Discovery Framework path for the Call Explorer feature. Returns the resulting pref value. Gated by Sales Record Summaries access. Public alternative `POST /connect/setup/discovery/feature/sales-cloud-call-explorer/{enable,disable}` (Connect API SetupDiscovery) exists with shape mismatch.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-explorer-pref-toggle`   — status: `proposed`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-#### `toggle-sales-conversation-mining-pref`
-
-Toggle the ConversationMining org pref (Sales Signals). Dual-mode: legacy direct pref write, or discovery-on orgs route through the Discovery Framework path for the Sales Signals feature. Returns the resulting pref value. Gated by Conversation Mining Settings access. Prerequisite step for the APD360-perm and refresh-sales-mining toggles. Public alternative `POST /connect/setup/discovery/feature/sales-cloud-sales-signals/{enable,disable}` exists with shape mismatch.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-conversation-mining-pref-toggle`   — status: `proposed`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-#### `toggle-signals2dc-pref`
-
-Toggle the ECISignals2DC org pref (Signals to DataCloud). Single direct pref write (no discovery-framework branch for this pref). Returns the resulting pref value. Gated by Conversation Mining Settings access. CDP/Genie should be enabled for the resulting signalsDCStatus to reflect a real provisioning state. No public Connect/Tooling/Metadata alternative for this specific pref.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-signals2-dcpref-toggle`   — status: `proposed`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-#### `toggle-sales-conversation-mining-apd360-perm`
-
-Toggle the aPD360ForECI org-permission bit. Direct org-permission write (NOT a pref). Returns the resulting perm value. Gated by Sales Record Summaries access. Should run AFTER toggle-sales-conversation-mining-pref — the perm sits on top of the conversation-mining feature pref. No public Metadata/Tooling alternative for org-permission bits at this level.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-conversation-mining-apd360-perm-toggle`   — status: `implemented`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-**Depends on:** `toggle-sales-conversation-mining-pref`
-
-#### `toggle-sales-rep-feedback-pref`
-
-Toggle the EinsteinSalesRepFdbkEnab org pref (Enablement Coaching). Single direct pref write. Returns the resulting pref value. Gated by Sales Record Summaries access. No public Connect/Tooling/Metadata Settings type covers this specific pref.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-rep-feedback-pref-toggle`   — status: `proposed`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-#### `toggle-sales-call-generative-insights-pref`
-
-Toggle the GenerativeConvInsights org pref (Conversational Intelligence). Single direct pref write, plus a server-side info log. Returns the resulting pref value. Gated by Sales Record Summaries access. No public Metadata Settings type covers this specific pref.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-generative-insights-pref-toggle`   — status: `proposed`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)* — Whether d is enabled.
-
-#### `refresh-sales-mining`
-
-Kick off a Sales Conversation Mining refresh and return the resulting ConversationMiningStatus (typically PROCESSING immediately after start). An imperative service trigger, not a pref/perm write. Gated by Conversation Mining Settings access. Should run after toggle-sales-conversation-mining-pref enables the feature. No public Connect/Tooling alternative — service-action without CRUD equivalent.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-mining-refresh`   — status: `proposed`
-
-**Depends on:** `toggle-sales-conversation-mining-pref`
-
-**Output:** ConversationMiningStatus object — the conversation-mining state immediately after the refresh kicks off. Typically PROCESSING when refresh just started; contains status enum + status details. Inspect getState.salesConversationMiningStatus or re-call refresh-sales-mining to poll for completion.
-
-### Verify operations
-
-#### `verify-toggle-sales-email-pref`
-
-Read getState; confirm isSalesEmailAssistantPrefEnabled equals the value passed to toggle-sales-email-pref. On enable, also confirm isOpenPromptEnabled=true (the dual-pref atomic batch flips OnlyUseBuilderPrompts in legacy-discovery-off orgs). Inspect the state UI-enum: ENABLED if Hawking is ready, IN_PROGRESS if PROVISIONING, HAWKING_TENANT_ERROR if PROVISION_FAILED (in which case getState resets the pref to false — re-toggle if needed).
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-sales-email-pref`
-
-#### `verify-toggle-open-prompt`
-
-Read getState; confirm isOpenPromptEnabled equals the value passed to toggle-open-prompt (already inverted server-side; getState returns !OnlyUseBuilderPrompts so true means open-prompt allowed).
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-open-prompt`
-
-#### `verify-toggle-sales-call-summarization-pref`
-
-Read getState; confirm isSalesCallSummarizationPrefEnabled equals the value passed to toggle-sales-call-summarization-pref.
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-sales-call-summarization-pref`
-
-#### `verify-toggle-sales-call-explorer-pref`
-
-Read getState; confirm isSalesCallExplorerPrefEnabled equals the value passed to toggle-sales-call-explorer-pref.
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-sales-call-explorer-pref`
-
-#### `verify-toggle-sales-conversation-mining-pref`
-
-Read getState; confirm isSalesConversationMiningPrefEnabled equals the value passed to toggle-sales-conversation-mining-pref. Optionally inspect salesConversationMiningProvisioningStatus and salesConversationMiningStatus (only populated when pref is on).
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-sales-conversation-mining-pref`
-
-#### `verify-toggle-signals2dc-pref`
-
-Read getState; confirm eciSignals2DCPref equals the value passed to toggle-signals2dc-pref. Inspect signalsDCStatus / signalsDCDetails for the underlying provisioning state when CDP/Genie is enabled.
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-signals2dc-pref`
-
-#### `verify-toggle-sales-conversation-mining-apd360-perm`
-
-Read getState; confirm isSalesConversationMiningAPD360PermEnabled equals the value passed to toggle-sales-conversation-mining-apd360-perm.
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-sales-conversation-mining-apd360-perm`
-
-#### `verify-toggle-sales-rep-feedback-pref`
-
-Read getState; confirm isSalesRepFeedbackPrefEnabled equals the value passed to toggle-sales-rep-feedback-pref.
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-sales-rep-feedback-pref`
-
-#### `verify-toggle-sales-call-generative-insights-pref`
-
-Read getState; confirm isSalesCallGenerativeInsightsPrefEnabled equals the value passed to toggle-sales-call-generative-insights-pref.
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `toggle-sales-call-generative-insights-pref`
-
-#### `verify-refresh-sales-mining`
-
-Read getState; inspect salesConversationMiningStatus (the ConversationMiningStatus object) for the post-refresh state. Refresh kicked from PROCESSING to a terminal status (success/failure) over time — re-poll if still PROCESSING. Also surfaces salesConversationMiningProvisioningStatus.
-
-**Call:** `GET /headless/invoke/platform/gptemail-generation`
-
-**Depends on:** `refresh-sales-mining`

package/skills/agentforce-wizard-ui-forecasting-analytics-components-configure/SKILL.md

@@ -1,64 +0,0 @@
----
-name: agentforce-wizard-ui-forecasting-analytics-components-configure
-description: "Use this skill when users want to einstein Forecasting Prediction Tuner setup (ForecastingPredictive AI application type). Trigger when users mention wizard, ui, forecasting, analytics, components."
-metadata:
-  version: "1.0"
----
-
-# Managing Wizard Ui Forecasting Analytics Components
-
-## When to Use This Skill
-
-Einstein Forecasting Prediction Tuner setup (ForecastingPredictive AI application type). Three Aura ops — get-tuner-setup-state reads whether the predictor's AI application is provisioned; load-tuner-metadata returns the Opportunity field catalog plus the saved prediction configuration; save-tuner-metadata upserts the prediction configuration and returns the AI application id. All gate on Predictive Forecasting + Customize Application + Modify All Data. No public Connect/Tooling/Metadata alternative — the AI application record is tooling-internal.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Org has Predictive Forecasting (Einstein Forecasting Prediction) enabled. (check: `Predictive Forecasting enabled`)
-- Running user has the Customize Application user permission. (check: `USER_PERMISSION_CUSTOMIZE_APPLICATION`)
-- Running user has the Modify All Data user permission. (check: `USER_PERMISSION_MODIFY_ALL_DATA`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `forecasting-prediction-tuner-setup-flow-controller-get-tuner-setup-state` | read | implemented | `GET /headless/invoke/analytics/forecasting-analytics/get-tuner-setup-state` | — |
-| `forecasting-prediction-tuner-setup-flow-controller-load-tuner-metadata` | read | implemented | `GET /headless/invoke/analytics/forecasting-analytics/load-tuner-metadata` | `forecasting-prediction-tuner-setup-flow-controller-get-tuner-setup-state` |
-| `forecasting-prediction-tuner-setup-flow-controller-save-tuner-metadata` | write | implemented | `PATCH /headless/invoke/analytics/forecasting-analytics/save-tuner-metadata` | `forecasting-prediction-tuner-setup-flow-controller-load-tuner-metadata` |
-
-### Read operations
-
-#### `forecasting-prediction-tuner-setup-flow-controller-get-tuner-setup-state`
-
-Read whether the ForecastingPredictive AI application is provisioned. Returns hasAIApplication=true when the AI application exists with a valid id; false blocks downstream tuner steps until upstream Einstein/AI application setup runs.
-
-**Call:** `GET /headless/invoke/analytics/forecasting-analytics/get-tuner-setup-state`   — status: `implemented`
-
-**Output:** A single boolean field hasAIApplication. True when a ForecastingPredictive AI application exists in the org with a valid id; false otherwise.
-
-#### `forecasting-prediction-tuner-setup-flow-controller-load-tuner-metadata`
-
-Load Opportunity custom fields, picklist fields paired with their values (CurrencyIsoCode excluded), the RecordTypeId field with RecordTypeInfo entries when custom record types exist, and the org's saved prediction configuration (null on a fresh org).
-
-**Call:** `GET /headless/invoke/analytics/forecasting-analytics/load-tuner-metadata`   — status: `implemented`
-
-**Depends on:** `forecasting-prediction-tuner-setup-flow-controller-get-tuner-setup-state`
-
-**Output:** Carries availableOppFields (Opportunity custom field list), oppPicklistFieldsAndValues (picklist fields + values plus RecordTypeId+RecordTypeInfo when custom record types exist), and predictionConfig (current saved prediction configuration or null on a fresh org).
-
-### Write operations
-
-#### `forecasting-prediction-tuner-setup-flow-controller-save-tuner-metadata`
-
-Upsert the org's prediction configuration. Accepts a Map<String,Object> under key `predictionConfig`, but the controller first re-serializes it through a string-valued map type — every value is string-coerced — before deserializing into the prediction-config object, so send string-valued fields (e.g. `excludedFields` as a JSON-encoded string, not a native array). Updates when the config carries both AIApplicationId and PredictionDefinitionId, else creates the ForecastingPredictive AI application. Returns the AI application id. Round-trip predictionConfig from the load-tuner-metadata read on partial mutations to preserve unset fields.
-
-**Call:** `PATCH /headless/invoke/analytics/forecasting-analytics/save-tuner-metadata`   — status: `implemented`
-
-**Depends on:** `forecasting-prediction-tuner-setup-flow-controller-load-tuner-metadata`
-
-**Output:** String — the AI application id (aiAppId) of the upserted ForecastingPredictive AI application record. Use as evidence the predictor is now provisioned (a subsequent get-tuner-setup-state read should return hasAIApplication=true).

package/skills/agentforce-wizard-ui-sales-einstein-components-configure/SKILL.md

@@ -1,46 +0,0 @@
----
-name: agentforce-wizard-ui-sales-einstein-components-configure
-description: "Use this skill when users want to wizard subset of the Sales Email Assistant setup and filter-row picklist operations. Trigger when users mention wizard, ui, sales, einstein, components."
-metadata:
-  version: "1.0"
----
-
-# Managing Wizard Ui Sales Einstein Components
-
-## When to Use This Skill
-
-Wizard subset of the Sales Email Assistant setup and filter-row picklist operations. Two boolean org-pref toggles (EinsteinGPTSalesEmailsPref and ORG_PREFERENCE_CALL_SUMMARIZATION) plus a filter-row picklist read for the filter-row UI. The sales-email toggle, when Discovery Framework is off and enabled=true, performs an atomic bulk pref write flipping OnlyUseBuilderPrompts to false alongside the pref write; both toggles echo the saved Boolean. The picklist read returns {label, value} pairs; fieldApiName='RecordTypeId' branches to return the object's record types instead (label = record-type label, value = record-type id). Sibling SOR GPTEmailGeneration covers the remaining 7 toggles + composite getState read on this setup page.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `filter-row-picklist-controller-get-picklist-values` | read | implemented | `GET /headless/invoke/einstein/sales-einstein/filter-row-picklist/get-picklist-values` | — |
-| `sales-email-assistant-setup-controller-handle-sales-email-pref-toggle` | write | implemented | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-email-pref-toggle` | — |
-| `sales-email-assistant-setup-controller-handle-sales-call-summarization-pref-toggle` | write | implemented | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-summarization-pref-toggle` | — |
-
-### Read operations
-
-#### `filter-row-picklist-controller-get-picklist-values`
-
-Returns the available picklist values as {label, value} pairs for a field on an object, used to populate filter-row options. When the field is 'RecordTypeId', returns the object's record types instead (label = record-type label, value = record-type id). Returns an empty list when the object or field is not supplied. Requires View Setup access.
-
-**Call:** `GET /headless/invoke/einstein/sales-einstein/filter-row-picklist/get-picklist-values`   — status: `implemented`
-
-### Write operations
-
-#### `sales-email-assistant-setup-controller-handle-sales-email-pref-toggle`
-
-Sets EinsteinGPTSalesEmailsPref to `enabled`. When Discovery Framework is off and enabled=true, an atomic bulk pref write also flips OnlyUseBuilderPrompts to false (open-prompt defaults on); otherwise the write routes through the Discovery Framework path for the Sales Email feature. Returns Boolean. AURA-IS-CANONICAL: pref absent from Metadata Settings types and from Tooling Organization columns (source-verified).
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-email-pref-toggle`   — status: `implemented`
-
-#### `sales-email-assistant-setup-controller-handle-sales-call-summarization-pref-toggle`
-
-Enables or disables the Sales Call Summarization org preference. Writing the preference requires Setup administrator access, and the saved boolean value is returned.
-
-**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-summarization-pref-toggle`   — status: `implemented`