/**
 * Pantone "Gold" / coated-base lookup table — built-in fallback used
 * when no host-provided palette is available and the PDF's tint
 * transform did not yield a usable RGB primary.
 *
 * Hex values are sRGB approximations of the Pantone Coated palette as
 * published by Pantone for screen rendering. They are not a perfect
 * substitute for proofing against a physical Pantone chip, but they
 * give the separations panel a recognisable swatch instead of the
 * generic "every spot is purple" fallback.
 *
 * Lookup is case-insensitive and tolerates the common variants:
 * trailing " C" / " U" suffix, no suffix, whitespace, "PMS " prefix.
 * Add entries as customers report missing spots.
 */
/**
 * Look up a process-plate name (Cyan / Magenta / Yellow / Black,
 * synonyms, display-RGB plates). Returns ``undefined`` when the
 * name isn't a known process plate so callers can fall through to
 * the Pantone Gold lookup.
 */
export declare function processPlateLookup(name: string): string | undefined;
/**
 * Look up a spot-colour name in the built-in Pantone Gold table.
 * Returns ``undefined`` when there's no match; callers fall through
 * to ``rgbToHex(altRgb)`` or the default neutral grey.
 *
 * The match tolerates the common variants — "PANTONE 225 C",
 * "PANTONE 225C", "PMS 225 C", "Pantone 225 c" all resolve to the
 * same entry.
 */
export declare function pantoneGoldLookup(name: string): string | undefined;
/**
 * Convenience: convert an ``[r, g, b]`` triplet (each 0–255) to a
 * lowercase ``#rrggbb`` hex string.
 */
export declare function rgbToHex(rgb: readonly [number, number, number]): string;
/**
 * Full resolution chain for a single ink. Used by the separations
 * panel + every marketing site's spot-colour swatch render:
 *
 *   1. Built-in process-plate lookup (Cyan / Magenta / Yellow / Black
 *      + synonyms + RGB plates) — always wins because process plates
 *      have canonical primaries that no host should override
 *   2. Host-provided ``spotPalette[name]`` — usually codex's
 *      ``summary.spot_colors.colors[].swatch_hex`` or another
 *      preflight's swatch
 *   3. Built-in Pantone Gold library (~85 most-common Coated codes)
 *   4. PDF tint transform ``altRgb`` (parsed at extraction time)
 *   5. Neutral grey fallback ``#1f2937``
 *
 * The process-plate check sits at the top of the chain because
 * codex (and other engines) hash-derive random colours for process
 * plates when their detector can't read the named alternate. That
 * makes "Cyan" render orange, "Magenta" render blue, etc. The
 * canonical CMYK primaries are non-negotiable.
 */
export declare function resolveSpotSwatch(name: string, altRgb: readonly [number, number, number] | null | undefined, spotPalette: Record<string, string> | undefined): string;
/**
 * Resolve the display swatch hex for a detected ink — the **single source**
 * every surface shares (inks side-panel, separation plate composite,
 * densitometer, colour picker) so a process plate / spot swatch can never
 * diverge between them. Process inks use the canonical CMYK table; spots use
 * the 5-tier {@link resolveSpotSwatch} chain (host palette → Pantone Gold →
 * PDF tint colour → neutral grey).
 */
export declare function resolveInkSwatch(ink: {
    name: string;
    type: "process" | "spot";
    altRgb?: readonly [number, number, number] | null;
}, spotPalette: Record<string, string> | undefined): string;
//# sourceMappingURL=pantone-gold.d.ts.map