@salesforce/afv-skills 1.65.0 → 1.65.1

package/skills/industries-fsc-association-engine-settings-configure/SKILL.md

@@ -1,172 +0,0 @@
----
-name: industries-fsc-association-engine-settings-configure
-description: "Use this skill when users want to read and turn on or off the FSC Association Engine org preference. Trigger when users mention fsc, association, engine, settings, fsc association engine settings."
-metadata:
-  version: "1.0"
-  accessCheck: "(AssociationEngineAccessCheck.ORG_HAS_ASSOCIATION_ENGINE) || (AssociationEngineAccessCheck.USER_HAS_ASSOCIATION_ENGINE) || (UngroupedSettingAccessCheck.USER_PERMISSION_CUSTOMIZE_APPLICATION) || (UngroupedSettingAccessCheck.USER_PERMISSION_VIEW_SETUP)"
----
-
-# Managing Fsc Association Engine Settings
-
-## When to Use This Skill
-
-Read and turn on or off the FSC Association Engine org preference. Prefer Tooling AssociationEngineSettings.enableAssociationEngine for the preference itself; use the Aura access-check read to learn whether the caller can modify it. Association-criteria management on this Setup page is a separate skill.
-
-## Workflow
-
-1. getAccessCheckValues_2 (Aura) — returns {allowModify, associationEngine}.
-allowModify is whether Customize Application is on (the UI disables the
-toggle when this is false). associationEngine is the current org-preference
-state. This read also fails closed if View Setup or the Association Engine
-org/user entitlement is missing.
-
-2. tooling-set-enable-association-engine — preferred write. PATCH the
-AssociationEngineSettings Tooling singleton (Id 000000000000000AAA) with
-body {"FullName": "AssociationEngine", "Metadata": {"enableAssociationEngine":
-<bool>}}. FullName is required; omitting it returns FIELD_INTEGRITY_EXCEPTION
-"Full name must be specified to update metadata." enableAssociationEngine is
-an absolute target state, not a flip. A successful PATCH returns empty / 204.
-
-3. Re-read — either tooling-get-association-engine-settings
-(Metadata.enableAssociationEngine) or getAccessCheckValues_2
-(associationEngine). Assert the value equals what you sent.
-
-Aura handlePrefEnable_1 is what the Setup toggle actually calls and it does
-persist — live-verified — but prefer Tooling. The Aura write takes pref +
-value; the only recognized pref is associationEngine (case-insensitive). An
-unrecognized name or an empty string returns CONTROLLER_ERROR with an empty
-message and does not change state. The Aura write is declared void, so the
-200 body is empty even on a real persist; still re-read.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User must have View Setup permission (read + write). (check: `UngroupedSettingAccessCheck.USER_PERMISSION_VIEW_SETUP`)
-- User must have Customize Application permission to toggle the preference (write only). (check: `UngroupedSettingAccessCheck.USER_PERMISSION_CUSTOMIZE_APPLICATION`)
-- Org must have the FSC Association Engine feature license enabled. (check: `AssociationEngineAccessCheck.ORG_HAS_ASSOCIATION_ENGINE`)
-- User profile must carry the FSC Association Engine entitlement. (check: `AssociationEngineAccessCheck.USER_HAS_ASSOCIATION_ENGINE`)
-
-**Operational rules:**
-
-- CANONICAL SEQUENCE — check access, write via Tooling, re-read to verify.
-- SCOPE — this Setup page has one agent-relevant control, the Association
-Engine toggle. init and toggleAssociationEngine are UI wrappers over
-getAccessCheckValues and handlePrefEnable (plus a success toast). The
-association-criteria list on the same page is a separate skill; do not try
-to manage criteria through this one.
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `handlePrefEnable_1`: call `verify-handlePrefEnable_1` (`GET /headless/invoke/platform/fsc-association-engine-settings`)
-- After `tooling-set-enable-association-engine`: call `verify-tooling-set-enable-association-engine` (`GET /services/data/v67.0/tooling/query`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `getAccessCheckValues_2` | read | implemented | `GET /headless/invoke/platform/fsc-association-engine-settings` | — |
-| `handlePrefEnable_1` | read | implemented | `PATCH /headless/invoke/platform/fsc-association-engine-settings/handle-pref-enable` | `getAccessCheckValues_2` |
-| `verify-handlePrefEnable_1` | verify | implemented | `GET /headless/invoke/platform/fsc-association-engine-settings` | `handlePrefEnable_1` |
-| `tooling-get-association-engine-settings` | read | implemented | `GET /services/data/v67.0/tooling/query` | — |
-| `tooling-set-enable-association-engine` | write | implemented | `PATCH /services/data/v67.0/tooling/sobjects/AssociationEngineSettings/000000000000000AAA` | `tooling-get-association-engine-settings` |
-| `verify-tooling-set-enable-association-engine` | verify | implemented | `GET /services/data/v67.0/tooling/query` | `tooling-set-enable-association-engine` |
-
-### Dependency graph
-
-```mermaid
-graph TD
-  getAccessCheckValues_2["getAccessCheckValues_2 (read)"]
-  handlePrefEnable_1["handlePrefEnable_1 (read)"]
-  verify_handlePrefEnable_1["verify-handlePrefEnable_1 (verify)"]
-  tooling_get_association_engine_settings["tooling-get-association-engine-settings (read)"]
-  tooling_set_enable_association_engine["tooling-set-enable-association-engine (write)"]
-  verify_tooling_set_enable_association_engine["verify-tooling-set-enable-association-engine (verify)"]
-  getAccessCheckValues_2 --> handlePrefEnable_1
-  handlePrefEnable_1 --> verify_handlePrefEnable_1
-  tooling_get_association_engine_settings --> tooling_set_enable_association_engine
-  tooling_set_enable_association_engine --> verify_tooling_set_enable_association_engine
-```
-
-### Read operations
-
-#### `getAccessCheckValues_2`
-
-Returns a two-key map: allowModify (true when the caller has Customize Application — the UI disables the toggle when false) and associationEngine (current org-preference state). This is NOT a map of permission-gate names; associationEngine is the preference itself. Requires View Setup plus the Association Engine org and user entitlements; otherwise the call errors. Does not require Customize Application to read. Live-verified 2026-09-02 against orgfarm-a557ae8f7b: {"associationEngine": false, "allowModify": true}.
-
-**Call:** `GET /headless/invoke/platform/fsc-association-engine-settings`   — status: `implemented`
-
-**Output:** Object with two booleans. allowModify: true when the caller can turn the preference on or off. associationEngine: true when Association Engine is currently enabled for the org. Both keys are always present. Live-verified 2026-09-02 against orgfarm-a557ae8f7b.
-
-#### `handlePrefEnable_1`
-
-Aura write the Setup toggle uses. Sets the Association Engine org preference to value (absolute on/off, not a flip). pref must be associationEngine (case-insensitive; ASSOCIATIONENGINE also works). An unrecognized name or an empty string returns CONTROLLER_ERROR with an empty message and does not change state — unlike Branch Management, this write does not silently ignore bad names. Returns void: a 200 body is empty. Prefer the Tooling write (tooling-set-enable-association-engine) for agents; keep this step because it is what the UI calls. Requires View Setup, Customize Application, and the Association Engine org and user entitlements. Live-verified 2026-09-02 against orgfarm-a557ae8f7b.
-
-**Call:** `PATCH /headless/invoke/platform/fsc-association-engine-settings/handle-pref-enable`   — status: `implemented`
-
-**Inputs:**
-
-- `pref` *(`String`)*
-- `value` *(`boolean`)*
-
-**Depends on:** `getAccessCheckValues_2`
-
-**Output:** Empty object. The Aura write is declared void. A 200 means the access gates passed and pref matched associationEngine; it is still not a substitute for re-reading associationEngine. An unrecognized pref does not return 200 — it returns CONTROLLER_ERROR with an empty message. Live-verified 2026-09-02: pref='associationEngine' returned 200 {} and persisted; pref='totallyBogusPrefName' and pref='' each returned CONTROLLER_ERROR and left the preference unchanged.
-
-#### `tooling-get-association-engine-settings`
-
-Public read of the same org preference the Setup toggle writes. Tooling SOQL on the AssociationEngineSettings singleton (one row per org, key prefix 0HE). Project the Metadata compound field and read enableAssociationEngine under it. This is the same value Aura returns as associationEngine — live-verified both directions. Does not return allowModify; use getAccessCheckValues_2 for that.
-
-**Call:** `GET /services/data/v67.0/tooling/query`   — status: `implemented`
-
-**Inputs:**
-
-- `q` *(`String`)* — SOQL projecting Metadata, e.g. SELECT Id, FullName, Metadata FROM AssociationEngineSettings. Read enableAssociationEngine under Metadata.
-
-**Output:** Tooling QueryResult with one record. Metadata.enableAssociationEngine is the current on/off state. FullName is AssociationEngine. Live-verified 2026-09-02 against orgfarm-a557ae8f7b.
-
-### Write operations
-
-#### `tooling-set-enable-association-engine`
-
-Preferred write. PATCH the AssociationEngineSettings Tooling singleton. Body MUST include top-level FullName "AssociationEngine" plus the new state nested under Metadata, e.g. {"FullName": "AssociationEngine", "Metadata": {"enableAssociationEngine": true}}. Omitting FullName returns FIELD_INTEGRITY_EXCEPTION. enableAssociationEngine is an absolute target state. A successful PATCH is empty / 204; re-read to confirm. Live-verified 2026-09-02 against orgfarm-a557ae8f7b: this write flipped the Aura associationEngine value, and the Aura write flipped this field.
-
-**Call:** `PATCH /services/data/v67.0/tooling/sobjects/AssociationEngineSettings/000000000000000AAA`   — status: `implemented`
-
-**Inputs:**
-
-- `body` *(`Object`)* — {"FullName": "AssociationEngine", "Metadata": {"enableAssociationEngine": <boolean>}}. FullName is required.
-
-**Depends on:** `tooling-get-association-engine-settings`
-
-**Output:** HTTP 204 / empty body on success. Re-read tooling-get-association-engine-settings or getAccessCheckValues_2 to confirm. Live-verified 2026-09-02 against orgfarm-a557ae8f7b.
-
-### Verify operations
-
-#### `verify-handlePrefEnable_1`
-
-Re-read getAccessCheckValues_2 (or tooling-get-association-engine-settings) and assert associationEngine / enableAssociationEngine equals the value just written. Required after either write path. Live-verified 2026-09-02 against orgfarm-a557ae8f7b.
-
-**Call:** `GET /headless/invoke/platform/fsc-association-engine-settings`   — status: `implemented`
-
-**Depends on:** `handlePrefEnable_1`
-
-#### `verify-tooling-set-enable-association-engine`
-
-Re-read AssociationEngineSettings via Tooling SOQL and assert Metadata.enableAssociationEngine equals the value just written. Required after tooling-set-enable-association-engine. Live-verified 2026-09-02 against orgfarm-a557ae8f7b.
-
-**Call:** `GET /services/data/v67.0/tooling/query`   — status: `implemented`
-
-**Inputs:**
-
-- `q` *(`String`)* — Same query as tooling-get-association-engine-settings: SELECT Id, FullName, Metadata FROM AssociationEngineSettings.
-
-**Depends on:** `tooling-set-enable-association-engine`
-
-**Output:** Metadata.enableAssociationEngine must equal the boolean sent on the preceding PATCH.

package/skills/industries-fsc-b2b-settings-configure/SKILL.md

@@ -1,61 +0,0 @@
----
-name: industries-fsc-b2b-settings-configure
-description: "Use this skill when users want to read-and-toggle for FSC B2B + FSC Account Plan org preferences (Industries cloud). Trigger when users mention fscb2bsettings."
-metadata:
-  version: "1.0"
-  accessCheck: "(IndustriesAccessCheck.ORG_HAS_B2B) || (setupUtil.isSetupAdmin)"
----
-
-# Querying Fscb2 B Settings
-
-## When to Use This Skill
-
-Read-and-toggle for FSC B2B + FSC Account Plan org preferences (Industries cloud). Read returns a 4-key map {IsFSCB2BPrefEnabled, userHasAccess, isAccountPlanEnabled, isFSCAccountPlanPrefEnabled} where userHasAccess composes Setup-admin AND ORG_HAS_B2B. Write toggles exactly one of two prefs: FSCB2BPref or FSCAccountPlanEnabled; any other value raises IllegalStateException. Both methods require the View B2B Settings access guard.
-
-## Workflow
-
-Order: call getAccessCheckValues first to read the four-key access map, then gate any write on userHasAccess=true (composes Setup-admin AND ORG_HAS_B2B). handlePrefEnable toggles exactly ONE org preference per call: pref must be "FSCB2BPref" or "FSCAccountPlanEnabled" (case-sensitive) — any other value raises IllegalStateException; value is the boolean target state. Both methods require the View B2B Settings access guard and ORG_HAS_B2B feature; without them calls fail with NoAccessException regardless of user permission. Verified live against a live org: getAccessCheckValues returned the 4-key map and handlePrefEnable(FSCB2BPref) round-tripped the toggle (HTTP 200).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Industries B2B feature must be enabled on the org (IndustriesAccessCheck.ORG_HAS_B2B). Enforced at runtime by validateAccess(); calls fail with NoAccessException when ORG_HAS_B2B is off, regardless of user permission. (check: `IndustriesAccessCheck.ORG_HAS_B2B`)
-- Caller must be a Setup admin (setupUtil.isSetupAdmin()). validateAccess() throws NoAccessException when this fails. (check: `setupUtil.isSetupAdmin`)
-- Caller must hold the View B2B Settings access access guard. Enforced declaratively by @ServiceComponentAccessGuard on both methods. (check: `View B2B Settings access`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `getAccessCheckValues_2` | read | implemented | `GET /headless/invoke/platform/fsc/assessment-settings/get-access-check-values` | — |
-| `handlePrefEnable_1` | read | implemented | `PATCH /headless/invoke/platform/fsc/assessment-settings/handle-pref-enable` | `getAccessCheckValues_2` |
-
-### Read operations
-
-#### `getAccessCheckValues_2`
-
-Read four access-check booleans gating the FSC B2B Settings page UI: IsFSCB2BPrefEnabled (ORG_HAS_B2BENABLED), userHasAccess (Setup-admin AND ORG_HAS_B2B), isAccountPlanEnabled (Account Plan enabled), isFSCAccountPlanPrefEnabled (ORG_HAS_FSCACCOUNT_PLAN_ENABLED). userHasAccess controls whether toggle UI is editable. No public Connect/Tooling/Metadata alternative — 4-key composed shape is value-add.
-
-**Call:** `GET /headless/invoke/platform/fsc/assessment-settings/get-access-check-values`   — status: `implemented`
-
-**Output:** Map<String,Boolean> with exactly four keys: IsFSCB2BPrefEnabled, userHasAccess, isAccountPlanEnabled, isFSCAccountPlanPrefEnabled. userHasAccess=true only when caller is Setup admin AND ORG_HAS_B2B is enabled; clients use it to gate edit controls.
-
-#### `handlePrefEnable_1`
-
-Toggle exactly one of two FSC org preferences. pref must be FSCB2BPref (writes ORG_PREFERENCE_FSCB2BPREF) or FSCAccountPlanEnabled (writes ORG_PREFERENCE_FSCACCOUNT_PLAN_ENABLED); any other value raises IllegalStateException. Save failure surfaces as AuraHandledException. Requires View B2B Settings access + Setup admin + ORG_HAS_B2B. No public Metadata API field for these prefs (IndustriesSettings WSDL omits them); Tooling OrganizationSettingsDetail substitution would drop the pref allowlist + access-guard composition (contract-fidelity gate).
-
-**Call:** `PATCH /headless/invoke/platform/fsc/assessment-settings/handle-pref-enable`   — status: `implemented`
-
-**Inputs:**
-
-- `pref` *(`String`)*
-- `value` *(`boolean`)*
-
-**Depends on:** `getAccessCheckValues_2`
-
-**Output:** Empty body on success (HTTP 200 indicates the named org preference was successfully written). Save failure surfaces as AuraHandledException with the SaveResult error message; pref outside {FSCB2BPref, FSCAccountPlanEnabled} raises IllegalStateException.

package/skills/industries-fsc-insurance-settings-configure/SKILL.md

@@ -1,58 +0,0 @@
----
-name: industries-fsc-insurance-settings-configure
-description: "Use this skill when users want to toggle FSC Insurance org preferences (17-key allowlist: FSCINSURANCE_CPQ, FSCINSURANCE_M2MRSHIPS, FSCINSURANCE_MPROD1POL, FSCINSURANCE_REPORT, FSCINSURANCE_CALCULATEPARENTPOLICYONLY, VLOCITY_POLICY_ADMINISTRATION_PREF, VLOCITY_CLAIM_MGMT_PREF, INSURANCE_SERVICE_EXCELLENCE, INSURA. Trigger when users mention fsc, insurance, settings, fsc insurance settings."
-metadata:
-  version: "1.0"
-  accessCheck: "OldAccessCheck.USER_HAS_CUSTOMIZE_APPLICATION_OR_SYS_ADMIN"
----
-
-# Querying Fsc Insurance Settings
-
-## When to Use This Skill
-
-Toggle FSC Insurance org preferences (17-key allowlist: FSCINSURANCE_CPQ, FSCINSURANCE_M2MRSHIPS, FSCINSURANCE_MPROD1POL, FSCINSURANCE_REPORT, FSCINSURANCE_CALCULATEPARENTPOLICYONLY, VLOCITY_POLICY_ADMINISTRATION_PREF, VLOCITY_CLAIM_MGMT_PREF, INSURANCE_SERVICE_EXCELLENCE, INSURANCE_EINSTEIN_PREF, DIGITALINSURANCE_POLICYRNWL, INSURANCE_COEXISTENCE, INSURANCE_TRANSACTION_DETAIL, INSURANCE_BILLING, ENFORCE_INSURANCE_UNIQUE_PRODUCT_CODE, INSURANCE_ENFORCE_UNIQUE_MEMBERS_AND_ASSETS, INSURANCE_DESIGN_ADVISOR, DIGITAL_INSURANCE_REVENUE_COEXISTENCE) and read the admin's access-check map (~22 keys: feature-license booleans + org-preference states + APIEnabled). Workflow: read getAccessCheckValues first to discover which prefs are toggleable in this org, then handlePrefEnable per change. Several prefs gate-check additional license/perm/state when value=true (Service Excellence, Einstein, Report, Vlocity Policy/Claim, Billing, Enforce Unique Members/Assets) and throw NoAccessException on failure. Requires Setup Admin plus at least one of FSC Insurance, FSC Insurance Claim Mgmt, or FSC Insurance Policy Admin license. Billing-context mapping is delegated to the billingContextSettings child component (separate controller, separate SOR) and is OUT OF SCOPE here.
-
-## Workflow
-
-Order: call getAccessCheckValues first — it returns an org-specific boolean map (org-conditional keys) showing which features/prefs are available; use it to decide which toggles are valid in this org before writing. Then call handlePrefEnable once per change. pref must be one of the 17-key allowlist (FSCINSURANCE_CPQ, FSCINSURANCE_M2MRSHIPS, FSCINSURANCE_MPROD1POL, FSCINSURANCE_REPORT, FSCINSURANCE_CALCULATEPARENTPOLICYONLY, VLOCITY_POLICY_ADMINISTRATION_PREF, VLOCITY_CLAIM_MGMT_PREF, INSURANCE_SERVICE_EXCELLENCE, INSURANCE_EINSTEIN_PREF, DIGITALINSURANCE_POLICYRNWL, INSURANCE_COEXISTENCE, INSURANCE_TRANSACTION_DETAIL, INSURANCE_BILLING, ENFORCE_INSURANCE_UNIQUE_PRODUCT_CODE, INSURANCE_ENFORCE_UNIQUE_MEMBERS_AND_ASSETS, INSURANCE_DESIGN_ADVISOR, DIGITAL_INSURANCE_REVENUE_COEXISTENCE) — any other value raises IllegalStateException; value is the boolean target state. Enabling several prefs (value=true) triggers cross-pref/license gates that throw NoAccessException on failure: INSURANCE_BILLING needs INSURANCE_TRANSACTION_DETAIL on; INSURANCE_EINSTEIN_PREF needs APIEnabled + EGPTINSURANCE_REC_SUMMARY + Einstein GPT; FSCINSURANCE_REPORT needs APIEnabled + INSURANCE_MPROD2POL; the VLOCITY_* prefs each need APIEnabled + the matching license; INSURANCE_SERVICE_EXCELLENCE needs Customize Application + Identity Verification + Person Accounts; INSURANCE_ENFORCE_UNIQUE_MEMBERS_AND_ASSETS needs INSURANCE_M2MRSHIPS. Disabling INSURANCE_TRANSACTION_DETAIL is rejected when the org holds that license. Requires Setup Admin + at least one FSC Insurance license. Billing-context mapping (the billingContextSettings child component) is a separate controller/skill and is OUT OF SCOPE here. Verified live against a live org: getAccessCheckValues returned the access map (HTTP 200).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Caller must be Setup Admin (Customize Application or System Administrator). (check: `OldAccessCheck.USER_HAS_CUSTOMIZE_APPLICATION_OR_SYS_ADMIN`)
-- Org must hold at least one FSC Insurance feature license: IndustriesInsurance, FSC Insurance Claim Mgmt, or FSC Insurance Policy Admin. (check: `IndustriesInsuranceAccessCheck.ORG_HAS_INSURANCE OR IndustriesPolicyadminAccessCheck.ORG_HAS_FSCINSURANCE_CLAIM_MGMT OR IndustriesPolicyadminAccessCheck.ORG_HAS_FSCINSURANCE_POLICY_ADMIN`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `getAccessCheckValues_2` | read | implemented | `GET /headless/invoke/industries/industries-insurance/insurance-settings-page/get-access-check-values` | — |
-| `handlePrefEnable_1` | read | implemented | `PATCH /headless/invoke/industries/industries-insurance/insurance-settings-page/handle-pref-enable` | `getAccessCheckValues_2` |
-
-### Read operations
-
-#### `getAccessCheckValues_2`
-
-Returns Map<String,Boolean> aggregating ~22 access-check keys: FSC Insurance feature-license booleans (FSCInsuranceCoverageMaster, FSCInsuranceM2MRships, FSCInsuranceMultiProd1Policy, FSCInsuranceReport, etc.), org-preference states (InsuranceDesignAdvisor, EnforceInsuranceUniqueProductCode, etc.), and APIEnabled. Three keys are conditional on the caller's licenses (VlocityPolicyAdministrationPref, VlocityPolicyClaimMgmtPref, EGPTInsuranceCmpntPref). Used on page load to gate which preference toggles to surface. Throws NoAccessException unless the caller is Setup Admin AND the org has at least one of ORG_HAS_INSURANCE / ORG_HAS_FSCINSURANCE_CLAIM_MGMT / ORG_HAS_FSCINSURANCE_POLICY_ADMIN.
-
-**Call:** `GET /headless/invoke/industries/industries-insurance/insurance-settings-page/get-access-check-values`   — status: `implemented`
-
-**Output:** Map<string,boolean> with these keys (controller body lines 226-272). Unconditional (20): FSCInsuranceCoverageMaster, FSCInsuranceM2MRships, FSCInsuranceMultiProd1Policy, FSCInsuranceReport, FSCInsuranceCalculateParentPolicyOnly, DigitalInsurancePolicyRnwl, InsuranceCoexistence, InsuranceTransactionDetail, InsuranceTransactionDetailAccessible, InsuranceBilling, InsuranceBillingAccessible, EnforceInsuranceUniqueProductCode, InsuranceEnforceUniqueMembersAndAssets, InsuranceDesignAdvisor, DigitalInsuranceRevenueCoexistence, DigitalInsuranceOnly, FSCInsuranceServiceConsole, APIEnabled, VlocityPolicyAdmin, VlocityClaimMgmt. Conditional: VlocityPolicyAdministrationPref (when org has FSC Insurance Policy Admin), VlocityPolicyClaimMgmtPref (when org has FSC Insurance Claim Mgmt), EGPTInsuranceCmpntPref (when EGPTINSURANCE_REC_SUMMARY perm + Einstein GPT enabled).
-
-#### `handlePrefEnable_1`
-
-Writes one named org preference via permAndPrefUtil.setOrgPref(_getPref(pref), value). Allowed pref keys (allowlist; unknown values throw IllegalStateException): FSCINSURANCE_CPQ, FSCINSURANCE_M2MRSHIPS, FSCINSURANCE_MPROD1POL, FSCINSURANCE_REPORT, FSCINSURANCE_CALCULATEPARENTPOLICYONLY, VLOCITY_POLICY_ADMINISTRATION_PREF, VLOCITY_CLAIM_MGMT_PREF, INSURANCE_SERVICE_EXCELLENCE, INSURANCE_EINSTEIN_PREF, DIGITALINSURANCE_POLICYRNWL, INSURANCE_COEXISTENCE, INSURANCE_TRANSACTION_DETAIL, INSURANCE_BILLING, ENFORCE_INSURANCE_UNIQUE_PRODUCT_CODE, INSURANCE_ENFORCE_UNIQUE_MEMBERS_AND_ASSETS, INSURANCE_DESIGN_ADVISOR, DIGITAL_INSURANCE_REVENUE_COEXISTENCE. Cross-pref gates fire when value=true and throw NoAccessException on failure: INSURANCE_BILLING requires INSURANCE_TRANSACTION_DETAIL pref ON; INSURANCE_EINSTEIN_PREF requires APIEnabled + EGPTINSURANCE_REC_SUMMARY + Einstein GPT; FSCINSURANCE_REPORT requires APIEnabled + INSURANCE_MPROD2POL license; VLOCITY_POLICY_ADMINISTRATION_PREF and VLOCITY_CLAIM_MGMT_PREF each require APIEnabled + matching license; INSURANCE_SERVICE_EXCELLENCE requires Customize Application + Identity Verification + Person Accounts; INSURANCE_ENFORCE_UNIQUE_MEMBERS_AND_ASSETS requires INSURANCE_M2MRSHIPS license. Disabling INSURANCE_TRANSACTION_DETAIL (value=false) is rejected when ORG_HAS_INSURANCE_TRANSACTION_DETAIL license is on. Returns void; controller throws ServiceException on setOrgPref failure carrying the first error message.
-
-**Call:** `PATCH /headless/invoke/industries/industries-insurance/insurance-settings-page/handle-pref-enable`   — status: `implemented`
-
-**Inputs:**
-
-- `pref` *(`String`)*
-- `value` *(`boolean`)*
-
-**Depends on:** `getAccessCheckValues_2`

package/skills/industries-fsc-visa-fulfillment-setup-configure/SKILL.md

@@ -1,103 +0,0 @@
----
-name: industries-fsc-visa-fulfillment-setup-configure
-description: "Use this skill when users want to enable Visa Resolve Online (VROL) integration for FSC dispute management (OrgPreferences.VROLIntegration). Trigger when users mention fsc, visa, fulfillment, setup, fsc visa fulfillment setup."
-metadata:
-  version: "1.0"
-  accessCheck: "IndustriesDisputeManagement.userHasAccessToDisputeManagement"
----
-
-# Managing Fsc Visa Fulfillment Setup
-
-## When to Use This Skill
-
-Enable Visa Resolve Online (VROL) integration for FSC dispute management
-(OrgPreferences.VROLIntegration). Step 1 reads two booleans:
-isVisaFulfillmentAccessible (Dispute Management feature license) and
-isVisaFulfillmentEnabled (the org preference) — check accessible first.
-Step 2 ENABLES the preference (enabled=true) and is refused unless the
-caller is a Setup admin and the org has Dispute Management. Enabling is
-ONE-WAY: it is irreversible and permanently locks after a UI confirmation
-modal — disabling is not a supported capability (enabled=false is accepted
-on the wire only as a constraint; see agent_guidance). Both ops are
-aura-routed via /headless/invoke/industries/industries-dispute-management/visa-fulfillment-settings/*.
-AURA-IS-CANONICAL: public Connect/Tooling preference paths drop the
-feature-license gate and cannot reconstruct the accessibility flag;
-Metadata API has no IndustriesDisputeManagementSettings type.
-
-## Workflow
-
-Enabling Visa Resolve Online (VROL) integration is a ONE-WAY operation. Once
-OrgPreferences.VROLIntegration is set to true it is permanently locked: the Setup UI
-disables the toggle after enable and there is no supported path to turn it back off.
-Before enabling, the Setup UI presents a confirmation modal the admin must accept,
-precisely because the action is irreversible — treat enabling as requiring deliberate,
-confirmed intent, and surface that irreversibility to the user before proceeding.
-
-Disabling is NOT a supported capability. Although the save endpoint technically accepts
-enabled=false on the wire, that is a system constraint, not an available action: do not
-present disabling to users as something this skill can do, and never call save with
-enabled=false as a rollback — there is no rollback once the setting is enabled.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- (precondition) (check: `Dispute Management access`)
-
-**Operational rules:**
-
-- AURA-IS-CANONICAL: the public Connect setup.connect.api.{get,update}Preference and
-Tooling OrgPreferenceSetting paths drop the Dispute Management feature-license gate
-this Aura controller enforces, and the read DTO's isVisaFulfillmentAccessible flag
-is not exposed as an org preference, so the two-key state cannot be reconstructed
-from a generic preference read. The Aura controller remains canonical. Metadata API
-has no IndustriesDisputeManagementSettings type.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `getVisaFulfillmentSettings_1` | read | implemented | `GET /headless/invoke/industries/industries-dispute-management/visa-fulfillment-settings/get-visa-fulfillment-settings` | — |
-| `saveVisaFulfillmentPreference_2` | write | implemented | `PATCH /headless/invoke/industries/industries-dispute-management/visa-fulfillment-settings/save-visa-fulfillment-preference` | `getVisaFulfillmentSettings_1` |
-
-### Read operations
-
-#### `getVisaFulfillmentSettings_1`
-
-Reads two booleans for the org: isVisaFulfillmentAccessible (whether Dispute
-Management is available) and isVisaFulfillmentEnabled (whether
-OrgPreferences.VROLIntegration is on). Check accessible first — do not call
-save when accessible is false; the write is refused without Dispute Management
-access. AURA-IS-CANONICAL: a public Connect or Tooling org-preference read
-returns only the enabled boolean; the accessibility flag is not an org
-preference, so the two-key state cannot be reconstructed from a generic
-preference read. Metadata API has no IndustriesDisputeManagementSettings type.
-
-**Call:** `GET /headless/invoke/industries/industries-dispute-management/visa-fulfillment-settings/get-visa-fulfillment-settings`   — status: `implemented`
-
-### Write operations
-
-#### `saveVisaFulfillmentPreference_2`
-
-Enables Visa Resolve Online integration by writing OrgPreferences.VROLIntegration=true.
-This is a ONE-WAY, irreversible operation: the Setup UI shows a confirmation modal
-before enabling and permanently locks the toggle afterward, so there is no supported
-way to disable it once set. Disabling is NOT a capability of this step — although
-the endpoint accepts enabled=false on the wire, treat that only as a system constraint:
-never call it to roll back, and never present disable to users. Refused unless the
-caller is a Setup admin and the org has Dispute Management. AURA-IS-CANONICAL: public
-Connect and Tooling org-preference paths drop the explicit feature-license gate this
-Aura controller enforces — contract-fidelity violation. Metadata API has no
-IndustriesDisputeManagementSettings type.
-
-**Call:** `PATCH /headless/invoke/industries/industries-dispute-management/visa-fulfillment-settings/save-visa-fulfillment-preference`   — status: `implemented`
-
-**Inputs:**
-
-- `enabled` *(`boolean`)*
-
-**Depends on:** `getVisaFulfillmentSettings_1`

package/skills/industries-fsc-wealth-agent-settings-configure/SKILL.md

@@ -1,117 +0,0 @@
----
-name: industries-fsc-wealth-agent-settings-configure
-description: "Use this skill when users want to read or set the org switch for Financial Advisor Assistance. Trigger when users mention fscwealth, agent, settings, fscwealth agent settings."
-metadata:
-  version: "1.0"
----
-
-# Managing Fsc Wealth Agent Settings
-
-## When to Use This Skill
-
-Read or set the org switch for Financial Advisor Assistance. The customer-facing
-name is "Financial Advisor Assistance"; the preference is `WealthAgentPref`.
-
-  GET   /services/data/v67.0/setup/org/preferences/WealthAgentPref
-        -> {isPreferenceEnabled: boolean}
-  PATCH same path, body {desiredState: boolean}
-        -> echoes the post-write {isPreferenceEnabled}
-
-PATCH self-verifies, so no read-back is needed. Two-way toggle; the preference
-name is case-sensitive.
-
-Requires View Setup AND the org to be provisioned for the feature, satisfied by
-either the Financial Advisor Assistance org permission or its pilot equivalent.
-An unprovisioned org returns an error, not a false reading.
-
-This preference is one of four switches and does not make the feature usable on
-its own. Check the preconditions before reporting success.
-
-## Workflow
-
-Only a 200 tells you the switch's real state. Treat any other response as "could
-not determine" and never report the feature as off because of an error. The Setup
-page makes exactly that mistake: when its read fails it still renders the toggle
-in the Off position.
-
-Not every failure is about the org. Two of them are about your own request, and
-reporting either as a provisioning problem is wrong:
-  400 - your request is malformed, typically a missing or non-boolean
-        `desiredState` on the PATCH. Fix the body and retry; says nothing about
-        the org.
-  404 - the preference name is wrong. The name is a permanent key in the
-        server's allowlist, so a correctly spelled name cannot 404 on any org.
-        Retry with the exact spelling.
-
-Any OTHER non-2xx means the org is not provisioned, or the caller lacks View
-Setup. This surfaces as 401 INSUFFICIENT_ACCESS, with different messages on the
-read and write paths so you can tell the customer which half failed. The
-published OAS documents 403 here, so do not match on the code alone.
-
-If asked to turn the feature on, confirm afterwards that the advisors who need it
-hold the per-user Financial Advisor Assistance access permission, and say which
-pieces you could not verify. In the UI, enabling is gated behind a disclosure
-that the feature uses generative AI, that output may be inaccurate, that the
-customer assumes responsibility for how it is applied, and that it consumes
-Einstein Requests, Flex Credits or Data Cloud Requests. The API applies no such
-gate, so surface that before writing.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- View Setup is necessary but not sufficient. This preference carries an additional per-preference access check, satisfied by either the Financial Advisor Assistance org permission or its pilot equivalent, and it gates reads as well as writes. Without it the caller cannot even read the current state. (check: `Org provisioned for Financial Advisor Assistance`)
-- Four things must be true: the org provisioned with the org permission or its pilot equivalent, this preference on, and each advisor granted the per-user Financial Advisor Assistance access permission. Flipping this preference on an org missing the others changes nothing an advisor can observe. (check: `The preference alone does not enable the feature`)
-- The Setup page is registered under FSC Setup Home and is visible only in orgs with Financial Services Cloud. The API call does not gate on the license, but the feature only does anything in a licensed org. (check: `Financial Services Cloud licensing`)
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `setOrgPreferences_1`: call `verify-is-org-preference-enabled` (`GET /services/data/v67.0/setup/org/preferences/WealthAgentPref`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `isOrgPreferenceEnabled_wire_2` | read | — | `GET /services/data/v67.0/setup/org/preferences/WealthAgentPref` | — |
-| `setOrgPreferences_1` | write | — | `PATCH /services/data/v67.0/setup/org/preferences/WealthAgentPref` | `isOrgPreferenceEnabled_wire_2` |
-| `verify-is-org-preference-enabled` | verify | — | `GET /services/data/v67.0/setup/org/preferences/WealthAgentPref` | `setOrgPreferences_1` |
-
-### Read operations
-
-#### `isOrgPreferenceEnabled_wire_2`
-
-Read the switch. Returns {isPreferenceEnabled: boolean} for this one preference. The name is case-sensitive.
-
-**Call:** `GET /services/data/v67.0/setup/org/preferences/WealthAgentPref`
-
-**Output:** {isPreferenceEnabled: boolean} - a single boolean for this preference, not a map keyed by preference name.
-
-### Write operations
-
-#### `setOrgPreferences_1`
-
-Set the switch. Body is {desiredState: <bool>}; the response echoes the post-write state, so no separate verify step is needed.
-
-**Call:** `PATCH /services/data/v67.0/setup/org/preferences/WealthAgentPref`
-
-**Depends on:** `isOrgPreferenceEnabled_wire_2`
-
-**Output:** {isPreferenceEnabled: boolean} echoing the post-write state.
-
-### Verify operations
-
-#### `verify-is-org-preference-enabled`
-
-Optional re-read. The PATCH already echoes post-write state, so this is only worth running when a concurrent writer may have raced.
-
-**Call:** `GET /services/data/v67.0/setup/org/preferences/WealthAgentPref`   — _optional_
-
-**Depends on:** `setOrgPreferences_1`
-
-**Output:** {isPreferenceEnabled: boolean}. Passes when it matches the value just written.

package/skills/industries-fsc-wealth-settings-configure/SKILL.md

@@ -1,99 +0,0 @@
----
-name: industries-fsc-wealth-settings-configure
-description: "Use this skill when users want to toggle FSC (Financial Services Cloud) Wealth Management org preferences and read the access-check map that gates the Setup page. Trigger when users mention fsc, wealth, settings, fsc wealth settings."
-metadata:
-  version: "1.0"
-  accessCheck: "(WealthManagement.isAdminUser) || (WealthManagement.isAdminWithRBLUsingCalc)"
----
-
-# Managing Fsc Wealth Settings
-
-## When to Use This Skill
-
-Toggle FSC (Financial Services Cloud) Wealth Management org preferences and read the access-check map that gates the Setup page. The controller accepts an 8-pref allowlist via the `pref` parameter — `RBLUsingCalc`, `RecordRollup`, `TransformRBLtoDPE`, `SlackForCib`, `IndustriesKycPref`, `TearSheetPref`, `IndustriesOnboarding`, `DigitalLendingReadOnly` — unknown names throw. Two write paths: `handle-pref-enable` is the generic toggle, gated on the FSC org permission for all prefs except `IndustriesKycPref` and `DigitalLendingReadOnly`; `handle-rblpref-enable` is enable-only and additionally runs the calc-engine RBL rule conversion as part of the toggle, returning per-rule conversion outcomes. `get-access-check-values` returns a 16-key map combining preferences, permissions, and the setup-admin flag — call it before a write to determine which prefs the current admin can mutate.
-
-## Workflow
-
-Workflow: (1) Call `get-access-check-values` first to read the access map — most write attempts fail without `IsFinancialServicesPermEnabled` (skipped only for `IndustriesKycPref`/`DigitalLendingReadOnly`). The map is necessary but NOT sufficient: a true permission key does not guarantee a write is accepted — `handle-rblpref-enable` is separately guarded by `isAdminWithRBLUsingCalc`, which is not exposed as its own map key, so `IsRBLUsingCalcPermEnabled:true` can still yield ACCESS_DENIED (verified against a live org). (2a) For non-RBL prefs, call `handle-pref-enable` with the canonical pref name + `value:true`. This path is effectively ENABLE-ONLY for org prefs: `value:true` returns 200 and flips the corresponding `Is*PrefEnabled` flag, but `value:false` returns CONTROLLER_ERROR (`There was an error enabling or disabling a setting: OrgPreferences.<Pref>`) — confirmed for TearSheetPref and IndustriesKycPref against a live org. Treat these toggles as one-way enablement; do not rely on this surface to turn a pref back off. (2b) For `RBLUsingCalc`, prefer `handle-rblpref-enable` — enable-only (`value=false` raises) and additionally converts existing RBL rules through the calc-engine, returning `result.totalRulesCount` + `result.failedRulesErrorMap` so the agent can surface conversion failures; requires the `isAdminWithRBLUsingCalc` guard (see caveat above). (3) Re-read `get-access-check-values` after a write to confirm the corresponding `Is*PrefEnabled` flag flipped (verify chains added below).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User must have WealthManagement isAdminUser access (check: `Wealth Management admin access`)
-- User must have WealthManagement isAdminWithRBLUsingCalc access (check: `Wealth Management admin access`)
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `handle-pref-enable`: call `verify-handle-pref-enable` (`GET /headless/invoke/platform/fsc-wealth-settings`)
-- After `handle-rblpref-enable`: call `verify-handle-rblpref-enable` (`GET /headless/invoke/platform/fsc-wealth-settings`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `handle-pref-enable` | write | implemented | `PATCH /headless/invoke/platform/fsc-wealth-settings/handle-pref-enable` | — |
-| `handle-rblpref-enable` | write | implemented | `PATCH /headless/invoke/platform/fsc-wealth-settings/handle-rblpref-enable` | — |
-| `get-access-check-values` | read | implemented | `GET /headless/invoke/platform/fsc-wealth-settings` | — |
-| `verify-handle-pref-enable` | verify | — | `GET /headless/invoke/platform/fsc-wealth-settings` | `handle-pref-enable` |
-| `verify-handle-rblpref-enable` | verify | — | `GET /headless/invoke/platform/fsc-wealth-settings` | `handle-rblpref-enable` |
-
-### Read operations
-
-#### `get-access-check-values`
-
-Read the 16-key access-check map driving FSC Wealth Setup gating. Returns a `Map<String, Boolean>` mixing org preferences (e.g. `IsRBLUsingCalcPreferenceEnabled`, `isTransformRBLtoDPEEnabled`, `isIndustriesKycPrefEnabled`, `isTearSheetPrefEnabled`, `isIndustriesOnboardingPrefEnabled`, `isReadOnlyRecordsEnabled`), org permissions (e.g. `IsFinancialServicesPermEnabled`, `IsRBLUsingCalcPermEnabled`, `isIndustriesKycPermEnabled`, `isTearSheetPermEnabled`, `isDigitalLendingEnabled`, `isDigitalLendingAdminUserPermEnabled`, `isIndustriesOnboardingEnabled`), and a `userHasAccess` setup-admin flag. Use this read to decide which prefs `handle-pref-enable` / `handle-rblpref-enable` can write — but note the map is NECESSARY-BUT-NOT-SUFFICIENT: a true permission key does not guarantee a write is accepted. Verified against a live org, `IsRBLUsingCalcPermEnabled:true` (with `userHasAccess:true` and `IsFinancialServicesPermEnabled:true`) still returned ACCESS_DENIED from `handle-rblpref-enable`, which is separately guarded by `isAdminWithRBLUsingCalc` — a capability this map does NOT expose as its own key. No public alternative aggregates preferences AND permissions AND setup-admin in one call — `setup.connect.api.checkPreference` only covers preferences, missing 8 of the 16 keys.
-
-**Call:** `GET /headless/invoke/platform/fsc-wealth-settings`   — status: `implemented`
-
-**Output:** Map<String, Boolean> with 16 keys: preferences (`IsRBLUsingCalcPreferenceEnabled`, `isTransformRBLtoDPEEnabled`, `isIndustriesKycPrefEnabled`, `isTearSheetPrefEnabled`, `isIndustriesOnboardingPrefEnabled`, `isReadOnlyRecordsEnabled`), permissions (`IsRBLUsingCalcPrefEnabled` reflecting ORG_HAS_RBLUSING_CALC_PREF, `IsRecordRollupPrefEnabled` reflecting ORG_HAS_RECORD_ROLLUP_PREF, `IsRBLUsingCalcPermEnabled`, `IsFinancialServicesPermEnabled`, `isIndustriesKycPermEnabled`, `isTearSheetPermEnabled`, `isIndustriesOnboardingEnabled`, `isDigitalLendingEnabled`, `isDigitalLendingAdminUserPermEnabled`), and one `userHasAccess` setup-admin flag computed.
-
-### Write operations
-
-#### `handle-pref-enable`
-
-Toggle one of 8 allowlisted FSC Wealth prefs (`RBLUsingCalc`, `RecordRollup`, `TransformRBLtoDPE`, `SlackForCib`, `IndustriesKycPref`, `TearSheetPref`, `IndustriesOnboarding`, `DigitalLendingReadOnly`); unknown names raise IllegalStateException (surfaced on the wire as CONTROLLER_ERROR). For all prefs except `IndustriesKycPref` and `DigitalLendingReadOnly` the controller enforces `IndustriesFSCAccessCheck.ORG_HAS_FINANCIAL_SERVICES` server-side. `RBLUsingCalc` in a non-FSC org is routed through the settings `operation.modify().setBoolean(...)` instead of `permAndPrefUtil.setOrgPref`. `IndustriesKycPref` toggles emit FSC telemetry. No public Connect/Tooling/Metadata alternative reproduces the FSC feature gate, the RBLUsingCalc-without-FSC routing, or the telemetry side-effect — Aura controller is canonical. Verified against a live org: this path is effectively ENABLE-ONLY for org preferences — `value:true` returns HTTP 200 and the matching `Is*PrefEnabled` flag flips on read-back, but `value:false` returns CONTROLLER_ERROR (`There was an error enabling or disabling a setting: OrgPreferences.<Pref>`), confirmed for both `TearSheetPref` (FSC-gated) and `IndustriesKycPref` (not FSC-gated). Treat these toggles as one-way enablement; do not rely on this surface to turn a pref back off.
-
-**Call:** `PATCH /headless/invoke/platform/fsc-wealth-settings/handle-pref-enable`   — status: `implemented`
-
-**Inputs:**
-
-- `pref` *(`String`)* — Value for the pref field.
-- `value` *(`boolean`)* — Toggle the value preference on or off.
-
-#### `handle-rblpref-enable`
-
-Enable an RBL preference (typically `RBLUsingCalc`) and run the calc-engine RBL rule conversion as an atomic side-effect of the toggle. Enable-only: `value=false` raises IllegalStateException. Returns `RblRulesConversionOutputRepresentation` carrying `result.conversionStatus`, `result.totalRulesCount`, `result.failedRulesErrorMap` (per-rule errors), `result.packageNameSpace`, and `result.calcJobDefinitions`. The pref is only flipped on if at least one rule converts; conversion exception triggers an inline pref rollback. Gated by Wealth Management admin access. No public alternative reproduces the calc-engine conversion side-effect or the typed conversion-result return — Aura controller is canonical.
-
-**Call:** `PATCH /headless/invoke/platform/fsc-wealth-settings/handle-rblpref-enable`   — status: `implemented`
-
-**Inputs:**
-
-- `pref` *(`String`)* — Value for the pref field.
-- `value` *(`boolean`)* — Toggle the value preference on or off.
-
-**Output:** RblRulesConversionOutputRepresentation. Carries `result.conversionStatus` (boolean — true when all eligible rules converted), `result.totalRulesCount` (int), `result.failedRulesErrorMap` (map of rule-id → error message for failed rules), `result.packageNameSpace` (string — managed-package namespace; empty for org-default), and `result.calcJobDefinitions` (map of CalcJobDefinition records keyed by job-definition name).
-
-### Verify operations
-
-#### `verify-handle-pref-enable`
-
-Read back via `get-access-check-values` to confirm the just-written pref took effect. The access-check map exposes `IsRBLUsingCalcPreferenceEnabled` (for `RBLUsingCalc`), `isTransformRBLtoDPEEnabled`, `isIndustriesKycPrefEnabled`, `isTearSheetPrefEnabled`, `isIndustriesOnboardingPrefEnabled`, `isReadOnlyRecordsEnabled` — match the write's `pref` to the corresponding `Is*PrefEnabled` key. Note: `RecordRollup` and `SlackForCib` have no direct read-back key in this map; for those, no verify is available.
-
-**Call:** `GET /headless/invoke/platform/fsc-wealth-settings`
-
-**Depends on:** `handle-pref-enable`
-
-#### `verify-handle-rblpref-enable`
-
-Read back via `get-access-check-values` to confirm the RBL pref enable took effect. `IsRBLUsingCalcPreferenceEnabled` reflects `RBLUsingCalc`; `isTransformRBLtoDPEEnabled` reflects `TransformRBLtoDPE`. The verify confirms the pref state but does NOT re-validate calc-engine rule conversion — inspect the write's response (`result.failedRulesErrorMap`, `result.totalRulesCount`) for that.
-
-**Call:** `GET /headless/invoke/platform/fsc-wealth-settings`
-
-**Depends on:** `handle-rblpref-enable`