/**
 * Copyright (c) 2026, Salesforce, Inc.,
 * All rights reserved.
 * For full license text, see the LICENSE.txt file
 */
import { type DeleteSpec, type ToolOutput } from "./types.js";
import { type PrimeDeps } from "../lib/prime-schema.js";
/**
 * Build a UIAPI delete mutation against a Salesforce org. Implements
 * `sf_gql_delete` intent for the graphiti MCP server (FR-5.7).
 *
 * Unlike create/update, delete is uniform across SObjects:
 * - The input type is the schema-wide `RecordDeleteInput!`, NOT an
 *   `<Object>`-specific input. Every `<Object>Delete` mutation field
 *   accepts the same `RecordDeleteInput!` carrying the record `Id`.
 * - The result is a `RecordDeletePayload` exposing only `Id` (a plain
 *   `ID`, not a value wrapper), so the selection is always `Id` and
 *   there is no `Record` sub-path — hence no `returnFields`.
 *
 * Implicit behaviors not visible in the signature:
 * - `inputVariable` defaults to `"input"`, declared as
 *   `$<name>: RecordDeleteInput!`. A leading `$` is stripped.
 * - Operation name defaults to `Delete<Object>` (e.g. `DeleteAccount`).
 *
 * Throws on invalid `object`, `inputVariable`, or `operationName` (must be
 * valid GraphQL Names), auth-missing, or introspection failure (via
 * `getSchemaWithPriming`); never throws on validation or codegen
 * failure (those surface as `warnings[]`).
 */
export declare function buildDelete(spec: DeleteSpec, deps?: PrimeDeps): Promise<ToolOutput>;