/**
 * Amendment cross-check (FR2): do the ids an amendment claims match what the
 * requirements file actually defines?
 *
 * Two checks only, and both are data (AC-13) — they never fail a gate and never
 * change an exit code. The obvious third check, "a retired criterion no
 * amendment claims", was specified and then dropped: measured on this repo it
 * fires 44 times across 12 instances that have never been amended, which is
 * noise arriving before any signal (retired AC-12).
 *
 * Warnings from here surface in `aidlc amend` output alone (AC-74). Putting
 * them where the traceability warnings surface — `aidlc gate --json` and the
 * `criterionWarnings` block at `commands/transition.ts:408-419` — would have
 * changed output for every never-amended instance on the first run.
 *
 * Requirements: change-management/AC-10, AC-11, AC-13
 */
import type { ParsedRequirements } from '../traceability/types.js';
import type { Amendment } from './types.js';
/**
 * Cross-check one amendment's claimed ids against the AC definitions.
 *
 * @param amendment - The amendment under consideration.
 * @param parsed - Parsed requirements for the same file.
 * @returns Warnings, ordered `Retires:` then `Issues:`, ascending by id.
 */
export declare function crossCheck(amendment: Amendment, parsed: ParsedRequirements): string[];
//# sourceMappingURL=cross-check.d.ts.map