@salesforce/afv-skills 1.65.0 → 1.66.0

package/skills/industries-advanced-therapy-management-settings-configure/SKILL.md

@@ -1,73 +0,0 @@
----
-name: industries-advanced-therapy-management-settings-configure
-description: "Use this skill when users want to reads the ATM setup wizard config and toggles the single registered ATM Flow Event Preference action (atmSetupToggleFlowEventPref), which writes the org preference \"disable ATM flow orchestration event\". Trigger when users mention advanced, therapy, management, settings, advanced therapy management settings."
-metadata:
-  version: "1.0"
-  accessCheck: "Industries.userCanAccessSetup"
----
-
-# Managing Advanced Therapy Management Settings
-
-## When to Use This Skill
-
-Reads the ATM setup wizard config and toggles the single registered ATM Flow Event Preference action (atmSetupToggleFlowEventPref), which writes the org preference "disable ATM flow orchestration event". The naming is inverted: by DEFAULT the preference is OFF and flow orchestration events for Advanced Therapy Management are ENABLED (required for entry condition-based orchestrator flows to resume normally). Enabling the preference (the "ACTIVE" toggle state) DISABLES those flow events — so an agent must NOT assume ACTIVE means "events are active." Two distinct invocations exist, and BOTH go through the parameterized step (parameterized-execute-admin-setup-step-action), NOT the plain execute-admin-setup-step-action step (which maps to a no-arg execute() that is a no-op for this action and changes nothing): (1) READ current state — paramKeys=[type], paramValues=[GET_STATUS] — returns a boolean result (result=true ⇒ the disable preference is ON ⇒ flow events are currently DISABLED; result=false ⇒ events ENABLED). This read is side-effect-free and can be called standalone without toggling first. (2) WRITE — paramKeys=[inputState], paramValues=[true] or [false] — inputState=true sets the disable preference ON (DISABLES flow events, response custom.toggleStatus=ACTIVE); inputState=false sets it OFF (re-ENABLES events, custom.toggleStatus=INACTIVE). custom.toggleStatus is returned by the WRITE only; the GET_STATUS read returns the boolean result, not custom.toggleStatus. Config is read via the public GET /connect/industries/adminSetup/{fileName}; the parameterized action invocation runs on the Setup dispatcher (Aura) /headless/invoke controller (paramKeys[]/paramValues[] arrays).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User must have Industries AccessSetup access (check: `View Setup permission`)
-
-**Operational rules:**
-
-- IMPORTANT — both the status read and the toggle go through parameterized-execute-admin-setup-step-action. The plain execute-admin-setup-step-action step is a no-op for this action (backing no-arg execute() returns false and writes nothing); never use it to toggle.
-To check current state (e.g. "are ATM flow-orchestration events disabled?"): call parameterized-execute-admin-setup-step-action with actionName=atmSetupToggleFlowEventPref, paramKeys=[type], paramValues=[GET_STATUS]. This is side-effect-free — no need to read config or toggle first. The response's boolean result=true means the disable preference is ON ⇒ flow orchestration events are currently DISABLED; result=false means events are ENABLED (the default) and entry condition-based orchestrator flows can resume normally. (This read returns the boolean result, not custom.toggleStatus.)
-To change the setting: call parameterized-execute-admin-setup-step-action with actionName=atmSetupToggleFlowEventPref, paramKeys=[inputState], and paramValues=[true] to DISABLE flow events (sets the disable preference ON; response custom.toggleStatus=ACTIVE) or paramValues=[false] to ENABLE them (response custom.toggleStatus=INACTIVE). Optionally read config first (get-admin-setup-data, fileName=AdvancedTherapyManagementSetup) to confirm action.name, then verify the new state with the GET_STATUS call above.
-Access: the write requires the Advanced Therapy Orchestration org capability plus Customize Application / System Administrator; page access is gated by View Setup permission.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `get-admin-setup-data` | read | proposed | `GET /connect/industries/adminSetup/{fileName}` | — |
-| `execute-admin-setup-step-action` | write | proposed | `PATCH /headless/invoke/platform/advanced-therapy-management-settings/execute-admin-setup-step-action` | — |
-| `parameterized-execute-admin-setup-step-action` | write | proposed | `PATCH /headless/invoke/platform/advanced-therapy-management-settings/parameterized-execute-admin-setup-step-action` | — |
-
-### Read operations
-
-#### `get-admin-setup-data`
-
-Loads ATM wizard config. Pass fileName=AdvancedTherapyManagementSetup. Returns AdminSetupRepresentation with configurations[].steps[] carrying action.name and stepCompletionCheck the agent traverses to dispatch toggles.
-
-**Call:** `GET /connect/industries/adminSetup/{fileName}`   — status: `proposed`
-
-**Inputs:**
-
-- `fileName` *(`String`)*
-
-### Write operations
-
-#### `execute-admin-setup-step-action`
-
-Execute admin setup step action.
-
-**Call:** `PATCH /headless/invoke/platform/advanced-therapy-management-settings/execute-admin-setup-step-action`   — status: `proposed`
-
-**Inputs:**
-
-- `actionName` *(`String`)* — Name of the action.
-
-#### `parameterized-execute-admin-setup-step-action`
-
-Parameterized execute admin setup step action.
-
-**Call:** `PATCH /headless/invoke/platform/advanced-therapy-management-settings/parameterized-execute-admin-setup-step-action`   — status: `proposed`
-
-**Inputs:**
-
-- `actionName` *(`String`)* — Name of the action.
-- `params` *(`Map<String, String>`)* — Value for params.

package/skills/industries-atm-settings-starter-configure/SKILL.md

@@ -1,76 +0,0 @@
----
-name: industries-atm-settings-starter-configure
-description: "Use this skill when users want to manage Advanced Therapy Management Settings Starter (Health Cloud Starter-license variant of AdvancedTherapyManagementSettings — same ATM Flow Event Preference toggle, a second Setup mount over the same AdminSetupController + atmSetupToggleFlowEventPref action from this setup page. Trigger when users mention advanced, therapy, management, settings, starter, advanced therapy management settings starter."
-metadata:
-  version: "1.0"
----
-
-# Managing Advanced Therapy Management Settings Starter
-
-## When to Use This Skill
-
-Setup page entry point for Advanced Therapy Management Settings Starter (Health Cloud Starter-license variant of AdvancedTherapyManagementSettings — same ATM Flow Event Preference toggle, a second Setup mount over the same AdminSetupController + atmSetupToggleFlowEventPref action, on the advanced-therapy-management-settings-starter dispatcher path). The action writes the org preference "disable ATM flow orchestration event". The naming is inverted: by DEFAULT the preference is OFF and flow orchestration events for Advanced Therapy Management are ENABLED (required for entry condition-based orchestrator flows to resume normally). Enabling the preference (the "ACTIVE" toggle state) DISABLES those flow events — so an agent must NOT assume ACTIVE means "events are active." Two distinct invocations exist, and BOTH go through the parameterized step (parameterized-execute-admin-setup-step-action), NOT the plain execute-admin-setup-step-action step (which maps to a no-arg execute() that is a no-op for this action and changes nothing): (1) READ current state — paramKeys=[type], paramValues=[GET_STATUS] — returns a boolean result (result=true ⇒ the disable preference is ON ⇒ flow events are currently DISABLED; result=false ⇒ events ENABLED). Side-effect free; callable standalone without toggling first. (2) WRITE — paramKeys=[inputState], paramValues=[true] or [false] — inputState=true sets the disable preference ON (DISABLES flow events, response custom.toggleStatus=ACTIVE); inputState=false sets it OFF (re-ENABLES events, custom.toggleStatus=INACTIVE). custom.toggleStatus is returned by the WRITE only; the GET_STATUS read returns the boolean result, not custom.toggleStatus. Config is read via get-admin-setup-data (fileName=AdvancedTherapyManagementSetup).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User must have Industries AccessSetup access (enforced by @ServiceComponentAccessGuard(View Setup permission) on the Aura controller and by the underlying setup-framework Apex layer the Connect API delegates to). (check: `View Setup permission`)
-- Org must have HealthCloud Multi-Step Scheduling enabled (one of the OR-list feature gates on the Connect operation's org-access-check; ATM Settings Starter is the LifeSciences-tree-placed Multi-Step Scheduling configuration entry point). (check: `Multi-Step Scheduling enabled`)
-- Wizard config resource AdvancedTherapyManagementSetup.json must be present in core/ui-industries-common-components/resources/setupConfig/ (jar-shipped; not org-deployable). The Aura component hard-codes featureConfigFileName=AdvancedTherapyManagementSetup.json so the agent must pass that exact value as fileName.
-
-**Operational rules:**
-
-- IMPORTANT — both the status read and the toggle go through parameterized-execute-admin-setup-step-action. The plain execute-admin-setup-step-action step is a no-op for this action (backing no-arg execute() returns false and writes nothing); never use it to toggle.
-To check current state (e.g. "are ATM Starter flow-orchestration events disabled?"): call parameterized-execute-admin-setup-step-action with actionName=atmSetupToggleFlowEventPref, paramKeys=[type], paramValues=[GET_STATUS]. Side-effect-free. The response's boolean result=true means the disable preference is ON ⇒ flow orchestration events are currently DISABLED; result=false means events are ENABLED (the default) and entry condition-based orchestrator flows can resume normally. (This read returns the boolean result, not custom.toggleStatus.)
-To change the setting: call parameterized-execute-admin-setup-step-action with actionName=atmSetupToggleFlowEventPref, paramKeys=[inputState], and paramValues=[true] to DISABLE flow events (sets the disable preference ON; response custom.toggleStatus=ACTIVE) or paramValues=[false] to ENABLE them (response custom.toggleStatus=INACTIVE). Optionally read config first (get-admin-setup-data, fileName=AdvancedTherapyManagementSetup) to confirm action.name, then verify the new state with the GET_STATUS call above.
-Access: the write requires the Advanced Therapy Orchestration org capability plus Customize Application / System Administrator; page access is gated by View Setup permission.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `get-admin-setup-data` | read | proposed | `GET /connect/industries/adminSetup/{fileName}` | — |
-| `execute-admin-setup-step-action` | write | proposed | `PATCH /headless/invoke/platform/advanced-therapy-management-settings-starter/execute-admin-setup-step-action` | — |
-| `parameterized-execute-admin-setup-step-action` | write | proposed | `PATCH /headless/invoke/platform/advanced-therapy-management-settings-starter/parameterized-execute-admin-setup-step-action` | — |
-
-### Read operations
-
-#### `get-admin-setup-data`
-
-Loads ATM wizard config; pass fileName=AdvancedTherapyManagementSetup. Returns AdminSetupRepresentation with configurations[].steps[].action.{name,type}; agent reads action.name=atmSetupToggleFlowEventPref from group 4 (the only AdminExecute) to drive the toggle steps.
-
-**Call:** `GET /connect/industries/adminSetup/{fileName}`   — status: `proposed`
-
-**Inputs:**
-
-- `fileName` *(`String`)*
-
-**Output:** AdminSetupRepresentation: isSuccess (boolean), errors (array of ErrorRepresentation), featureName (string echoing the loaded config's title key), configurations (array of AdminSetupGroupRepresentation, each with groupName/groupOrder/groupAccessCheck/timeToComplete/groupStatus and steps[] of AdminSetupStepRepresentation carrying name/order/dependency/action{name,type,resource,target}/actionResponse/helpUrl/preValidation/stepAccessCheck/stepCompletionCheck/stepStatus), disableReset (boolean — true for this wizard).
-
-### Write operations
-
-#### `execute-admin-setup-step-action`
-
-Execute admin setup step action.
-
-**Call:** `PATCH /headless/invoke/platform/advanced-therapy-management-settings-starter/execute-admin-setup-step-action`   — status: `proposed`
-
-**Inputs:**
-
-- `actionName` *(`String`)* — Name of the action.
-
-#### `parameterized-execute-admin-setup-step-action`
-
-Parameterized execute admin setup step action.
-
-**Call:** `PATCH /headless/invoke/platform/advanced-therapy-management-settings-starter/parameterized-execute-admin-setup-step-action`   — status: `proposed`
-
-**Inputs:**
-
-- `actionName` *(`String`)* — Name of the action.
-- `params` *(`Map<String, String>`)* — Value for params.

package/skills/industries-batch-document-ai-configure/SKILL.md

@@ -1,196 +0,0 @@
----
-name: industries-batch-document-ai-configure
-description: "Use this skill when users want to configure batch IDP processing templates that schedule unattended document extraction over selected content folders. Trigger when users mention batch, document, ai, batch document ai."
-metadata:
-  version: "1.0"
-  accessCheck: "IntelligentDocumentProcessingAccessCheck.ORG_HAS_INTELLIGENT_DOC_EXTRACT_GATE"
----
-
-# Managing Batch Document Ai
-
-## When to Use This Skill
-
-Configure batch IDP processing templates that schedule unattended document extraction over selected content folders. Steps: pick libraries and drill folders (filtered by DocExtractDefFldrType, default Content_Folder), preflight name uniqueness, create/update with multi-folder bindings + run-as user + start time + reviewBeforeSave flag, then activate/deactivate or delete. All operations route through the batch intelligent document extraction setup endpoint on the dispatcher; no Connect/Tooling alternative exists for this Health Cloud / Industries surface.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Org has Intelligent Document Processing enabled (the IntelligentDocumentProcessingAccessCheck.ORG_HAS_INTELLIGENT_DOC_EXTRACT_GATE feature gate must be on). Every controller method calls checkAccessAndThrowException which fails closed when the gate is off. (check: `IntelligentDocumentProcessingAccessCheck.ORG_HAS_INTELLIGENT_DOC_EXTRACT_GATE`)
-- Running user has Customize Application or System Administrator permission. The class-level @ServiceComponentAccessGuard is Customize Application permission and is also re-checked inside checkAccessAndThrowException. (check: `Customize Application permission`)
-- Running user has View Setup access (setupUtil.hasViewSetup() must be true). Required by every method's access check. (check: `View Setup`)
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`deleteBatchProcessingTemplate_10`** — Delete the BatchProcessingTemplate at batchTemplateId. The service-layer deleteConfiguration cascades to BatchDocumentExtractionFolder child rows; void return. AURA-IS-CANONICAL — raw sObject DELETE on the parent does not reproduce the cascade nor the IDP feature-gate check.
-  - Rollback: No automatic rollback.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `getBatchProcessingTemplates_7` | read | implemented | `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-batch-processing-templates` | — |
-| `getBatchProcessingTemplate_6` | read | implemented | `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-batch-processing-template` | `getBatchProcessingTemplates_7` |
-| `checkBatchTemplateExists_8` | read | implemented | `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/check-batch-template-exists` | — |
-| `getLibraries_1` | read | implemented | `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-libraries` | — |
-| `getFolderItems_2` | read | implemented | `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-folder-items` | `getLibraries_1` |
-| `getFolderItemsCount_3` | read | implemented | `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-folder-items-count` | `getLibraries_1` |
-| `getFolderLocationPath_4` | read | implemented | `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-folder-location-path` | `getLibraries_1` |
-| `createOrUpdateBatchProcessingTemplate_5` | write | implemented | `PATCH /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/create-or-update-batch-processing-template` | `getLibraries_1`, `checkBatchTemplateExists_8` |
-| `updateBatchTemplateActiveStatus_9` | write | implemented | `PATCH /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/update-batch-template-active-status` | `getBatchProcessingTemplates_7` |
-| `deleteBatchProcessingTemplate_10` | delete | implemented | `DELETE /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/delete-batch-processing-template` | `getBatchProcessingTemplates_7` |
-
-### Dependency graph
-
-```mermaid
-graph TD
-  getBatchProcessingTemplates_7["getBatchProcessingTemplates_7 (read)"]
-  getBatchProcessingTemplate_6["getBatchProcessingTemplate_6 (read)"]
-  checkBatchTemplateExists_8["checkBatchTemplateExists_8 (read)"]
-  getLibraries_1["getLibraries_1 (read)"]
-  getFolderItems_2["getFolderItems_2 (read)"]
-  getFolderItemsCount_3["getFolderItemsCount_3 (read)"]
-  getFolderLocationPath_4["getFolderLocationPath_4 (read)"]
-  createOrUpdateBatchProcessingTemplate_5["createOrUpdateBatchProcessingTemplate_5 (write)"]
-  updateBatchTemplateActiveStatus_9["updateBatchTemplateActiveStatus_9 (write)"]
-  deleteBatchProcessingTemplate_10["deleteBatchProcessingTemplate_10 (delete)"]
-  getBatchProcessingTemplates_7 --> getBatchProcessingTemplate_6
-  getLibraries_1 --> getFolderItems_2
-  getLibraries_1 --> getFolderItemsCount_3
-  getLibraries_1 --> getFolderLocationPath_4
-  getLibraries_1 --> createOrUpdateBatchProcessingTemplate_5
-  checkBatchTemplateExists_8 --> createOrUpdateBatchProcessingTemplate_5
-  getBatchProcessingTemplates_7 --> updateBatchTemplateActiveStatus_9
-  getBatchProcessingTemplates_7 --> deleteBatchProcessingTemplate_10
-```
-
-### Read operations
-
-#### `getBatchProcessingTemplates_7`
-
-List every BatchProcessingTemplate visible to the admin, each row carrying templateBatchId, isActive, isBatchActive, processingStartTime, userId, sendForReview, plus joined folder bindings (folderName/folderPathOrId/folderType/lastProcessedFileTime). No public Connect/Tooling alternative — the controller's joined-folder shape is non-reconstructable.
-
-**Call:** `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-batch-processing-templates`   — status: `implemented`
-
-#### `getBatchProcessingTemplate_6`
-
-Fetch one BatchProcessingTemplate by id (or DeveloperName), returning the same extractTemplateData shape as the list view: templateBatchId, isActive/isBatchActive, processingStartTime, userId, sendForReview, plus joined folders. AURA-IS-CANONICAL — controller wraps a service-layer join the raw DocumentExtractionDef sObject does not expose.
-
-**Call:** `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-batch-processing-template`   — status: `implemented`
-
-**Inputs:**
-
-- `batchTemplateId` *(`String`)*
-
-**Depends on:** `getBatchProcessingTemplates_7`
-
-#### `checkBatchTemplateExists_8`
-
-Probe DocumentExtractionDef by templateDeveloperName and return true only when the row exists AND IsBatchDefined=true. Pre-flight uniqueness gate before createOrUpdate. AURA-IS-CANONICAL — a raw SOQL probe would skip the IDP feature gate and the IsBatchDefined nullity check the controller enforces.
-
-**Call:** `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/check-batch-template-exists`   — status: `implemented`
-
-**Inputs:**
-
-- `templateDeveloperName` *(`String`)*
-
-#### `getLibraries_1`
-
-List ContentWorkspace records (libraries) eligible as document sources, after the controller's requireContentFolder(folderType) allowlist gate validates folderType against DocExtractDefFldrType (default Content_Folder when null). AURA-IS-CANONICAL — folderType allowlist is feature-specific, not present on generic content endpoints.
-
-**Call:** `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-libraries`   — status: `implemented`
-
-**Inputs:**
-
-- `folderType` *(`String`)*
-
-#### `getFolderItems_2`
-
-List items inside parentContentFolderId paged by offset+pageSize, after the same DocExtractDefFldrType allowlist gate. Returns entries (folder children). AURA-IS-CANONICAL — generic content data-provider lacks the feature-specific folderType filter.
-
-**Call:** `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-folder-items`   — status: `implemented`
-
-**Inputs:**
-
-- `parentContentFolderId` *(`String`)*
-- `offset` *(`Integer`)*
-- `pageSize` *(`Integer`)*
-- `folderType` *(`String`)*
-
-**Depends on:** `getLibraries_1`
-
-#### `getFolderItemsCount_3`
-
-Return the integer total of items under parentContentFolderId, after the DocExtractDefFldrType allowlist gate. Used to drive pagination-control state alongside getFolderItems_2. AURA-IS-CANONICAL — wraps the count with the IDP feature gate raw COUNT() bypasses.
-
-**Call:** `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-folder-items-count`   — status: `implemented`
-
-**Inputs:**
-
-- `parentContentFolderId` *(`String`)*
-- `folderType` *(`String`)*
-
-**Depends on:** `getLibraries_1`
-
-#### `getFolderLocationPath_4`
-
-Return the breadcrumb hierarchy from the root workspace down to contentFolderId as an ordered List<Map> (one entry per ancestor folder). Used to render the folder picker's location trail. AURA-IS-CANONICAL — service-layer breadcrumb composition is not reconstructable from raw ContentFolder parent walks.
-
-**Call:** `GET /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/get-folder-location-path`   — status: `implemented`
-
-**Inputs:**
-
-- `contentFolderId` *(`String`)*
-- `folderType` *(`String`)*
-
-**Depends on:** `getLibraries_1`
-
-### Write operations
-
-#### `createOrUpdateBatchProcessingTemplate_5`
-
-Atomically persist a BatchProcessingTemplate plus its folder bindings. All inputs are required; folders is List of {id, folderType} validated row-by-row against DocExtractDefFldrType. isUpdate=false inserts, true updates in place; existing folder lastProcessedFileTime is preserved. Returns {success, templateId, templateName, developerName, message}. AURA-IS-CANONICAL — the custom result shape and atomic template+folders write are non-reconstructable from raw sObject upsert.
-
-**Call:** `PATCH /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/create-or-update-batch-processing-template`   — status: `implemented`
-
-**Inputs:**
-
-- `templateId` *(`String`)*
-- `userId` *(`String`)*
-- `startDateTime` *(`String`)*
-- `reviewBeforeSave` *(`Boolean`)*
-- `folders` *(`List<Map<String, Object>>`)*
-- `isUpdate` *(`Boolean`)*
-
-**Depends on:** `getLibraries_1`, `checkBatchTemplateExists_8`
-
-#### `updateBatchTemplateActiveStatus_9`
-
-Toggle isBatchActive on the template at batchTemplateId. The controller re-reads after the write and throws when the persisted value does not equal the requested isActive — a built-in readback verify. Returns the extractTemplateData shape. AURA-IS-CANONICAL — readback equality check is not present in raw sObject UPDATE.
-
-**Call:** `PATCH /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/update-batch-template-active-status`   — status: `implemented`
-
-**Inputs:**
-
-- `batchTemplateId` *(`String`)*
-- `isActive` *(`Boolean`)*
-
-**Depends on:** `getBatchProcessingTemplates_7`
-
-### Destructive operations
-
-#### `deleteBatchProcessingTemplate_10`
-
-Delete the BatchProcessingTemplate at batchTemplateId. The service-layer deleteConfiguration cascades to BatchDocumentExtractionFolder child rows; void return. AURA-IS-CANONICAL — raw sObject DELETE on the parent does not reproduce the cascade nor the IDP feature-gate check.
-
-**Call:** `DELETE /headless/invoke/industries/industries-common/batch-intelligent-doc-extract-setup/delete-batch-processing-template`   — status: `implemented`
-
-**Inputs:**
-
-- `batchTemplateId` *(`String`)*
-
-**Depends on:** `getBatchProcessingTemplates_7`

package/skills/industries-behavioral-health-app-settings-configure/SKILL.md

@@ -1,71 +0,0 @@
----
-name: industries-behavioral-health-app-settings-configure
-description: "Use this skill when users want to read or toggle the org-level Behavioral Health App preference (ORG_PREFERENCE_BEHAVIORAL_HEALTH_APP_PREF) for Health Cloud — Setup > Platform Tools > Feature Settings > Health Cloud > Behavioral Health App Settings. Trigger when users mention behavioral, health, app, settings, behavioral health app settings."
-metadata:
-  version: "1.0"
-  accessCheck: "(UngroupedSettingAccessCheck.USER_PERMISSION_VIEW_SETUP) && (UngroupedSettingAccessCheck.USER_PERMISSION_CUSTOMIZE_APPLICATION) && (IndustriesSettingAccessCheck.ORG_PERMISSION_BEHAVIORAL_HEALTH_APP)"
----
-
-# Managing Behavioral Health App Settings
-
-## When to Use This Skill
-
-Read or toggle the org-level Behavioral Health App preference (ORG_PREFERENCE_BEHAVIORAL_HEALTH_APP_PREF) for Health Cloud — Setup > Platform Tools > Feature Settings > Health Cloud > Behavioral Health App Settings. Two operations on a single boolean: GET returns the current state, PATCH writes a new value. Both gated server-side by Customize Application + ViewSetup + the BehavioralHealthApp org permission (Health Cloud feature license); failure throws localized NoAccessException. Toggle additionally publishes a featurePref.enable / featurePref.disable PFT telemetry event for the Behavioral Health product feature taxonomy.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Caller must hold the Customize Application user permission (UngroupedSettingAccessCheck.USER_PERMISSION_CUSTOMIZE_APPLICATION); Behavioral Health setup access requires it on both read and toggle, throwing AuraHandledException with localized 'Global_Setup.NoAccessException' otherwise. (check: `USER_PERMISSION_CUSTOMIZE_APPLICATION`)
-- Org must have the BehavioralHealthApp org permission enabled (the Health Cloud feature license — StandardPermissionSet_force.BehavioralHealthApp); IndustriesSettingAccessCheck.ORG_PERMISSION_BEHAVIORAL_HEALTH_APP gates both methods. Without it the controller throws AuraHandledException; a Metadata API deploy of IndustriesSettings.enableBehavioralHealthAppPref also fails because the persistence layer enforces the same license. (check: `IndustriesSettingAccessCheck.ORG_PERMISSION_BEHAVIORAL_HEALTH_APP`)
-- Caller must have View Setup access (setupUtil.hasViewSetup()); without it both controller methods throw AuraHandledException before any pref read or write. (check: `setupUtil.hasViewSetup`)
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `toggleBehavioralHealthAppOrgPref_2`: call `verifyBehavioralHealthAppOrgPref_3` (`GET /headless/invoke/platform/behavioral-health-app-settings`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `getBehavioralHealthAppOrgPref_1` | read | implemented | `GET /headless/invoke/platform/behavioral-health-app-settings` | — |
-| `toggleBehavioralHealthAppOrgPref_2` | write | implemented | `PATCH /headless/invoke/platform/behavioral-health-app-settings/toggle-behavioral-health-app-org-pref` | `getBehavioralHealthAppOrgPref_1` |
-| `verifyBehavioralHealthAppOrgPref_3` | verify | implemented | `GET /headless/invoke/platform/behavioral-health-app-settings` | `toggleBehavioralHealthAppOrgPref_2` |
-
-### Read operations
-
-#### `getBehavioralHealthAppOrgPref_1`
-
-Reads ORG_PREFERENCE_BEHAVIORAL_HEALTH_APP_PREF. Gated by ViewSetup + Customize Application + BehavioralHealthApp org permission; denial throws AuraHandledException('Global_Setup.NoAccessException').
-
-**Call:** `GET /headless/invoke/platform/behavioral-health-app-settings`   — status: `implemented`
-
-### Write operations
-
-#### `toggleBehavioralHealthAppOrgPref_2`
-
-Writes ORG_PREFERENCE_BEHAVIORAL_HEALTH_APP_PREF; publishes featurePref.enable/disable PFT event for BEHAVIORAL_HEALTH_PRODUCT_FEATURE_ID. Same gate as read. SaveResult error → ServiceException. Returns void; re-call GET to read back.
-
-**Call:** `PATCH /headless/invoke/platform/behavioral-health-app-settings/toggle-behavioral-health-app-org-pref`   — status: `implemented`
-
-**Inputs:**
-
-- `value` *(`boolean`)*
-
-**Depends on:** `getBehavioralHealthAppOrgPref_1`
-
-### Verify operations
-
-#### `verifyBehavioralHealthAppOrgPref_3`
-
-Read-back via getBehavioralHealthAppOrgPref to confirm toggleBehavioralHealthAppOrgPref_2 persisted. Returns boolean — the same ORG_PREFERENCE_BEHAVIORAL_HEALTH_APP_PREF the toggle wrote; it should equal the value passed to the toggle.
-
-**Call:** `GET /headless/invoke/platform/behavioral-health-app-settings`   — status: `implemented`
-
-**Depends on:** `toggleBehavioralHealthAppOrgPref_2`

package/skills/industries-branch-management-settings-configure/SKILL.md

@@ -1,89 +0,0 @@
----
-name: industries-branch-management-settings-configure
-description: "Use this skill when users want to read and toggle Branch Management org preferences. Trigger when users mention branch, management, settings, branch management settings."
-metadata:
-  version: "1.0"
-  accessCheck: "(BranchManagementAccessCheck.ORG_HAS_BRANCH_MANAGEMENT) || (UngroupedSettingAccessCheck.USER_PERMISSION_CUSTOMIZE_APPLICATION)"
----
-
-# Managing Branch Management Settings
-
-## When to Use This Skill
-
-Read and toggle Branch Management org preferences. The BRANCH_ASSOCIATION_PREF enum currently exposes one member, associateAccountWithBranch (when on, records the user's branch on accounts they create or own). Read returns Map<prefName,Boolean>. Write takes (pref, enabled) where enabled is the ABSOLUTE target state, not a flip. CRITICAL: savePref is declared void, so a 200 with an empty body means only that the call was accepted — it is NOT proof the preference changed. An unrecognized pref name matches no enum member and returns an identical empty 200 while persisting nothing, so an agent MUST confirm every write by re-reading getBranchManagementPrefs. Pref matching is case-insensitive (equalsIgnoreCase). Access: reads need (View Setup OR View All Data) AND ORG_HAS_BRANCH_MANAGEMENT, else NoAccessException; writes need Customize Application AND ORG_HAS_BRANCH_MANAGEMENT, and when either is missing the call THROWS AuraHandledException rather than silently no-opping. No public Connect, Tooling, or Metadata alternative — the controller is canonical. Wire-verified 2026-09-01 against orgfarm-a557ae8f7b (API v66.0).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Org must have Branch Management enabled (ORG_HAS_BRANCH_MANAGEMENT feature gate). When off, both read and write throw NoAccessException.checkRequiredAccess / hasRequiredAccess. (check: `BranchManagementAccessCheck.ORG_HAS_BRANCH_MANAGEMENT`)
-- Caller must have View Setup or View All Data user permission to read the preferences. (check: `UngroupedSettingAccessCheck.USER_PERMISSION_VIEW_SETUP or USER_PERMISSION_VIEW_ALL_DATA`)
-- Caller must have Customize Application user permission to write a preference (savePref), in addition to ORG_HAS_BRANCH_MANAGEMENT. When either is missing, hasRequiredAccess throws AuraHandledException — it never returns false, and the write never silently no-ops. (check: `UngroupedSettingAccessCheck.USER_PERMISSION_CUSTOMIZE_APPLICATION`)
-
-**Operational rules:**
-
-- CANONICAL SEQUENCE — read, write, then re-read to verify.
-1. getBranchManagementPrefs_1 — returns {associateAccountWithBranch: <bool>}. Use it to learn the current state and to confirm access before writing.
-2. savePref_2 — pref='associateAccountWithBranch', enabled=<desired absolute state>.
-3. getBranchManagementPrefs_1 again — assert the returned value equals what you sent.
-Step 3 is MANDATORY, not optional. savePref returns void, so a successful write and a silently ignored write are indistinguishable on the wire: both return HTTP 200 with an empty body. The only value of `pref` that does anything is 'associateAccountWithBranch'; any other string, including a typo or an empty string, is ignored and still returns 200. Matching is case-insensitive, so 'ASSOCIATEACCOUNTWITHBRANCH' also works, but send the canonical casing.
-`enabled` is an absolute target state, not a toggle — send true to turn the preference on and false to turn it off. Do not send the inverse of the current value expecting a flip.
-If a write throws AuraHandledException, the caller is missing Customize Application or the org lacks Branch Management. Re-read to confirm nothing changed, then surface the permission gap rather than retrying.
-SCOPE — this Setup page exposes exactly one control, the associateAccountWithBranch toggle. Its other client-side handlers (init, toggleBranchAssociation) are UI wrappers over these same two controller methods and add no server-side behavior: init calls getBranchManagementPrefs on page load, and toggleBranchAssociation calls savePref then updates local component state and raises a success toast. There is no further agent-callable capability on this page.
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `savePref_2`: call `verify-save-pref` (`GET /headless/invoke/platform/branch-management-settings/get-branch-management-prefs`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `getBranchManagementPrefs_1` | read | implemented | `GET /headless/invoke/platform/branch-management-settings/get-branch-management-prefs` | — |
-| `savePref_2` | write | implemented | `PATCH /headless/invoke/platform/branch-management-settings/save-pref` | `getBranchManagementPrefs_1` |
-| `verify-save-pref` | verify | implemented | `GET /headless/invoke/platform/branch-management-settings/get-branch-management-prefs` | `savePref_2` |
-
-### Read operations
-
-#### `getBranchManagementPrefs_1`
-
-Returns Map<String,Boolean> of Branch Management prefs (currently only associateAccountWithBranch). Requires View Setup or View All Data + ORG_HAS_BRANCH_MANAGEMENT feature gate; else NoAccessException.
-
-**Call:** `GET /headless/invoke/platform/branch-management-settings/get-branch-management-prefs`   — status: `implemented`
-
-**Output:** Map<String,Boolean> keyed by BRANCH_ASSOCIATION_PREF prefName — one entry per enum member, currently only associateAccountWithBranch; each value is the current org-pref enabled state. The controller iterates the enum on every call, so the key set is fixed by the enum rather than by org configuration. Live-verified 2026-09-01 against orgfarm-a557ae8f7b (API v66.0): returned exactly {"associateAccountWithBranch": false} on an org with the preference off.
-
-### Write operations
-
-#### `savePref_2`
-
-Set a BRANCH_ASSOCIATION_PREF org pref. Matching is case-insensitive (equalsIgnoreCase) against the enum's prefName; an unrecognized name matches nothing and persists nothing while still returning 200. Returns void — the response never confirms persistence, so always re-read getBranchManagementPrefs to verify. Requires Customize Application AND ORG_HAS_BRANCH_MANAGEMENT; when either is missing hasRequiredAccess THROWS AuraHandledException rather than no-opping.
-
-**Call:** `PATCH /headless/invoke/platform/branch-management-settings/save-pref`   — status: `implemented`
-
-**Inputs:**
-
-- `pref` *(`String`)*
-- `enabled` *(`boolean`)*
-
-**Depends on:** `getBranchManagementPrefs_1`
-
-**Output:** Empty JSON object. savePref is declared void, so a 200 carries no payload and is NOT evidence that the preference persisted — an unrecognized pref name returns an identical empty 200 having changed nothing. Live-verified 2026-09-01 against orgfarm-a557ae8f7b (API v66.0): pref='totallyBogusPrefName' and pref='' each returned 200 {} and left associateAccountWithBranch unchanged, while pref='associateAccountWithBranch' returned the same 200 {} and did persist. Confirm every write by re-reading getBranchManagementPrefs.
-
-### Verify operations
-
-#### `verify-save-pref`
-
-Re-read getBranchManagementPrefs after savePref_2 and assert the returned value for the pref you wrote equals the `enabled` value you sent. REQUIRED, not optional: savePref is declared void and returns an empty 200 whether it persisted the change or silently ignored the request, so this read is the only signal that the write took effect. If the value did not change, the pref name matched no BRANCH_ASSOCIATION_PREF member — check it against the enum's single member, associateAccountWithBranch.
-
-**Call:** `GET /headless/invoke/platform/branch-management-settings/get-branch-management-prefs`   — status: `implemented`
-
-**Depends on:** `savePref_2`
-
-**Output:** Map<String,Boolean> — the same shape getBranchManagementPrefs_1 returns. Assert the associateAccountWithBranch entry equals the `enabled` value passed to savePref_2. Live-verified 2026-09-01 against orgfarm-a557ae8f7b (API v66.0): after writing true the read returned {"associateAccountWithBranch": true}; after writing false it returned {"associateAccountWithBranch": false}; after writing a bogus pref name it was unchanged.