/**
 * MetaHarness MCP Tools — ADR-150 Phase-2 deep-integration surface.
 *
 * Exposes the static-analysis MetaHarness CLIs as first-class MCP tools
 * so Claude Code agents can call them programmatically without shelling
 * out themselves. Five tools, all read-only / subprocess-isolated:
 *
 *   - metaharness_score          5-dim readiness scorecard
 *   - metaharness_genome         7-section categorical report
 *   - metaharness_mcp_scan       static MCP security findings
 *   - metaharness_threat_model   enterprise-grade threat model
 *   - metaharness_oia_audit      composite audit (score + threat + mcp) → memory
 *
 * ADR-153 Darwin Mode integration adds three additional tools that target
 * the separate `@metaharness/darwin` npm package (not the umbrella):
 *
 *   - metaharness_evolve         mutate harness policy surfaces, sandbox-score, promote
 *   - metaharness_security_bench upstream's "Darwin Shield" (their own ADR-155)
 *   - metaharness_bench          create/verify bench suites used by evolve --bench
 *
 * @metaharness/redblue integration adds one tool that targets the standalone
 * `@metaharness/redblue` npm package — adversarial red/blue LLM testing
 * for the agents and apps you own:
 *
 *   - metaharness_redblue        red-team → judge → blue-patch → retest → report
 *
 * metaharness@0.3.0 + @metaharness/darwin@0.8.0 add two more:
 *
 *   - metaharness_learn          upstream ADR-235 GEPA learning run ($0 dry-run
 *                                default; run=true to spend; needs repo checkout)
 *   - metaharness_gepa           GEPA library surface — genome load/validate/
 *                                render + transcript failure analysis
 *
 * Every tool resolves the corresponding plugin script
 * (`plugins/ruflo-metaharness/scripts/<X>.mjs`) via the same locator
 * the commands/metaharness.ts dispatcher uses, then spawns it with
 * `--format json` and parses the response.
 *
 * ADR-150 ARCHITECTURAL CONSTRAINT
 * --------------------------------
 * This file has ZERO static `@metaharness/*` imports. All metaharness
 * invocation stays in the plugin scripts behind the `_harness.mjs`
 * subprocess bridge. When the plugin scripts aren't reachable at
 * runtime, each tool returns a structured `{ degraded: true }` payload
 * — never throws.
 *
 * @module @claude-flow/cli/mcp-tools/metaharness
 */
import type { MCPTool } from './types.js';
export declare const metaharnessTools: MCPTool[];
//# sourceMappingURL=metaharness-tools.d.ts.map