/**
 * `aidlc amend <instance>` — record a mid-instance requirements change and
 * reopen the phases it invalidated (FR5).
 *
 * Two modes. `--impact` is read-only: it parses the amendment, cross-checks the
 * ids it claims, walks every remaining citation and prints them. The write path
 * additionally validates the amendment's `Reopens:` field and rewrites phase
 * state, and it is the most destructive write in the framework — it clears
 * `completed_at`/`completed_by` on completed phases — so it carries the
 * protections the transition path carries: a live claim, a printed plan before
 * any write, `--confirm` from testing onwards, and an idempotence marker.
 *
 * Every exit path emits the same `--json` envelope with an error code drawn from
 * a closed set (AC-77). An error shape invented per branch is what makes `--json`
 * unparseable by anything downstream.
 *
 * One refusal reads the impact walk: a write that would leave a completed phase
 * citing a retired criterion is stopped (`uncovered-citation`). The walk still
 * never chooses what is reopened — see `change/coverage.ts`.
 *
 * Requirements: change-management/AC-30, AC-31, AC-34, AC-35, AC-36, AC-43,
 * AC-60, AC-64, AC-67, AC-68, AC-74, AC-76, AC-77, AC-86, AC-90, AC-91;
 * amend-cannot-reopen-current-phase/AC-3, AC-4, AC-5, AC-8, AC-9, AC-10, AC-11
 */
import { Command } from 'commander';
export declare function registerAmend(program: Command): void;
//# sourceMappingURL=amend.d.ts.map