@salesforce/afv-skills 1.63.0 → 1.65.0

package/skills/experience-apex-pages-configure/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: experience-apex-pages-configure
+description: "Use this skill when users want to manage Visualforce Apex Pages (key prefix `066`) via the Tooling sObject API. Trigger when users mention apex, pages, apex pages."
+metadata:
+  version: "1.0"
+  accessCheck: "UserPermissions.ViewSetup"
+---
+
+# Managing Apex Pages
+
+## When to Use This Skill
+
+Manage Visualforce Apex Pages (key prefix `066`) via the Tooling sObject API. UDD
+`sobjectFamily="TOOLING"` blocks standard sObject CRUD; Metadata API CRUD is
+documented-broken on FullName (BI-EDS udd/216/ApexPage.entity.xml line 22). Tooling
+sObject is the only working programmatic surface.
+
+- List: `GET /services/data/v66.0/tooling/query?q=SELECT ... FROM ApexPage` —
+  filterable on Name, MasterLabel, NamespacePrefix, ApiVersion, ControllerType.
+- Read one: `GET /services/data/v66.0/tooling/sobjects/ApexPage/{id}` — returns
+  full record incl. Markup, Metadata (ApexPageDescriptor), NamespacePrefix.
+- Create: `POST /services/data/v66.0/tooling/sobjects/ApexPage` with required
+  body `{Name, MasterLabel, ApiVersion, Markup}`.
+
+Required-on-create: `Name` (DeveloperName, ≤80), `MasterLabel` (≤80), `ApiVersion`
+(DOUBLE, scale=1), `Markup` (CLOB, ≤1,048,576 chars). `ControllerType` is the
+`ApexPageControllerType` enum (Standard | Custom | Extension) — first-class on
+create when binding the page to a controller. Update (PATCH) and delete
+(DELETE) on `/sobjects/ApexPage/{id}` exist in the Tooling REST contract but
+are dropped from this SOR by the producer-merge layer; see `notes.coverage_gap`.
+
+## Workflow
+
+Workflow: list_ApexPage_1 (SOQL filter to find a page by Name / MasterLabel /
+ControllerType) → get_ApexPage_1 by Id (returns full Markup + Metadata) →
+create_ApexPage_1 with required `{Name, MasterLabel, ApiVersion, Markup}`.
+Read steps are independent — call get_ApexPage_1 directly when the Id is
+already known.
+
+## Critical Constraints
+
+**Preconditions:**
+
+- Org must have Apex Pages enabled (`Apex Pages enabled` feature gate). Without this org-level setting the Tooling REST surface returns no rows / refuses writes regardless of user permissions. (check: `Apex Pages enabled`)
+- Read access requires `OrgPermissions.AuthorApexPages` plus `UserPermissions.ViewSetup` (the Tooling per-API-access tuple on the ApexPage entity). (check: `UserPermissions.ViewSetup`)
+- Create / update / delete requires `Customize Application permission` (entity `editAccess` on ApexPage). (check: `Customize Application permission`)
+
+**Destructive operations — require explicit user confirmation:**
+
+- **`delete_ApexPage_1`** — Delete a ApexPage record by Id via the Tooling/sObject API. The {id} path parameter is the record Id.
+  - Rollback: No automatic rollback.
+
+## Operations Reference
+
+Operations grouped by purpose. Use these as the building blocks for the workflows above.
+
+### Summary
+
+| Operation | Purpose | Status | Call | Depends on |
+|-----------|---------|--------|------|------------|
+| `list_ApexPage_1` | read | — | `query.ApexPage` | — |
+| `get_ApexPage_1` | read | — | `sobjects/ApexPage/{id}` | — |
+| `create_ApexPage_1` | write | — | `sobjects/ApexPage` | — |
+| `update_ApexPage_1` | write | — | `sobjects/ApexPage/{id}` | — |
+| `delete_ApexPage_1` | delete | — | `sobjects/ApexPage/{id}` | — |
+
+### Read operations
+
+#### `list_ApexPage_1`
+
+SOQL over ApexPage via Tooling. Filter on Name (DeveloperName), MasterLabel, NamespacePrefix, ApiVersion, ControllerType. Markup is large (≤1MB) — project explicitly when needed. Paginate via nextRecordsUrl when totalSize > 2000.
+
+**Call:** `query.ApexPage`
+
+**Output:** Tooling QueryResult: {totalSize: int, done: bool, nextRecordsUrl: string|null, records: [{Id (066…), Name, MasterLabel, ApiVersion, ControllerType, NamespacePrefix, ManageableState, CreatedDate, LastModifiedDate, ...projected}]}. done=false → call nextRecordsUrl to continue paging.
+
+#### `get_ApexPage_1`
+
+Get one ApexPage by Id (key prefix 066). Returns the full record including Markup (≤1MB CLOB), MasterLabel, ApiVersion (DOUBLE), ControllerType (`ApexPageControllerType` enum: Standard | Custom | Extension), Metadata (ApexPageDescriptor), NamespacePrefix. 404 NOT_FOUND when the Id is unknown.
+
+**Call:** `sobjects/ApexPage/{id}`
+
+**Output:** Full ApexPage record: {Id (066…), Name (DeveloperName, ≤80), MasterLabel (≤80), ApiVersion (DOUBLE), Markup (CLOB ≤1,048,576 chars), ControllerType (ApexPageControllerType enum: Standard|Custom|Extension), ControllerKey, NamespacePrefix, ManageableState, IsAvailableInTouch (bool), CreatedDate, LastModifiedDate, SystemModstamp, Metadata (ApexPageDescriptor — Tooling-only), FullName (Tooling-only)}.
+
+### Write operations
+
+#### `create_ApexPage_1`
+
+POST a new ApexPage. Required body fields: `Name` (DeveloperName, ≤80), `MasterLabel` (≤80), `ApiVersion` (DOUBLE), `Markup` (CLOB ≤1,048,576). Optional: `ControllerType` (ApexPageControllerType enum), `ControllerKey`, `Description`. Returns Tooling SaveResult `{id, success, errors[]}` plus a Location header pointing at `/sobjects/ApexPage/{id}`.
+
+**Call:** `sobjects/ApexPage`
+
+**Output:** Tooling SaveResult: {id: string (066…, the new ApexPage Id), success: bool, errors: [{statusCode, message, fields[]}]}. On success the response Location header carries `/services/data/v66.0/tooling/sobjects/ApexPage/{id}`. On REQUIRED_FIELD_MISSING / DUPLICATE_DEVELOPER_NAME / INVALID_FIELD, errors[] is populated and success=false.
+
+#### `update_ApexPage_1`
+
+Update a ApexPage record by Id via the Tooling/sObject API. The {id} path parameter is the record Id; body fields replace existing values.
+
+**Call:** `sobjects/ApexPage/{id}`
+
+### Destructive operations
+
+#### `delete_ApexPage_1`
+
+Delete a ApexPage record by Id via the Tooling/sObject API. The {id} path parameter is the record Id.
+
+**Call:** `sobjects/ApexPage/{id}`

package/skills/experience-app-home-configure/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: experience-app-home-configure
+description: "Use this skill when users want to app Manager Setup page. Trigger when users mention app, home, app home."
+metadata:
+  version: "1.0"
+---
+
+# Managing App Home
+
+## When to Use This Skill
+
+App Manager Setup page. Three operations against CustomApplication Tooling records: list the App Manager picker categories (TabSetType API name to display label), delete a CustomApplication (logs an AppManagerListView audit record; returns null when caller lacks Customize Application), and upgrade a Classic CustomApplication to Lightning (clones plus optionally copies per-profile ProfileActionOverride rows). All steps AURA-IS-CANONICAL: no public Connect, Tooling, or Metadata equivalent reproduces the audit side-effect, permission-aware return, or the composite clone-plus-profile-copy.
+
+## Workflow
+
+Three independent steps; no required ordering. get-list-views returns picker labels (no caller input). delete-app and upgrade-app each take a CustomApplication id sourced externally (Tooling SOQL on CustomApplication, or the page's loaded row set). All require Customize Application user permission.
+
+## Critical Constraints
+
+**Destructive operations — require explicit user confirmation:**
+
+- **`delete-app`** — Delete the CustomApplication identified by id. Logs an AppManagerListView audit record on success; returns null instead of the id when caller lacks Customize Application. AURA-IS-CANONICAL: raw Tooling DELETE loses the audit side-effect and the permission-aware null return.
+  - 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 |
+|-----------|---------|--------|------|------------|
+| `get-list-views` | read | implemented | `GET /headless/invoke/platform/app-home` | — |
+| `delete-app` | delete | implemented | `DELETE /headless/invoke/platform/app-home/delete-app` | — |
+| `upgrade-app` | write | implemented | `PATCH /headless/invoke/platform/app-home/upgrade-app` | — |
+
+### Read operations
+
+#### `get-list-views`
+
+Return the App Manager list-view picker as a map of TabSetType API name to display label (e.g. AllApps, Classic, Lightning) that scopes which CustomApplication rows the page renders.
+
+**Call:** `GET /headless/invoke/platform/app-home`   — status: `implemented`
+
+**Notes:** adoption_note: Approved for agent serving. Returns the App Manager list-view picker as a map of TabSetType API name to display label (no caller input, no side effects), and carries a correct, unmasked permission gate that rejects unauthorized callers outright. The endpoint contract is sound and functional; approved for serving so it lands in the routes-jar regen.
+
+### Write operations
+
+#### `upgrade-app`
+
+Clone the source Classic CustomApplication (id) to a new Lightning CustomApplication with the supplied label/developerName; asserts source UiType is not already Lightning. When preserveProfileSetting=true, copies per-profile ProfileActionOverride entries. AURA-IS-CANONICAL: composite clone-plus-profile-copy has no public equivalent.
+
+**Call:** `PATCH /headless/invoke/platform/app-home/upgrade-app`   — status: `implemented`
+
+**Inputs:**
+
+- `id` *(`String`)* — Value for the id field.
+- `label` *(`String`)* — Value for the label field.
+- `developerName` *(`String`)* — Name of the developer.
+- `preserveProfileSetting` *(`boolean`)* — Toggle the preserve profile setting preference on or off.
+
+**Notes:** reject_on_attestation: Two-sided mutation: creates a new app cloned from the source app's metadata AND mutates the old app in place, plus copies permission-set assignments to the new app. Its only guard against a malformed invocation is not reliably enforced at runtime, so it cannot be relied on to reject one. Permission-gated but never live-validated for this node, with no natural way to read back and confirm the result afterward. Identical implementation independently gated to reject_on_attestation for the sibling NavigationMenus node on the same grounds. Too high-blast-radius and hard-to-reverse for autonomous invocation without human attestation.; masking_bug_pointer: Same pattern as delete-app: on any failure — a permission denial or any other error — this step returns a generic, uninformative error rather than one identifying the real problem. A headless caller cannot distinguish "access denied" from "clone failed" from any other failure via the error message alone.
+
+### Destructive operations
+
+#### `delete-app`
+
+Delete the CustomApplication identified by id. Logs an AppManagerListView audit record on success; returns null instead of the id when caller lacks Customize Application. AURA-IS-CANONICAL: raw Tooling DELETE loses the audit side-effect and the permission-aware null return.
+
+**Call:** `DELETE /headless/invoke/platform/app-home/delete-app`   — status: `implemented`
+
+**Inputs:**
+
+- `id` *(`String`)*
+
+**Notes:** reject_on_attestation: Irreversible delete that also removes the app's per-profile visibility and its utility-bar and icon configuration, with no natural way to read back and confirm the result afterward. Permission-gated, but never live-validated for this node. Identical implementation independently gated to reject_on_attestation for the sibling NavigationMenus node on the same grounds. Do not auto-invoke; require explicit human attestation per invocation pending live E2E confirmation.; masking_bug_pointer: On any failure — including a permission denial — this step returns a generic, uninformative error rather than one identifying the real problem, so a caller cannot tell an access-denial apart from any other failure. The served description's claim that this step "returns null" on a permission failure is also inaccurate: null is returned only when the target app record is not found, never on permission denial.

package/skills/experience-aura-lightning-out-access-configure/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: experience-aura-lightning-out-access-configure
+description: "Use this skill when users want to manage the AuraLightningOutAccess org preference, which gates whether Aura components can be served through Lightning Out (the cross-org embed surface for Aura). Trigger when users mention aura, lightning, out, access, aura lightning out access."
+metadata:
+  version: "1.0"
+  accessCheck: "OrgPermissions.AuraLightningOutPermission"
+---
+
+# Managing Aura Lightning Out Access
+
+## When to Use This Skill
+
+Manage the AuraLightningOutAccess org preference, which gates whether Aura components can be served through Lightning Out (the cross-org embed surface for Aura). Two operations: read the current boolean state, then flip it on/off. The PATCH response echoes the new state, so the caller does not need a follow-up read to confirm persistence. Caller must hold the AuraLightningOutPermission org permission (UDD access check Lightning Out settings access).
+
+## Workflow
+
+Org-wide preference gating whether Aura components can be served through Lightning Out (the cross-org Aura embed surface). Canonical flow: read the current boolean via the GET step, then PATCH the desired value; the write response echoes the post-update isPreferenceEnabled, so no follow-up read is needed. Writes require the AuraLightningOutPermission org permission — without it the PATCH returns 401 INSUFFICIENT_ACCESS "Cannot update preference value!" (distinct from an OAuth/token failure, which differs by errorCode). Reads are ungated. Send desiredState as the boolean; an empty body returns 400 "Invalid desiredState passed!".
+
+## Critical Constraints
+
+**Preconditions:**
+
+- Caller must hold the AuraLightningOutPermission org permission; the setup page's UDD access check userCanAccessAuraLightningOutSettings gates read/write of this preference. (check: `OrgPermissions.AuraLightningOutPermission`)
+
+## 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 | — | `checkPreference` | — |
+| `setOrgPreferences_1` | write | — | `updatePreference` | `isOrgPreferenceEnabled_wire_2` |
+
+### Read operations
+
+#### `isOrgPreferenceEnabled_wire_2`
+
+Read whether the AuraLightningOutAccess org preference is currently enabled. Response field isPreferenceEnabled is the boolean.
+
+**Call:** `checkPreference`
+
+**Output:** PreferenceCheckOutputRepresentation with one field: isPreferenceEnabled (boolean) — true when AuraLightningOutAccess is currently enabled for the org, false otherwise.
+
+### Write operations
+
+#### `setOrgPreferences_1`
+
+Set the AuraLightningOutAccess org preference to the new boolean value. Response echoes the post-update isPreferenceEnabled, confirming persistence without an extra read.
+
+**Call:** `updatePreference`
+
+**Depends on:** `isOrgPreferenceEnabled_wire_2`
+
+**Output:** PreferenceCheckOutputRepresentation echoing the new state: isPreferenceEnabled (boolean) is the value of AuraLightningOutAccess after the update — equals desiredState on success.
+
+**Notes:** error_contracts: [{'status': 400, 'errorCode': 'BAD_REQUEST', 'message_pattern': 'Invalid desiredState passed!', 'when': 'Request body is empty or omits the desiredState field.', 'body_shape': '[{"errorCode":"BAD_REQUEST","message":"Invalid desiredState passed!"}]'}, {'status': 401, 'errorCode': 'INSUFFICIENT_ACCESS', 'message_pattern': 'Cannot update preference value!', 'when': 'Caller lacks the AuraLightningOutPermission org permission. Distinguish from an OAuth-token failure by the errorCode + message combination (a bad token would return AUTH_ERROR or 401 with a different message).', 'body_shape': '[{"errorCode":"INSUFFICIENT_ACCESS","message":"Cannot update preference value!"}]'}, {'status': 405, 'errorCode': 'METHOD_NOT_ALLOWED', 'when': 'A verb other than GET, HEAD, or PATCH is used against this path.', 'body_shape': '[{"errorCode":"METHOD_NOT_ALLOWED","message":"HTTP Method ... not allowed. Allowed are GET,HEAD,PATCH"}]'}]

package/skills/experience-briefcase-configure/SKILL.md

@@ -0,0 +1,287 @@
+---
+name: experience-briefcase-configure
+description: "Use this skill when users want to manage Briefcase Definitions for offline mobile data priming. Trigger when users mention briefcase."
+metadata:
+  version: "1.0"
+  accessCheck: "(Briefcase.userCanEditBriefcase) || (Briefcase.userCanViewBriefcase)"
+---
+
+# Managing Briefcase
+
+## When to Use This Skill
+
+Manage Briefcase Definitions for offline mobile data priming. This setup page lets admins create, edit, activate/deactivate, and delete Briefcase definitions that control which records are cached on mobile devices for offline use. It also manages briefcase rule configurations, user/profile assignments, connected app associations, and profile-level briefcase regeneration. Use this SOR when a user needs to configure offline data availability for Salesforce mobile apps.
+
+## Critical Constraints
+
+**Preconditions:**
+
+- User must have Briefcase EditBriefcase access (check: `Edit Briefcase permission`)
+- User must have Briefcase ViewBriefcase access (check: `View Briefcase permission`)
+
+**Destructive operations — require explicit user confirmation:**
+
+- **`delete-briefcase-tooling`** — Permanently delete a Briefcase definition by its Salesforce ID via the Tooling API.
+  - Rollback: Cannot be undone — the Briefcase definition and all its rules/assignments are permanently removed
+
+## Verification Checklist
+
+After every write operation, confirm the effect by re-reading state:
+
+- After `get-briefcase-list-and-guardrail-org-values`: call `verify-acknowledge-hyperforce` (`GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values`)
+- After `create-briefcase-tooling`: call `verify-create-briefcase-tooling` (`GET /services/data/v67.0/tooling/query`)
+- After `update-briefcase-tooling`: call `verify-update-briefcase-tooling` (`GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`)
+- After `update-briefcase-state-tooling`: call `verify-update-briefcase-state-tooling` (`GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`)
+- After `delete-briefcase-tooling`: call `verify-delete-briefcase-tooling` (`GET /services/data/v67.0/tooling/query`)
+- After `update-briefcase-assignments-sobject`: call `verify-update-briefcase-assignments-sobject` (`GET /services/data/v67.0/query`)
+
+## Operations Reference
+
+Operations grouped by purpose. Use these as the building blocks for the workflows above.
+
+### Summary
+
+| Operation | Purpose | Status | Call | Depends on |
+|-----------|---------|--------|------|------------|
+| `update-briefcase-connected-apps` | write | implemented | `PATCH /headless/invoke/platform/briefcase/update-briefcase-connected-apps` | — |
+| `get-apps-list-for-briefcase` | read | implemented | `GET /headless/invoke/platform/briefcase/get-apps-list-for-briefcase` | — |
+| `get-briefcase-list-and-guardrail-org-values` | read | implemented | `GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values` | — |
+| `acknowledge-hyperforce-for-high-volume-priming` | write | implemented | `PATCH /headless/invoke/platform/briefcase/acknowledge-hyperforce-for-high-volume-priming` | — |
+| `get-briefcase` | read | implemented | `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | — |
+| `verify-acknowledge-hyperforce` | verify | implemented | `GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values` | `get-briefcase-list-and-guardrail-org-values` |
+| `create-briefcase-tooling` | write | implemented | `POST /services/data/v67.0/tooling/sobjects/BriefcaseDefinition` | `get-briefcase-list-and-guardrail-org-values`, `get-apps-list-for-briefcase` |
+| `verify-create-briefcase-tooling` | verify | implemented | `GET /services/data/v67.0/tooling/query` | `create-briefcase-tooling` |
+| `update-briefcase-tooling` | write | implemented | `PATCH /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `get-briefcase-list-and-guardrail-org-values` |
+| `verify-update-briefcase-tooling` | verify | implemented | `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `update-briefcase-tooling` |
+| `update-briefcase-state-tooling` | write | implemented | `PATCH /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `get-briefcase-list-and-guardrail-org-values` |
+| `verify-update-briefcase-state-tooling` | verify | implemented | `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `update-briefcase-state-tooling` |
+| `delete-briefcase-tooling` | delete | implemented | `DELETE /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `get-briefcase-list-and-guardrail-org-values` |
+| `verify-delete-briefcase-tooling` | verify | implemented | `GET /services/data/v67.0/tooling/query` | `delete-briefcase-tooling` |
+| `update-briefcase-assignments-sobject` | write | implemented | `POST /services/data/v67.0/sobjects/BriefcaseAssignment` | `get-briefcase-list-and-guardrail-org-values` |
+| `verify-update-briefcase-assignments-sobject` | verify | implemented | `GET /services/data/v67.0/query` | `update-briefcase-assignments-sobject` |
+
+### Dependency graph
+
+```mermaid
+graph TD
+  update_briefcase_connected_apps["update-briefcase-connected-apps (write)"]
+  get_apps_list_for_briefcase["get-apps-list-for-briefcase (read)"]
+  get_briefcase_list_and_guardrail_org_values["get-briefcase-list-and-guardrail-org-values (read)"]
+  acknowledge_hyperforce_for_high_volume_priming["acknowledge-hyperforce-for-high-volume-priming (write)"]
+  get_briefcase["get-briefcase (read)"]
+  verify_acknowledge_hyperforce["verify-acknowledge-hyperforce (verify)"]
+  create_briefcase_tooling["create-briefcase-tooling (write)"]
+  verify_create_briefcase_tooling["verify-create-briefcase-tooling (verify)"]
+  update_briefcase_tooling["update-briefcase-tooling (write)"]
+  verify_update_briefcase_tooling["verify-update-briefcase-tooling (verify)"]
+  update_briefcase_state_tooling["update-briefcase-state-tooling (write)"]
+  verify_update_briefcase_state_tooling["verify-update-briefcase-state-tooling (verify)"]
+  delete_briefcase_tooling["delete-briefcase-tooling (delete)"]
+  verify_delete_briefcase_tooling["verify-delete-briefcase-tooling (verify)"]
+  update_briefcase_assignments_sobject["update-briefcase-assignments-sobject (write)"]
+  verify_update_briefcase_assignments_sobject["verify-update-briefcase-assignments-sobject (verify)"]
+  get_briefcase_list_and_guardrail_org_values --> verify_acknowledge_hyperforce
+  get_briefcase_list_and_guardrail_org_values --> create_briefcase_tooling
+  get_apps_list_for_briefcase --> create_briefcase_tooling
+  create_briefcase_tooling --> verify_create_briefcase_tooling
+  get_briefcase_list_and_guardrail_org_values --> update_briefcase_tooling
+  update_briefcase_tooling --> verify_update_briefcase_tooling
+  get_briefcase_list_and_guardrail_org_values --> update_briefcase_state_tooling
+  update_briefcase_state_tooling --> verify_update_briefcase_state_tooling
+  get_briefcase_list_and_guardrail_org_values --> delete_briefcase_tooling
+  delete_briefcase_tooling --> verify_delete_briefcase_tooling
+  get_briefcase_list_and_guardrail_org_values --> update_briefcase_assignments_sobject
+  update_briefcase_assignments_sobject --> verify_update_briefcase_assignments_sobject
+```
+
+### Read operations
+
+#### `get-apps-list-for-briefcase`
+
+Get apps list for briefcase.
+
+**Call:** `GET /headless/invoke/platform/briefcase/get-apps-list-for-briefcase`   — status: `implemented`
+
+#### `get-briefcase-list-and-guardrail-org-values`
+
+Get briefcase list and guardrail org values.
+
+**Call:** `GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values`   — status: `implemented`
+
+#### `get-briefcase`
+
+Retrieve a single Briefcase definition by its ID via the Tooling API. Returns full Metadata including briefcaseRules, filters, and relatedRules.
+
+**Call:** `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
+
+**Inputs:**
+
+- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to retrieve. Source: query BriefcaseDefinition sObject or output of get-briefcase-list-and-guardrail-org-values.
+
+**Output:** String representation of the Briefcase definition including masterLabel, developerName, description, id, active, type, briefcaseRules, assignments, connectedAppIds, syncStatus
+
+### Write operations
+
+#### `update-briefcase-connected-apps`
+
+Update briefcase connected apps.
+
+**Call:** `PATCH /headless/invoke/platform/briefcase/update-briefcase-connected-apps`   — status: `implemented`
+
+**Inputs:**
+
+- `briefcaseData` *(`Map<String, Object>`)* — Value for briefcase data.
+
+#### `acknowledge-hyperforce-for-high-volume-priming`
+
+Acknowledge hyperforce for high volume priming.
+
+**Call:** `PATCH /headless/invoke/platform/briefcase/acknowledge-hyperforce-for-high-volume-priming`   — status: `implemented`
+
+#### `create-briefcase-tooling`
+
+Create a new Briefcase definition with rules, assignments, and connected app associations via the Tooling API. The Metadata field accepts the full BriefcaseDefinition shape including briefcaseRules and filters.
+
+**Call:** `POST /services/data/v67.0/tooling/sobjects/BriefcaseDefinition`   — status: `implemented`
+
+**Inputs:**
+
+- `FullName` *(`String`)* — The developer name (unique identifier) for the Briefcase definition.
+- `Metadata` *(`Object`)* — BriefcaseDefinition metadata. Required fields: masterLabel (string), briefcaseRules (array, at least one rule). Each BriefcaseRule requires: targetEntity (API name of the sObject, e.g. 'Account'), queryScope (allowed values: 'Everything', 'Mine'; additionally 'AssignedToMe' is supported only for the ServiceAppointment entity — source: BriefcaseRule.QueryScope restrictedPicklist). Optional rule fields: briefcaseRuleFilters (array — each filter requires targetEntityField, filterOperator (short form: 'e'=equals, 's'=startsWith, 'd'=endsWith, 'l'=lessThan, 'g'=greaterThan, 'm'=lessThanOrEqual, 'h'=greaterThanOrEqual; NOTE: 'n'=notEquals is NOT supported for Briefcase filters — source: BriefcaseRuleFilter.FilterOperator restrictedPicklist), filterValue, filterSeqNumber (required, 1-based index)), filterLogic (REQUIRED when briefcaseRuleFilters present, e.g. '1' or '1 AND 2'), isAscendingOrder (boolean), orderBy (field name), recordLimit (integer), relatedRules (array of nested related rules — each requires targetEntity, queryScope, relationshipField, relationshipType; relationshipType is 'ParentToChild' for parent→child lookups or 'ChildToParent' for child→parent lookups — source: BriefcaseRule.RelationshipType restrictedPicklist; multiple relatedRules under one parent rule are supported). Operator+field compatibility is validated server-side — not all operators work with all field types (error: 'The combination of the field X and the operator Y for the entity Z is invalid'). Optional top-level: description (string), isActive (boolean, default false), type ('Standard' (default) or 'HighVolume' — source: BriefcaseDefinition.Type restrictedPicklist; MobileAppSync excluded for agent use).
+
+**Depends on:** `get-briefcase-list-and-guardrail-org-values`, `get-apps-list-for-briefcase`
+
+**Rollback:** Delete the created Briefcase using delete-briefcase-tooling with the record Id
+
+#### `update-briefcase-tooling`
+
+Update an existing Briefcase definition's metadata (label, description, rules, filters) via the Tooling API. Note that PATCH requires the full Metadata object (complete replacement, not partial).
+
+**Call:** `PATCH /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
+
+**Inputs:**
+
+- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to update. Source: query BriefcaseDefinition sObject or output of get-briefcase-list-and-guardrail-org-values.
+- `Metadata` *(`Object`)* — Full BriefcaseDefinition metadata (complete replacement): masterLabel, description, briefcaseRules, isActive. Must include all fields — omitted fields revert to defaults.
+
+**Depends on:** `get-briefcase-list-and-guardrail-org-values`
+
+**Rollback:** Call update-briefcase-tooling again with the previous field values retrieved from get-briefcase
+
+#### `update-briefcase-state-tooling`
+
+Activate or deactivate a Briefcase definition by updating the isActive flag in its Metadata via the Tooling API.
+
+**Call:** `PATCH /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
+
+**Inputs:**
+
+- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition. Source: query BriefcaseDefinition sObject.
+- `Metadata` *(`Object`)* — Full Metadata with isActive set to true (activate) or false (deactivate). Must include briefcaseRules and masterLabel even for state-only changes (full replacement semantics).
+
+**Depends on:** `get-briefcase-list-and-guardrail-org-values`
+
+**Rollback:** Call update-briefcase-state-tooling with the opposite active value to revert
+
+#### `update-briefcase-assignments-sobject`
+
+Manage Briefcase assignments by creating or deleting BriefcaseAssignment records. Each record links a BriefcaseDefinition to a user, group, or profile. Create one record per assignee; delete to unassign.
+
+**Call:** `POST /services/data/v67.0/sobjects/BriefcaseAssignment`   — status: `implemented`
+
+**Inputs:**
+
+- `BriefcaseId` *(`String`)* — The ID of the BriefcaseDefinition to assign.
+- `UserOrGroupId` *(`String`)* — Polymorphic reference — the ID of the User, Group, or Profile to assign. Accepts any of the three entity types in a single field.
+
+**Depends on:** `get-briefcase-list-and-guardrail-org-values`
+
+**Rollback:** DELETE /services/data/v67.0/sobjects/BriefcaseAssignment/{id} to remove the assignment
+
+### Verify operations
+
+#### `verify-acknowledge-hyperforce`
+
+Check whether the org has acknowledged Hyperforce AND actually has HighVolume capacity enabled. Reads briefcaseHyperforceAck flag and HighVolume guardrail limits from get-briefcase-list-and-guardrail-org-values output. If ack is true but limits are 0, the org does not support HighVolume — do NOT proceed.
+
+**Call:** `GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values`   — status: `implemented`
+
+**Depends on:** `get-briefcase-list-and-guardrail-org-values`
+
+#### `verify-create-briefcase-tooling`
+
+Confirm the new Briefcase was created by querying via Tooling SOQL.
+
+**Call:** `GET /services/data/v67.0/tooling/query`   — status: `implemented`
+
+**Inputs:**
+
+- `q` *(`string`)*
+
+**Depends on:** `create-briefcase-tooling`
+
+#### `verify-update-briefcase-tooling`
+
+Confirm the Briefcase update landed by re-reading the definition via Tooling API.
+
+**Call:** `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
+
+**Inputs:**
+
+- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to verify. Source: the id used in update-briefcase-tooling.
+
+**Depends on:** `update-briefcase-tooling`
+
+#### `verify-update-briefcase-state-tooling`
+
+Confirm activation/deactivation by re-reading the BriefcaseDefinition via Tooling API.
+
+**Call:** `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
+
+**Inputs:**
+
+- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to verify. Source: the id used in update-briefcase-state-tooling.
+- `fields` *(`string`)*
+
+**Depends on:** `update-briefcase-state-tooling`
+
+#### `verify-delete-briefcase-tooling`
+
+Confirm deletion by querying via Tooling SOQL and verifying the entry is gone.
+
+**Call:** `GET /services/data/v67.0/tooling/query`   — status: `implemented`
+
+**Inputs:**
+
+- `developerName` *(`String`)* — The DeveloperName of the BriefcaseDefinition to verify was deleted. Source: the developerName of the record passed to delete-briefcase-tooling.
+- `q` *(`string`)*
+
+**Depends on:** `delete-briefcase-tooling`
+
+#### `verify-update-briefcase-assignments-sobject`
+
+Confirm assignment changes by querying BriefcaseAssignment via SOQL.
+
+**Call:** `GET /services/data/v67.0/query`   — status: `implemented`
+
+**Inputs:**
+
+- `q` *(`string`)*
+
+**Depends on:** `update-briefcase-assignments-sobject`
+
+### Destructive operations
+
+#### `delete-briefcase-tooling`
+
+Permanently delete a Briefcase definition by its Salesforce ID via the Tooling API.
+
+**Call:** `DELETE /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
+
+**Inputs:**
+
+- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to delete. Source: query BriefcaseDefinition sObject.
+
+**Depends on:** `get-briefcase-list-and-guardrail-org-values`
+
+**Rollback:** Cannot be undone — the Briefcase definition and all its rules/assignments are permanently removed

package/skills/experience-community-flexi-page-list-create/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: experience-community-flexi-page-list-create
+description: "Use this skill when users want to browse and manage FlexiPage records that drive Experience Cloud (Communities) Builder pages — the records whose Type sits in the FlexiPageType.Container=COMMUNITIES subset (CommObjectPage, CommRecordPage, CommLoginPage, CommThemeLayoutPage, CommSearchResultPage, etc.). Trigger when users mention community, flexi, page, list, community flexi page list."
+metadata:
+  version: "1.0"
+---
+
+# Managing Community Flexi Page List
+
+## When to Use This Skill
+
+Browse and manage FlexiPage records that drive Experience Cloud (Communities) Builder pages — the records whose Type sits in the FlexiPageType.Container=COMMUNITIES subset (CommObjectPage, CommRecordPage, CommLoginPage, CommThemeLayoutPage, CommSearchResultPage, etc.). The Aloha Setup page at view_url renders this list filtered server-side; for programmatic CRUD use the Tooling sObject FlexiPage (read-flexi-page-list, read-flexi-page, write-flexi-page). Page-content edits are authored in the Lightning App Builder, not by direct sObject PATCH on the record's Metadata field. Org gates: Experience Cloud sites enabled, Experience Cloud pages enabled; user gates: view Experience Cloud pages (read), create Experience Cloud pages (write).
+
+## Critical Constraints
+
+**Preconditions:**
+
+- Networks (Experience Sites / Communities) feature must be enabled on the org. (check: `Experience Cloud sites enabled || Experience Cloud sites enabled`)
+- FlexiPage feature must be enabled for Communities on the org. (check: `Experience Cloud pages enabled`)
+- Org must NOT be a Help-Center-Networks-only org (the page is hidden in that mode). (check: `!Help Center networks-only mode`)
+- User must hold View Setup to load the page; Customize Application (or equivalent) is needed for write/delete row actions and Tooling FlexiPage CRUD. (check: `UserPermissions.ViewSetup; view Experience Cloud pages; create Experience Cloud pages (writes)`)
+
+## Operations Reference
+
+Operations grouped by purpose. Use these as the building blocks for the workflows above.
+
+### Summary
+
+| Operation | Purpose | Status | Call | Depends on |
+|-----------|---------|--------|------|------------|
+| `view_CommunityFlexiPageList_1` | read | — | `CommunityFlexiPageList.view` | — |
+| `read-flexi-page-list` | read | — | `GET /services/data/v66.0/tooling/query` | — |
+| `read-flexi-page` | read | — | `GET /services/data/v66.0/tooling/sobjects/FlexiPage/{id}` | `read-flexi-page-list` |
+| `write-flexi-page` | write | — | `POST /services/data/v66.0/tooling/sobjects/FlexiPage` | — |
+
+### Read operations
+
+#### `view_CommunityFlexiPageList_1`
+
+Open the Aloha Setup list view at view_url (PlatformTools > FeatureSettings > Networks). Renders FlexiPage records with FlexiPageType.Container=COMMUNITIES, with row-level Edit (App Builder) and Delete actions. For programmatic record access use steps read-flexi-page-list, read-flexi-page, write-flexi-page.
+
+**Call:** `CommunityFlexiPageList.view`
+
+#### `read-flexi-page-list`
+
+List Community FlexiPage records via Tooling SOQL filtered to FlexiPageType.Container=COMMUNITIES. Sibling FlexiPageList SOR's list_FlexiPage_1 is the unfiltered analog.
+
+**Call:** `GET /services/data/v66.0/tooling/query`
+
+**Output:** QueryResult.records[] of FlexiPage rows: Id, DeveloperName, MasterLabel, Type, NamespacePrefix, LastModifiedDate. The agent should call Tooling.describe(FlexiPage).Type for the authoritative community subset rather than relying on this step's hard-coded WHERE list, since the Container=COMMUNITIES set evolves across releases. Note LastModifiedById is not a valid FlexiPage column on the Tooling entity — resolve the actor via a follow-up SOQL against User if needed.
+
+#### `read-flexi-page`
+
+Read a single FlexiPage record by Id via the Tooling sObject API. Apply this once the agent has an Id from read-flexi-page-list or another source.
+
+**Call:** `GET /services/data/v66.0/tooling/sobjects/FlexiPage/{id}`
+
+**Depends on:** `read-flexi-page-list`
+
+**Output:** Tooling FlexiPage record. GET without ?fields returns the full record: Id, FullName, DeveloperName, MasterLabel, Type, Description, NamespacePrefix, ManageableState, ParentFlexiPage, EntityDefinitionId, LastModifiedDate, LastModifiedById, CreatedDate, SystemModstamp, plus the load-bearing Metadata sub-object. Metadata carries masterLabel, type, sobjectType, description, events[], flexiPageRegions[], parentFlexiPage, platformActionlist, quickActionList, template, and urls. flexiPageRegions[] elements carry name, type (Region), mode, appendable, prependable, replaceable, and itemInstances[] (each with a componentInstance authored via the Lightning App Builder — do not construct these from prose). template.name references an existing platform-bundled template (for example one:utilityBarTemplateDesktop on UtilityBar records, or flexipage:defaultTemplate on Community pages). To project a smaller payload, append ?fields=Id,MasterLabel,Type,...
+
+### Write operations
+
+#### `write-flexi-page`
+
+Create or update a Community-context FlexiPage record via the Tooling sObject API. On POST the wire contract requires a top-level FullName and a Metadata sub-object; Metadata must carry masterLabel, type (a FlexiPageType value in the COMMUNITIES subset — for example CommObjectPage or CommRecordPage), a non-empty flexiPageRegions[] array, and template.name referencing an existing platform-bundled template. sobjectType is set on record-page-type variants (for example CommObjectPage with sobjectType Account). PATCH also requires the Metadata sub-object — sending just top-level scalar field updates without Metadata returns 400 REQUIRED_FIELD_MISSING. The item-instance component graph inside flexiPageRegions[] is authored in the Lightning App Builder after this step provisions the record — do not synthesize componentInstance bodies from prose.
+
+**Call:** `POST /services/data/v66.0/tooling/sobjects/FlexiPage`
+
+**Output:** Tooling sObject create response — { id, success, errors[] } — on POST, and an empty 204 on PATCH. On create, only the shell record is provisioned; the flexiPageRegions[].itemInstances[] component graph is authored later in the Lightning App Builder. Verify the record shape post-write by calling read-flexi-page with the returned Id.
+
+**Rollback:** Delete the created FlexiPage via DELETE /services/data/v66.0/tooling/sobjects/FlexiPage/{id}. Confirmed reachable — DELETE on a non-existent Id returns 404 NOT_FOUND with a well-formed error body, so the surface exists and is idempotent from the caller's perspective. No separate rollback step is emitted because deletion is not a first-class customer workflow for this SOR — it is the undo verb for a mistaken create.
+
+**Notes:** patch_semantics: PATCH requires the full Metadata sub-object. Sending a partial Metadata does not merge with the persisted body — always read the current record first, mutate in-memory, and PATCH the full Metadata to avoid dropping fields.; fullname_immutability: FullName is set once on POST and is the record's stable developer-name identifier. Renaming requires deleting and recreating.; invalid_type_returns_500: An invalid FlexiPage type value (a string outside the FlexiPageType enum) returns 500 UNKNOWN_EXCEPTION rather than a validated 400 — this is a Core defect surface, not a documented contract. Agents constructing type values should pick from the community subset enumerated in agent_description.; empty_region_array_rejected: Metadata.flexiPageRegions must be a non-empty array. An empty [] is rejected with 400 "Required field is missing: flexiPageRegions" even though the key is present.; template_name_must_exist: Metadata.template.name must reference an existing platform-bundled template FullName. Templates are not created via this SOR.