/**
 * Rule: detail-view-renders
 *
 * For every model, boot the runtime, navigate to the model, and verify
 * no error boundary is shown even when the model has zero instances
 * (the empty state is still a render that can crash).
 *
 * Distinct from list-view-renders because v1's navigateToModel lands
 * on the list by default, not the detail. In practice both rules
 * currently exercise the same nav-click + no-error assertion; when
 * detail views get their own dedicated entry point in the DevShell,
 * this rule will diverge to target that path specifically.
 *
 * Kept as its own rule for two reasons:
 *   1. Failure attribution is clearer — a broken detail template
 *      fails this rule but not `list-view-renders`.
 *   2. The rule stays stable across harness evolution — when we add
 *      a `navigateToDetail` helper, only this rule's step changes,
 *      not the entire test surface.
 */
import type { UiContractRule } from '../test-case-types.js';
export declare const RULE_ID = "detail-view-renders";
export declare const detailViewRenders: UiContractRule;
//# sourceMappingURL=detail-view-renders.d.ts.map