/**
 * artifact-retention — host-owned pruning of the per-tool artifact store.
 *
 * The host writes every scanner/baseline/catalog artifact through the
 * `writeArtifact` seam into `<project>/.runtime/artifacts/<tool>/<runId>/<name>`
 * (the substrate composes the `<runId>` segment; ADR-0090 Phase-0 decision 1).
 * Unbounded, that store would grow one run-dir per invocation forever. This
 * helper keeps the N most-recent run-dirs per tool and removes the rest.
 *
 * A separate, pure-IO testable unit (mirroring `atomic-artifact-write.ts` vs
 * `artifact-seams.ts`): the write seam calls it after a successful artifact
 * write, gated on the target living inside the artifact store. Every failure
 * path is defensive — a prune problem must NEVER fail the run, so nothing here
 * throws (the seam additionally wraps the call).
 */
/**
 * Default number of per-tool run-dirs retained when `cli.artifacts.keep` is not
 * set in `opensip-cli.config.yml`. MUST match the Zod default declared on
 * `cliConfigSchema.artifacts.keep` (in `@opensip-cli/config`); kept here as a
 * literal because the config layer cannot import from the cli layer.
 */
export declare const DEFAULT_ARTIFACT_RETENTION_KEEP = 10;
/**
 * In-flight grace window (A12): a run-dir whose mtime is within this many ms of
 * `now` is NEVER evicted, regardless of its rank past `keep`.
 *
 * A slow CONCURRENT same-tool run creates its dir at scan start and only appends
 * to the report inside it — directory mtime is set at creation and report appends
 * do NOT bump it — so under load that dir can rank below `keep` while the peer is
 * still scanning. A naive rank-only prune would `rmSync` it mid-scan, faulting the
 * peer with a spurious `artifactValid=false`. The window MUST be >= the scanner
 * process budget (`DEFAULT_TIMEOUT_MS` = 300_000 ms in the substrate run loop): a
 * run cannot legitimately be in flight longer than its timeout, so any dir older
 * than this is guaranteed finished and safe to prune. Kept a literal (with a
 * margin over the substrate timeout) because the cli layer must not import the
 * substrate; the comment is the sync point.
 */
export declare const ARTIFACT_INFLIGHT_GRACE_MS: number;
/** Options for {@link pruneArtifactRetention}'s in-flight-safety floor (A12). */
export interface PruneRetentionOptions {
    /** `Date.now()` by default; injectable for deterministic tests. */
    readonly now?: number;
    /** The current run's dir name (== `runId`) — never pruned even if it ranks low. */
    readonly currentRunId?: string;
}
/**
 * Prune `<artifactsDir>/<tool>` down to the `keep` most-recent run-dirs.
 *
 * Run-dirs are ordered newest-first by mtime (tie-broken by name, descending,
 * for determinism); everything past the first `keep` is removed
 * (`rmSync({ recursive: true, force: true })`). Defensive throughout:
 *   - missing tool dir → no-op;
 *   - `keep <= 0` (or non-finite) → treated as disabled, no-op;
 *   - a failed removal is swallowed (best-effort) and never propagated.
 *
 * A12 in-flight safety: a dir is RANK-INDEPENDENTLY retained when it is the
 * current run's own dir (`opts.currentRunId`) or its mtime is within
 * {@link ARTIFACT_INFLIGHT_GRACE_MS} of `now` — a peer run that could still be
 * scanning is never deleted out from under it, regardless of how it ranks.
 */
export declare function pruneArtifactRetention(tool: string, artifactsDir: string, keep: number, opts?: PruneRetentionOptions): void;
//# sourceMappingURL=artifact-retention.d.ts.map