/**
 * Registration Integrity Floor MCP Tool — spec 2026-07-09, Task 10.
 *
 * Tool: pica_integrity_waive
 *
 * Flagged spec deviation (documented in the plan's Global Constraints and
 * the PR body): the design proposed NO new MCP tool for the floor — Tasks
 * 3-9 only enrich existing write-tool responses with integrity pressure
 * (see integrity-hints.ts). Waiving a gap has no existing tool vehicle, so
 * this is the one new surface. The connector-visible discover/execute
 * surface (pica_discover / pica_tool_details / pica_execute) is otherwise
 * unchanged — this tool is just one more entry in the taxonomy.
 *
 * Mirrors mcp-server/src/tools/custody.ts for file structure (small,
 * single-tool file, PicaClient constructor injection) AND
 * for the confirm-gate precedent — pica_custody_reconcile's `confirm`
 * boolean (executes only when confirm === true). Here the gate is a
 * refusal rather than a dry-run: refuse client-side, before any SDK call,
 * telling the agent to ask the user first, when confirm !== true.
 */
import { PicaClient } from "@withpica/mcp-sdk";
import type { ToolDefinition, ToolExecutor } from "./index.js";
export declare class IntegrityTools {
    private pica;
    constructor(pica: PicaClient);
    getTools(): Array<{
        definition: ToolDefinition;
        executor: ToolExecutor;
    }>;
    private waive;
}
//# sourceMappingURL=integrity.d.ts.map