import { type BaseStepContract } from "audit-tools/shared";
import { type RemediationStep, type RemediationStepKind, type RemediationStepStatus } from "./types.js";
export interface WriteStepInput {
    stepKind: RemediationStepKind;
    status: RemediationStepStatus;
    runId: string;
    repoRoot: string;
    artifactsDir: string;
    prompt: string;
    allowedCommands?: string[];
    stopCondition: string;
    artifactPaths?: Record<string, string>;
}
/**
 * Write the remediation step contract. Delegates to the shared
 * `writeStepContract` (drift-plan R3) which owns the steps/ filenames, mkdir,
 * prompt write, atomic current-step.json write, the forward-slash normalization
 * of ALL host-facing path fields, and the canonical-paths-win merge. This
 * wrapper only supplies the remediation contract version, the remediation
 * `step_kind` enum, and the trim-leading-whitespace behaviour remediation
 * prompts rely on.
 */
export declare function writeCurrentStep({ stepKind, status, runId, repoRoot, artifactsDir, prompt, allowedCommands, stopCondition, artifactPaths, }: WriteStepInput): Promise<RemediationStep>;
/**
 * Write the terminal blocked step the CLI's fatal backstop emits (backlog:
 * abnormal-exit no-step-contract). Remediate's DRAW of the shared blocked-step
 * assembly (`writeBlockedStepContract` in audit-tools/shared — semantics in
 * `runWithBlockedStepBackstop`): this wrapper supplies only the per-mode
 * inputs — the remediation contract version and the minted run id (same shape
 * as nextStep.ts's `randomRunId`, inlined because importing it would cycle
 * stepWriter → nextStep → stepWriter; there may be no loadable state to read a
 * real run id from when the backstop fires).
 */
export declare function writeBlockedStep(params: {
    root: string;
    artifactsDir: string;
    reason: string;
}): Promise<BaseStepContract>;
//# sourceMappingURL=stepWriter.d.ts.map