/**
 * Walk an OOXML abstractNum element tree and flag any `<w:lvl>` whose
 * `numFmt` is in the ordered family and whose `rFonts` points at a symbol
 * font. Returns the list of violations; empty means the abstract is clean.
 *
 * @param {object} abstractNum OOXML element shape: { name, attributes, elements: [...] }.
 * @returns {Array<{ ilvl: number, numFmt: string, font: string }>}
 */
export function findSymbolFontsOnOrderedLevels(abstractNum: object): Array<{
    ilvl: number;
    numFmt: string;
    font: string;
}>;
/**
 * Programmatic sanity checks for numbering abstract definitions.
 *
 * These checks catch OOXML-level correctness issues that the SuperDoc internal
 * projection layer normalizes away — in particular, cases where a list level's
 * `numFmt` disagrees with its `rFonts` (e.g. `decimal` numbering paired with
 * `Wingdings`, which causes Word to render digits as pictographic glyphs).
 *
 * Designed to be cheap and dependency-free so any unit or integration test can
 * use it to gate post-mutation state.
 */
/**
 * Word-known `numFmt` values that render numeric or alphabetic markers.
 * When any of these is set on a level whose `rFonts` points at a symbol font,
 * the marker character (e.g. "1", "a") is drawn through the symbol font and
 * comes out as a pictograph instead of a readable digit/letter.
 */
export const ORDERED_NUM_FMTS: Set<string>;
/**
 * Fonts with no standard numeric/alphabetic glyphs at ASCII codepoints.
 * Legitimate choice for bullet markers; never correct for ordered markers.
 */
export const SYMBOL_MARKER_FONTS: Set<string>;
//# sourceMappingURL=numbering-consistency.d.ts.map