/**
 * The characters the assembled document renders, framework chrome included.
 *
 * This decides which font subsets a built deck has to carry. It once also
 * carried a slide-only scope for the glyph-coverage check to warn from, but
 * that check now judges each element through the fonts the browser actually
 * rendered it with (see `check/judge.ts`'s `judgeGlyphs`) rather than against
 * a deck-wide codepoint set, so only this one scope is still read.
 */
export interface DeckCodepoints {
  readonly full: ReadonlySet<number>;
}
export interface DeckScanInput {
  /** Assembled slide markup — deck content only, no framework chrome. */
  slidesHtml: string;
  /** Framework chrome markup: nav, counter, progress, theme switch. */
  chromeHtml?: string;
  /**
   * Stylesheets that apply to the deck (zerp's own base styles). `<style>`
   * blocks inside `slidesHtml` are picked up on their own.
   */
  css?: readonly string[];
}
/**
 * Compute the codepoints a deck can render.
 *
 * Four sources feed it, because slide text alone misses most of them:
 *
 * - the assembled deck's own text, markdown already rendered, plus framework
 *   chrome's;
 * - `content:` string literals from the stylesheets that apply to it — the
 *   `"→ "` ul marker and the `"vs"` of `.compare` are drawn by CSS and appear
 *   in no slide file;
 * - the values of attributes those rules name with `attr()`, which is how
 *   `.compare[data-vs]` prints its own label;
 * - the digits, which `counter()` generates at render time.
 *
 * Script source counts too, deliberately: a string literal in a slide script
 * is text the deck may well render, and over-selecting a subset costs bytes
 * while under-selecting costs the reader a fallback glyph.
 */
export declare function scanDeckCodepoints(input: DeckScanInput): DeckCodepoints;