import type { PageModel } from '../editor/store.js';
/**
 * QA scenarios the active screen verifies, as executable rows: clicking a
 * claim reproduces the exact reviewed state (frame activation, state reveal,
 * prop flip, or preset resize). The ledger is host-declared and core-
 * validated, so a renamed component or retired preset fails the gate instead
 * of silently orphaning the scenario.
 */
export declare const FrameScenarioCoverage: import("react").FunctionComponent<{
    page: PageModel;
}>;
/**
 * Surfaces this frame owes an answer to.
 *
 * The declared axes are what the host remembered to declare, and for a long
 * time that was the whole story: an element nobody thought about produced no
 * axis and no complaint, because the ledger only ever compared declarations
 * with each other. This section is the other half — the editor lists the
 * operable elements of the tree it imported and the requests the frame made
 * while booting, and the host either points each one at a declaration or
 * excludes it with a reason.
 *
 * It renders nothing once every surface has a verdict, so a finished frame stays
 * quiet and an unfinished one says exactly what is missing.
 */
export declare const FrameSurfaceDemands: import("react").FunctionComponent<{
    page: PageModel;
}>;