@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental 1.111.0 → 1.112.0

package/dist/.a4drules/skills/exploring-graphql-schema/SKILL.md

@@ -1,149 +0,0 @@
----
-name: exploring-graphql-schema
-description: Explore the Salesforce GraphQL schema via grep-only lookups. Use before generating any GraphQL query — schema exploration must complete first.
-paths:
-  - "**/*.ts"
-  - "**/*.tsx"
-  - "**/*.graphql"
----
-
-# Salesforce GraphQL Schema Exploration
-
-Guidance for AI agents working with the Salesforce GraphQL API schema. **GREP ONLY** — the schema file is very large (~265,000+ lines). All lookups MUST use grep; do NOT open, read, stream, or parse the file.
-
-## Deployment Prerequisites
-
-The schema reflects the **current org state**. Custom objects and fields appear only after metadata is deployed.
-
-- **Before** running `npm run graphql:schema`: Deploy all metadata (objects, permission sets, layouts) and assign the permission set to the target user. Invoke the `deploying-to-salesforce` skill for the full sequence.
-- **After** any metadata deployment: Re-run `npm run graphql:schema` and `npm run graphql:codegen` so types and queries stay in sync.
-
-## Schema File Location
-
-**Location:** `schema.graphql` at the **SFDX project root** (NOT inside the webapp dir). All grep commands **must be run from the project root** where `schema.graphql` lives.
-
-> ⚠️ **Important (Access Policy - GREP ONLY)**: Do NOT open, view, stream, paginate, or parse the schema with any tool other than grep. All lookups MUST be done via grep using anchored patterns with minimal context as defined below.
-
-If the file is not present, generate it by running (from the **webapp dir**, not the project root):
-
-```bash
-# Run from webapp dir (force-app/main/default/webapplications/<app-name>/)
-npm run graphql:schema
-```
-
-**BEFORE generating any GraphQL query, you MUST:**
-
-1. **Check if schema exists**: Look for `schema.graphql` in the **SFDX project root**
-2. **If schema is missing**:
-   - `cd` to the **webapp dir** and run `npm run graphql:schema` to download it
-   - Wait for the command to complete successfully
-   - Then proceed with grep-only lookups as defined below.
-3. **If schema exists**: Proceed with targeted searches as described below
-
-> ⚠️ **DO NOT** generate GraphQL queries without first having access to the schema. Standard field assumptions may not match the target org's configuration.
-
-## Schema Structure Overview
-
-Main entry points: `Query { uiapi }` for reads; `Mutation { uiapi(input: ...) }` for creates/updates/deletes. Record queries use `uiapi.query.<ObjectName>`.
-
-## Allowed Lookups (grep-only)
-
-Use ONLY these grep commands to locate specific definitions in schema.graphql. Do not use editors (VS Code/vim/nano), cat/less/more/head/tail, or programmatic parsers (node/python/awk/sed/jq).
-
-- Always include:
-  - `-n` (line numbers) and `-E` (extended regex)
-  - Anchors (`^`) and word boundaries (`\b`)
-  - Minimal context with `-A N` (prefer the smallest N that surfaces the needed lines)
-
-### 1. Find Available Fields for a Record Type
-
-Search for `type <ObjectName> implements Record` to find all queryable fields:
-
-```bash
-# Example: Find Account fields (anchored, minimal context)
-grep -nE '^type[[:space:]]+Account[[:space:]]+implements[[:space:]]+Record\b' ./schema.graphql -A 60
-```
-
-### 2. Find Filter Options for a Record Type
-
-Search for `input <ObjectName>_Filter` to find filterable fields and operators:
-
-```bash
-# Example: Find Account filter options (anchored)
-grep -nE '^input[[:space:]]+Account_Filter\b' ./schema.graphql -A 40
-```
-
-### 3. Find OrderBy Options
-
-Search for `input <ObjectName>_OrderBy` for sorting options:
-
-```bash
-# Example: Find Account ordering options (anchored)
-grep -nE '^input[[:space:]]+Account_OrderBy\b' ./schema.graphql -A 30
-```
-
-### 4. Find Mutation Operations
-
-Search for operations in `UIAPIMutations`:
-
-```bash
-# Example: Find Account mutations (extended regex)
-grep -nE 'Account.*(Create|Update|Delete)' ./schema.graphql
-```
-
-### 5. Find Input Types for Mutations
-
-Search for `input <ObjectName>CreateInput` or `input <ObjectName>UpdateInput`:
-
-```bash
-# Example: Find Account create input (anchored)
-grep -nE '^input[[:space:]]+AccountCreateInput\b' ./schema.graphql -A 30
-```
-
-## Agent Workflow for Building Queries (grep-only)
-
-**Pre-requisites (MANDATORY):**
-
-- [ ] Verified `schema.graphql` exists in the **SFDX project root**
-- [ ] If missing, ran `npm run graphql:schema` from the **webapp dir** and waited for completion
-- [ ] Confirmed connection to correct Salesforce org (if downloading fresh schema)
-
-**Workflow Steps:**
-
-1. **Identify the target object** (e.g., Account, Contact, Opportunity)
-2. **Run the "Find Available Fields" grep command** for your object (copy only the field names visible in the grep output; do not open the file)
-3. **Run the "Find Filter Options" grep command** (`<Object>_Filter`) to understand filtering options
-4. **Run the "Find OrderBy Options" grep command** (`<Object>_OrderBy`) for sorting capabilities
-5. **Build the query** following the patterns in the `generating-graphql-read-query` or `generating-graphql-mutation-query` skill using only values returned by grep
-6. **Validate field names** using grep matches (case-sensitive). Do not open or parse the file beyond grep.
-
-## Tips for Agents
-
-- **Always verify field names** by running the specific grep commands; do not open the schema file
-- **Use grep with anchors and minimal -A context** to explore the schema efficiently—never read or stream the file
-- **Check relationships** by looking for `parentRelationship` and `childRelationship` comments in type definitions
-- **Look for Connection types** (e.g., `AccountConnection`) via grep to understand pagination structure
-- **Custom objects** end with `__c` (e.g., `CustomObject__c`)
-- **Custom fields** also end with `__c` (e.g., `Custom_Field__c`)
-
-## Forbidden Operations
-
-To prevent accidental large reads, the following are prohibited for schema.graphql:
-
-- Opening in any editor (VS Code, vim, nano)
-- Using cat, less, more, head, or tail
-- Programmatic parsing (node, python, awk, sed, jq)
-- Streaming or paginating through large portions of the file
-
-If any of the above occurs, stop and replace the action with one of the Allowed Lookups (grep-only).
-
-## Output Minimization
-
-- Prefer precise, anchored patterns with word boundaries
-- Use the smallest `-A` context that surfaces required lines
-- If results are noisy, refine the regex rather than increasing context
-
-## Related Skills
-
-- For generating read queries, invoke the `generating-graphql-read-query` skill
-- For generating mutation queries, invoke the `generating-graphql-mutation-query` skill

package/dist/.a4drules/skills/fetching-rest-api/SKILL.md

@@ -1,167 +0,0 @@
----
-name: fetching-rest-api
-description: REST API usage via the Data SDK fetch method. Use when implementing Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM calls — only when GraphQL is not sufficient.
-paths:
-  - "**/*.ts"
-  - "**/*.tsx"
-  - "**/*.graphql"
----
-
-# Salesforce REST API via Data SDK Fetch
-
-Use `sdk.fetch` from the Data SDK when GraphQL is not sufficient. The SDK applies authentication, CSRF handling, and base URL resolution. **Always use optional chaining** (`sdk.fetch?.()`) and handle the case where `fetch` is not available.
-
-Invoke this skill when you need to call Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM endpoints.
-
-## API Version
-
-Use the project's API version. It is typically injected as `__SF_API_VERSION__`; fallback to `"65.0"`:
-
-```typescript
-declare const __SF_API_VERSION__: string;
-const API_VERSION = typeof __SF_API_VERSION__ !== "undefined" ? __SF_API_VERSION__ : "65.0";
-```
-
-## Base Path
-
-URLs are relative to the Salesforce API base. The SDK prepends the correct base path. Use paths starting with `/services/...`.
-
----
-
-## Chatter API
-
-User and collaboration data. No GraphQL equivalent.
-
-| Endpoint | Method | Purpose |
-| -------- | ------ | ------- |
-| `/services/data/v{version}/chatter/users/me` | GET | Current user (id, name, email, username) |
-
-```typescript
-const sdk = await createDataSDK();
-const response = await sdk.fetch?.(`/services/data/v${API_VERSION}/chatter/users/me`);
-
-if (!response?.ok) throw new Error(`HTTP ${response?.status}`);
-const data = await response.json();
-return { id: data.id, name: data.name };
-```
-
----
-
-## Connect REST API
-
-File and content operations.
-
-| Endpoint | Method | Purpose |
-| -------- | ------ | ------- |
-| `/services/data/v{version}/connect/file/upload/config` | GET | Upload config (token, uploadUrl) for file uploads |
-
-```typescript
-const sdk = await createDataSDK();
-const configRes = await sdk.fetch?.(`/services/data/v${API_VERSION}/connect/file/upload/config`, {
-  method: "GET",
-});
-
-if (!configRes?.ok) throw new Error(`Failed to get upload config: ${configRes?.status}`);
-const config = await configRes.json();
-const { token, uploadUrl } = config;
-```
-
----
-
-## Apex REST
-
-Custom Apex REST resources. Requires corresponding Apex classes in the org. CSRF protection is applied automatically for `services/apexrest` URLs.
-
-| Endpoint | Method | Purpose |
-| -------- | ------ | ------- |
-| `/services/apexrest/auth/login` | POST | User login |
-| `/services/apexrest/auth/register` | POST | User registration |
-| `/services/apexrest/auth/forgot-password` | POST | Request password reset |
-| `/services/apexrest/auth/reset-password` | POST | Reset password with token |
-| `/services/apexrest/auth/change-password` | POST | Change password (authenticated) |
-| `/services/apexrest/{resource}` | GET/POST | Custom Apex REST resources |
-
-**Example (login):**
-
-```typescript
-const sdk = await createDataSDK();
-const response = await sdk.fetch?.("/services/apexrest/auth/login", {
-  method: "POST",
-  body: JSON.stringify({ email, password, startUrl: "/" }),
-  headers: { "Content-Type": "application/json", Accept: "application/json" },
-});
-```
-
-Apex REST paths do not include the API version.
-
----
-
-## UI API (REST)
-
-When GraphQL cannot cover the use case. **Prefer GraphQL** when possible.
-
-| Endpoint | Method | Purpose |
-| -------- | ------ | ------- |
-| `/services/data/v{version}/ui-api/records/{recordId}` | GET | Fetch a single record |
-
-```typescript
-const sdk = await createDataSDK();
-const response = await sdk.fetch?.(`/services/data/v${API_VERSION}/ui-api/records/${recordId}`);
-```
-
----
-
-## Einstein LLM Gateway
-
-AI features. Requires Einstein API setup.
-
-| Endpoint | Method | Purpose |
-| -------- | ------ | ------- |
-| `/services/data/v{version}/einstein/llm/prompt/generations` | POST | Generate text from Einstein LLM |
-
-```typescript
-const sdk = await createDataSDK();
-const response = await sdk.fetch?.(`/services/data/v${API_VERSION}/einstein/llm/prompt/generations`, {
-  method: "POST",
-  headers: { "Content-Type": "application/json" },
-  body: JSON.stringify({
-    additionalConfig: { applicationName: "PromptTemplateGenerationsInvocable" },
-    promptTextorId: prompt,
-  }),
-});
-
-if (!response?.ok) throw new Error(`Einstein LLM failed (${response?.status})`);
-const data = await response.json();
-return data?.generations?.[0]?.text ?? "";
-```
-
----
-
-## General Pattern
-
-```typescript
-import { createDataSDK } from "@salesforce/sdk-data";
-
-const sdk = await createDataSDK();
-
-if (!sdk.fetch) {
-  throw new Error("Data SDK fetch is not available in this context");
-}
-
-const response = await sdk.fetch(url, {
-  method: "GET", // or POST, PUT, PATCH, DELETE
-  headers: { "Content-Type": "application/json", Accept: "application/json" },
-  body: method !== "GET" ? JSON.stringify(payload) : undefined,
-});
-
-if (!response.ok) throw new Error(`HTTP ${response.status}`);
-const data = await response.json();
-```
-
----
-
-## Reference
-
-- Parent: `accessing-data` — enforces Data SDK usage for all Salesforce data fetches
-- GraphQL: `using-graphql` — use for record queries and mutations when possible
-- `createRecord` from `@salesforce/webapp-experimental/api` for UI API record creation (uses SDK internally)

package/dist/.a4drules/skills/generating-graphql-mutation-query/SKILL.md

@@ -1,258 +0,0 @@
----
-name: generating-graphql-mutation-query
-description: Generate Salesforce GraphQL mutation queries. Use when the query to generate is a mutation query. Schema exploration must complete first — invoke exploring-graphql-schema first.
-paths:
-  - "**/*.ts"
-  - "**/*.tsx"
-  - "**/*.graphql"
----
-
-# Salesforce GraphQL Mutation Query Generation
-
-**Triggering conditions**
-
-1. Only if the schema exploration phase completed successfully (invoke `exploring-graphql-schema` first)
-2. Only if the query to generate is a mutation query
-
-## Schema Access Policy
-
-> ⚠️ **GREP ONLY** — During mutation generation you may need to verify field names, input types, or representations. All schema lookups **MUST** use the grep-only commands defined in the `exploring-graphql-schema` skill. Do NOT open, read, stream, or parse `./schema.graphql` with any tool other than grep.
-
-## Your Role
-
-You are a GraphQL expert. Generate Salesforce-compatible mutation queries. Schema exploration must complete first. If the schema exploration has not been executed yet, you **MUST** run the full exploration workflow from the `exploring-graphql-schema` skill first, then return here for mutation query generation.
-
-## Mutation Queries General Information
-
-The GraphQL engine supports `Create`, `Update`, and `Delete` operations. `Update` and `Delete` operate on Id-based entity identification. See the [mutation query schema](#mutation-query-schema) section.
-
-## Mutation Query Generation Workflow
-
-Strictly follow the rules below when generating the GraphQL mutation query:
-
-1. **Input Fields Validation** - Validate that the set of fields validate [input field constraints](#mutation-queries-input-field-constraints). Verify every field name and type against grep output from the schema — do NOT guess or assume
-2. **Output Fields Validation** - Validate that the set of fields used in the select part of the query validate the [output fields constraints](#mutation-queries-output-field-constraints)
-3. **Type Consistency** - Make sure variables used as query arguments and their related fields share the same GraphQL type. Verify types via grep lookup — do NOT assume types
-4. **Report Phase** - Use the [Mutation Query Report Template](#mutation-query-report-template) below to report on the previous validation phases
-5. **Input Arguments** - `input` is the default name for the argument, unless otherwise specified
-6. **Output Field** - For `Create` and `Update` operations, the output field is always named `Record`, and is of type EntityName
-7. **Field Name Validation** - Every field name in the generated mutation **MUST** match a field confirmed via grep lookup in the schema. Do NOT guess or assume field names exist
-8. **Query Generation** - Use the [mutation query](#mutation-query-templates) template and adjust it based on the selected operation
-9. **Output Format** - Use the [standalone](#mutation-standalone-default-output-format---clean-code-only)
-10. **Lint Validation** - After writing the mutation to a file, run `npx eslint <file>` from the webapp dir to validate it against the schema. Fix any reported errors before proceeding. See [Lint Validation](#lint-validation) for details
-11. **Test the Query** - Use the [Generated Mutation Query Testing](#generated-mutation-query-testing) workflow to test the generated query
-    1. **Report First** - Always output the generated mutation in the proper output format BEFORE initiating any test
-
-## Mutation Query Schema
-
-**Important**: In the schema fragments below, replace **EntityName** occurrences by the real entity name (i.e. Account, Case...).
-**Important**: `Delete` operations all share the same generic `Record` entity name for both input and payload, only exposing the standard `Id` field.
-
-```graphql
-input EntityNameCreateRepresentation {
-  # Subset of EntityName fields here
-}
-input EntityNameCreateInput { EntityName: EntityNameCreateRepresentation! }
-type EntityNameCreatePayload { Record: EntityName! }
-
-input EntityNameUpdateRepresentation {
-  # Subset of EntityName fields here
-}
-input EntityNameUpdateInput { Id: IdOrRef! EntityName: EntityNameUpdateRepresentation! }
-type EntityNameUpdatePayload { Record: EntityName! }
-
-input RecordDeleteInput { Id: IdOrRef! }
-type RecordDeletePayload { Id: ID }
-
-type UIAPIMutations {
-  EntityNameCreate(input: EntityNameCreateInput!): EntityNameCreatePayload
-  EntityNameDelete(input: RecordDeleteInput!): RecordDeletePayload
-  EntityNameUpdate(input: EntityNameUpdateInput!): EntityNameUpdatePayload
-}
-```
-
-## Mutation Queries Input Field Constraints
-
-1. **`Create` Mutation Queries**:
-   1. **MUST** include all required fields
-   2. **MUST** only include createable fields
-   3. Child relationships can't be set and **MUST** be excluded
-   4. Fields with type `REFERENCE` can only be assigned IDs through their `ApiName` name
-2. **`Update` Mutation Queries**:
-   1. **MUST** include the id of the entity to update
-   2. **MUST** only include updateable fields
-   3. Child relationships can't be set and **MUST** be excluded
-   4. Fields with type `REFERENCE` can only be assigned IDs through their `ApiName` name
-3. **`Delete` Mutation Queries**:
-   1. **MUST** include the id of the entity to delete
-
-## Mutation Queries Output Field Constraints
-
-1. **`Create` and `Update` Mutation Queries**:
-   1. **MUST** exclude all child relationships
-   2. **MUST** exclude all `REFERENCE` fields, unless accessed through their `ApiName` member (no navigation to referenced entity)
-   3. Inaccessible fields will be reported as part of the `errors` attribute in the returned payload
-   4. Child relationships **CAN'T** be queried as part of a mutation
-   5. Fields with type `REFERENCE` can only be queried through their `ApiName` (no referenced entities navigation, no sub fields)
-2. **`Delete` Mutation Queries**:
-   1. **MUST** only include the `Id` field
-
-## Mutation Query Report Template
-
-Input arguments:
-
-- Required fields: FieldName1 (Type1), FieldName2 (Type2)...
-- Other fields: FieldName3 (Type3)...
-  Output fields: FieldNameA (TypeA), FieldNameB (TypeB)...
-
-## Mutation Query Templates
-
-```graphql
-mutation mutateEntityName(
-  # arguments
-) {
-  uiapi {
-    EntityNameOperation(input: {
-      # the following is for `Create` and `Update` operations only
-      EntityName: {
-        # Input fields
-      }
-      # the following is for `Update` and `Delete` operations only
-      Id: ... # id here
-    }) {
-      # the following is for `Create` and `Update` operations only
-      Record {
-        # Output fields
-      }
-      # the following is for `Delete` operations only
-      Id: ... # id here
-    }
-  }
-}
-```
-
-## Mutation Standalone (Default) Output Format - CLEAN CODE ONLY
-
-```javascript
-import { gql } from '@salesforce/sdk-data';
-const QUERY_NAME = gql`
-  mutation mutateEntity($input: EntityNameOperationInput!) {
-    uiapi {
-      EntityNameOperation(input: $input) {
-        # select output fields here depending on operation type
-      }
-    }
-  }
-`;
-
-const QUERY_VARIABLES = {
-  input: {
-    // The following is for `Create` and `Update` operations only
-    EntityName: {
-      // variables here
-    },
-    // The following is for `Update` and `Delete` operations only
-    Id: ... // id here
-  }
-};
-```
-
-**❌ FORBIDDEN — Do NOT include any of the following:**
-
-- Explanatory comments about the query (inline or surrounding)
-- Field descriptions or annotations
-- Additional text about what the query does
-- Workflow step descriptions or summaries
-- Comments like `// fetches...`, `// creates...`, `/* ... */`
-
-**✅ ONLY output:**
-
-- The raw query string constant (using `gql` tagged template)
-- The variables object constant
-- Nothing else — no extra imports, no exports, no wrapper functions
-
-## Lint Validation
-
-After writing the generated mutation into a source file, validate it against the schema using the project's GraphQL ESLint setup:
-
-```bash
-# Run from webapp dir (force-app/main/default/webapplications/<app-name>/)
-npx eslint <path-to-file-containing-mutation>
-```
-
-**How it works:** The ESLint config uses `@graphql-eslint/eslint-plugin` with its `processor`, which extracts GraphQL operations from `gql` template literals in `.ts`/`.tsx` files and validates the extracted `.graphql` virtual files against `schema.graphql`.
-
-**Rules enforced:** `no-anonymous-operations`, `no-duplicate-fields`, `known-fragment-names`, `no-undefined-variables`, `no-unused-variables`
-
-**On failure:** Fix the reported issues, re-run `npx eslint <file>` until clean, then proceed to testing.
-
-> ⚠️ **Prerequisites**: The `schema.graphql` file must exist (invoke `exploring-graphql-schema` first) and project dependencies must be installed (`npm install`).
-
-## Generated Mutation Query Testing
-
-**Triggering conditions** — **ALL conditions must be true:**
-
-1. The [Mutation Query Generation Workflow](#mutation-query-generation-workflow) completed with status `SUCCESS` and you have a generated query
-2. The query is a mutation query
-3. A non-manual method was used during schema exploration to retrieve introspection data
-
-**Workflow**
-
-1. **Report Step** - State the exact method you will use to test (e.g., `sf api request graphql` from the **project root**, Connect API, etc.) — this **MUST** match the method used during schema exploration
-2. **Interactive Step** - Ask the user whether they want you to test the query using the proposed method
-   1. **STOP and WAIT** for the user's answer. Do NOT proceed until the user responds. Do NOT assume consent.
-3. **Input Arguments** - You **MUST** ask the user for the input argument values to use in the test
-   1. **STOP and WAIT** for the user's answer. Do NOT proceed until the user provides values. Do NOT fabricate test data.
-4. **Test Query** - Only if the user explicitly agrees and has provided input values:
-   1. Execute the mutation using the reported method (e.g., `sf api request rest` to POST the query and variables to the GraphQL endpoint):
-      ```bash
-      sf api request rest /services/data/v65.0/graphql \
-        --method POST \
-        --body '{"query":"mutation mutateEntity($input: EntityNameOperationInput!) { uiapi { EntityNameOperation(input: $input) { Record { Id } } } }","variables":{"input":{"EntityName":{"Field":"Value"}}}}'
-      ```
-   2. Replace `v65.0` with the API version of the target org
-   3. Replace the `query` value with the generated mutation query string
-   4. Replace the `variables` value with the user-provided input arguments
-5. **Result Analysis** - Retrieve the `data` and `errors` attributes from the returned payload, and report the result of the test as one of the following options:
-   1. `PARTIAL` if `data` is not an empty object, but `errors` is not an empty list - Explanation: some of the queried fields are not accessible on mutations
-   2. `FAILED` if `data` is an empty object - Explanation: the query is not valid
-   3. `SUCCESS` if `errors` is an empty list
-6. **Remediation Step** - If status is not `SUCCESS`, use the [`FAILED`](#failed-status-handling-workflow) or [`PARTIAL`](#partial-status-handling-workflow) status handling workflows
-
-### `FAILED` Status Handling Workflow
-
-The query is invalid:
-
-1. **Error Analysis** - Parse and categorize the specific error messages
-2. **Root Cause Identification** - Use error message to identify the root cause:
-   - **Execution** - Error contains `invalid cross reference id` or `entity is deleted`
-   - **Syntax** - Error contains `invalid syntax`
-   - **Validation** - Error contains `validation error`
-   - **Type** - Error contains `VariableTypeMismatch` or `UnknownType`
-   - **Navigation** - Error contains `is not currently available in mutation results`
-   - **API Version** - Query deals with updates, you're testing with Connect API and error contains `Cannot invoke JsonElement.isJsonObject()`
-3. **Targeted Resolution** - Depending on the root cause categorization
-   - **Execution** - You're trying to update or delete an unknown/no longer available entity: either create an entity first, if you have generated the related query, or ask for a valid entity id to use. **STOP and WAIT** for the user to provide a valid Id
-   - **Syntax** - Update the query using the error message information to fix the syntax errors
-   - **Validation** - The field name is most probably invalid. Re-run the relevant grep command from the `exploring-graphql-schema` skill to verify the correct field name. If still unclear, ask the user for clarification and **STOP and WAIT** for their answer
-   - **Type** - Use the error details and re-verify the type via grep lookup in the schema. Correct the argument type and adjust variables accordingly
-   - **Navigation** - Use the [`PARTIAL` status handling workflow](#partial-status-handling-workflow) below
-   - **API Version** - `Record` selection is only available with API version 64 and higher, **report** the issue, and try again with API version 64
-4. **Test Again** - Resume the [query testing workflow](#generated-mutation-query-testing) with the updated query (increment and track attempt counter)
-5. **Escalation Path** - If targeted resolution fails after 2 attempts, ask for additional details and restart the entire GraphQL workflow from the `exploring-graphql-schema` skill
-
-### `PARTIAL` Status Handling Workflow
-
-The query can be improved:
-
-1. Report the fields mentioned in the `errors` list
-2. Explain that these fields can't be queried as part of a mutation query
-3. Explain that the query might be considered as failing, as it will report errors
-4. Offer to remove the offending fields
-5. **STOP and WAIT** for the user's answer. Do NOT remove fields without explicit consent.
-6. If they are OK with removing the fields restart the [generation workflow](#mutation-query-generation-workflow) with the new field list
-
-## Related Skills
-
-- Schema exploration: `exploring-graphql-schema` (must complete first)
-- Read query generation: `generating-graphql-read-query`