/**
 * kiro hook installer: own-file v1 hooks in .kiro/hooks/aidlc-cost.json.
 *
 * Kiro v1 hooks (IDE 1.0 / CLI 3.0+) are standalone JSON files, so install
 * is a file write and remove is a delete — no merge risk. `Stop` fires per
 * response (no session-end event exists); the recorder's cursor + lock make
 * repeated firings cheap no-ops (design §4.2, D2).
 *
 * Kiro CLI 2.x uses a different hook format and is out of scope for v1.
 */
import { type HookStatus } from './claude-code.js';
/**
 * Install the kiro cost hooks.
 *
 * Same change as the claude-code installer and for the same reason: the command
 * used to embed absolute paths to node and the CLI frozen at install time, which
 * any username, machine, or `nvm` change invalidated silently
 * (cost-capture-goes-dark/AC-1). Fixing only claude-code would have left the
 * identical defect here — this project's own lesson is that a bug report naming
 * one call site is a sample, not the population.
 *
 * Kiro sets no documented project-root variable, so the invocation falls back to
 * `.`; kiro runs hooks from the project root, and `AIDLC_PROJECT_ROOT` overrides
 * it for any host that does not.
 */
export declare function installKiroHooks(projectRoot: string, nodePath: string, cliPath: string): void;
export declare function removeKiroHooks(projectRoot: string): void;
export declare function kiroHookStatus(projectRoot: string): HookStatus;
//# sourceMappingURL=kiro.d.ts.map