import type { GetAngelNumberResponse } from '../types/index.js';
import { RoxyDataElement } from '../utils/base-element.js';
/**
 * Angel number card. Renders /angel-numbers/numbers/{number}: the number as a hero numeral, its title and core message, the pattern type / digit root / energy badges, keyword chips, the life-area interpretations (spiritual, love, career, money, twin flame) plus the biblical and shadow readings as an exclusive accordion, the affirmation, and the action steps.
 *
 * @remarks
 * The numeral, the pattern type, the digit root and the energy badge are computed from the sequence, so they are the card's data spine and `hide-readings` keeps every one of them. The core message, the keyword chips, the life-area accordion, the affirmation and the action steps are the reading and all go, which is the same line `roxy-angel-number-lookup` already draws on the same domain.
 *
 * The accordion draws the shared `interp-accordion` through `RoxyDataElement.renderInterpretation` rather than the bare `<details>` it once hand-rolled. That local copy predated the helper, so it neither honoured `hide-readings` nor answered to `::part(reading)`, and being plain `<details>` rather than `.interp-card` markup it was invisible to the e2e guard that caught the other five.
 */
export declare class RoxyAngelNumberCard extends RoxyDataElement<GetAngelNumberResponse> {
    static styles: import("lit").CSSResult[];
    protected renderData(d: GetAngelNumberResponse): import("lit").TemplateResult<1>;
    private renderSections;
}
declare global {
    interface HTMLElementTagNameMap {
        'roxy-angel-number-card': RoxyAngelNumberCard;
    }
}
//# sourceMappingURL=angel-number-card.d.ts.map