/**
 * PostReleaseValidationStage — gap analysis after publish/deploy (FR-17 + FR-18).
 *
 * FR-17: Compares spec FR list against deploy artifacts.
 * FR-18: When OKR tree is present, upgrades to KR-level gap analysis,
 *         supports PDCA sub-cycles, and enforces max cycle limits.
 */
import type { PostReleaseValidationInput, PostReleaseValidationOutput, KrGapEntry } from './post-release-validation-types.js';
export declare class PostReleaseValidationStage {
    /**
     * Run gap analysis against the spec FR list.
     * When okrTree is present and non-empty, KR-level analysis takes precedence
     * for canComplete determination (AC-18.9).
     */
    run(input: PostReleaseValidationInput): PostReleaseValidationOutput;
    /**
     * Run a PDCA sub-cycle within Post-Release Validation (AC-18.10, AC-18.11).
     * Simulates Implement→Review→Deploy→Validate sub-loop without modifying
     * the pipeline's main state machine.
     *
     * @param input - The validation input (with okrTree)
     * @param simulateFix - Callback that simulates fixing KR gaps and returns updated okrTree.
     *                      In real usage, this triggers actual work packages.
     * @returns Final output after all PDCA cycles complete or max reached.
     */
    runWithPdca(input: PostReleaseValidationInput, simulateFix: (gaps: KrGapEntry[], cycle: number) => PostReleaseValidationInput): PostReleaseValidationOutput;
    private runFrAnalysis;
    private analyzeKrGaps;
    private mapKrStatus;
    private krReasonForStatus;
    private assessFr;
    private reasonForStatus;
}
//# sourceMappingURL=post-release-validation-stage.d.ts.map