/**
 * Per-harness on-disk targets for the `sklx agent install` / `uninstall`
 * commands (SMI-5456 Wave 1 Step 5).
 *
 * This module is pure data (no filesystem access) — it says WHERE each
 * harness's MCP config and hook config live and in what format, so
 * `agent-config-merge*.ts` can merge into them generically and
 * `agent-pack-installer.ts` doesn't hard-code per-harness path logic inline.
 *
 * Confidence levels (documented per plan's own Validation Ladder philosophy —
 * Level 2a/3 in docs/internal/implementation/smi-5456-skillsmith-agent-wave1.md
 * is explicitly where per-harness wire formats get confirmed against real
 * harness binaries; Step-6 eval-worker web-verification 2026-07-01 upgraded
 * three rows from the original Step-5 estimates):
 *   - claude-code, cursor, windsurf: HIGH — MCP config path/shape verified
 *     against `packages/cli/src/templates/mcp-server.template.snippets.ts`
 *     (SMI-4580, already shipped and used in docs/website).
 *   - cursor HOOK config specifically: was WRONG (Claude-shaped keys/entry
 *     values, contradicted by a live Cursor UAT report) until SMI-5893 Wave
 *     8a; now HIGH — re-verified 2026-08 against three independent fetches
 *     of cursor.com/docs/hooks. See {@link AGENT_HOOK_TARGETS}.cursor's own
 *     comment for the confirmed shape.
 *   - hermes: HIGH for the skill path + YAML config shape (spike report §(b),
 *     3 independent official doc pages agree); hooks are spike-verified
 *     ABSENT (no SessionStart equivalent) — {@link AGENT_HOOK_TARGETS}
 *     therefore carries no hook target for hermes.
 *   - codex: HIGH for the config file path (`~/.codex/config.toml`, same
 *     snippet table) AND — per Step-6 verification of
 *     developers.openai.com/codex/hooks — HIGH for the hook-registration
 *     shape: inline `[[hooks.SessionStart]]` / `[[hooks.SessionStart.hooks]]`
 *     array-of-tables carrying `{type, command, timeout, statusMessage}`.
 *     Codex has NO SessionEnd event, and its Stop event fires PER-TURN (not
 *     per-session) — see `installCodexHooks` in
 *     `agent-pack-installer.harness.ts` for why nothing is wired for cleanup.
 *   - copilot: HIGH — `~/.copilot/mcp-config.json`, top-level `mcpServers`
 *     key (Step-6 verified; the earlier `mcp.json` guess was wrong). Global,
 *     not VS Code's workspace `.vscode/mcp.json`, remains correct: Copilot
 *     CLI removed `.vscode/mcp.json` support, and `sklx agent install` is a
 *     global (not per-project) command.
 *   - opencode: HIGH — `~/.config/opencode/opencode.json` under the `mcp`
 *     key, entries typed `local|remote` (Step-6 verified against
 *     opencode.ai/docs; entry VALUE shape differs from the mcpServers
 *     convention — see `buildOpenCodeMcpEntryValue` in
 *     `agent-pack-installer.entry.ts`). Agent markdown lives at
 *     `~/.config/opencode/agents/` — plural (opencode.ai/docs/agents/; the
 *     earlier singular `agent/` guess was wrong).
 *   - antigravity (SMI-6275 Wave 5): HIGH — `.agents/mcp_config.json`,
 *     standard `mcpServers` object shape, verified 2026-08-30 via live web
 *     search against antigravity.google/docs/ide/mcp/ and
 *     antigravity.google/docs/cli/mcp/ (both explicitly document the
 *     workspace-local path and the shared global sibling
 *     `~/.gemini/config/mcp_config.json`, corroborated by two independent
 *     third-party sources — Google Cloud Community/Medium and a Composio
 *     how-to). NOT listed in {@link AGENT_MCP_TARGETS} below, unlike every
 *     other row in this list — see `McpHarnessId`'s own doc comment for why,
 *     and `agent-pack-installer.antigravity-mcp.ts` for the dedicated
 *     writer this wave adds instead.
 */
import type { HarnessId } from '../services/agent-pack/index.js';
/**
 * Harnesses that can receive an MCP server registration via
 * {@link AGENT_MCP_TARGETS}'s HOME-anchored `Record` shape (7 targets).
 *
 * `antigravity` is EXCLUDED here (SMI-6275 Wave 5) even though it is a
 * {@link HarnessId} member — its `.agents/mcp_config.json` is
 * WORKSPACE-anchored (relative to the workspace root Wave 4's
 * `resolveScopedSkillsDir()` resolves), not home-anchored like every other
 * `McpConfigTarget.path` in this file, so it structurally cannot be a value
 * in a `Record<McpHarnessId, McpConfigTarget>` whose every consumer
 * (`relocateUnderHome`, `agent-manifest-path-guard.ts`'s home-relative
 * suffix computation) assumes a home-anchored path. This is the same
 * structural reason Cursor got its own dedicated installer split
 * (`agent-pack-installer.cursor-mcp.ts`, SMI-6279 Wave 9) rather than a
 * generic-path `AGENT_MCP_TARGETS` entry — AntiGravity gets the same
 * treatment: `agent-pack-installer.antigravity-mcp.ts` owns its path
 * resolution + entry-value shape entirely outside this table.
 */
export type McpHarnessId = Exclude<HarnessId, 'antigravity'> | 'windsurf' | 'hermes';
/** Config-file format the merge helper must speak for a given target. */
export type ConfigFormat = 'json' | 'yaml' | 'toml-block';
/**
 * Where + how to merge the Skillsmith MCP server registration for one harness.
 *
 * `keyPath` is only meaningful for `format: 'json'` — the property path (from
 * the parsed document root) to the object the merge helper inserts
 * `skillsmith: {...}` into, creating intermediate objects as needed.
 * `format: 'toml-block'` targets ignore `keyPath` — see
 * `agent-config-merge.toml-block.ts` for the marker-delimited scheme.
 */
export interface McpConfigTarget {
    harness: McpHarnessId;
    path: string;
    format: ConfigFormat;
    keyPath: string[];
}
/** Where to write a named-agent shim file for a harness that has one. */
export interface ShimTarget {
    harness: HarnessId;
    /** Absolute file path the rendered shim content is written to verbatim. */
    path: string;
}
/**
 * Where to install a hook SCRIPT and how to wire it into that harness's hook
 * config. `configFormat`/`configPath`/`keyPath` follow the same shape as
 * {@link McpConfigTarget} so hook wiring reuses the same merge helpers.
 */
export interface HookInstallTarget {
    harness: 'claude-code' | 'cursor' | 'codex';
    /** Directory the hook script itself is copied into (chmod 0755). */
    scriptDir: string;
    configPath: string;
    configFormat: ConfigFormat;
    /** Key path to the array this hook's command entry is appended to. */
    sessionStartKeyPath: string[];
    sessionEndKeyPath: string[];
}
/** MCP registration targets for every harness the pack supports (PRD §3.1). */
export declare const AGENT_MCP_TARGETS: Readonly<Record<McpHarnessId, McpConfigTarget>>;
/**
 * Named-agent shim file targets, per {@link HarnessId} (PRD §3.1 constraint
 * 2 / architecture doc artifacts A2-A5). Cursor and (VS Code's) Copilot both
 * read `.claude/agents/*.md` natively per the constraint matrix, so they
 * share the claude-code shim file rather than getting a second copy — only
 * harnesses with their OWN native shim format get a dedicated target here.
 */
export declare const AGENT_SHIM_TARGETS: Readonly<Record<HarnessId, ShimTarget | null>>;
/** Hook install targets — only harnesses with a real SessionStart hook (HOOK_HARNESSES). */
export declare const AGENT_HOOK_TARGETS: Readonly<Record<'claude-code' | 'cursor' | 'codex', HookInstallTarget>>;
/** Codex's `[agents.skillsmith-agent]` TOML entry lives in the same config file as its MCP registration. */
export declare const CODEX_CONFIG_TOML_PATH: string;
//# sourceMappingURL=agent-harness-targets.d.ts.map