/**
 * Inline Consent Bundle
 *
 * Auto-generated file containing the bundled consent components.
 * DO NOT EDIT - regenerate with: pnpm build:bundle
 *
 * @module @kya-os/consent/bundle/inline
 * @generated
 */
/**
 * The bundled consent.js content as a string.
 * Use this to serve the bundle from a Worker.
 */
export declare const CONSENT_BUNDLE: string;
/**
 * Size of the bundle in bytes (for logging/debugging)
 */
export declare const CONSENT_BUNDLE_SIZE: number;
/**
 * sha256 content hash of {@link CONSENT_BUNDLE} (first 16 hex chars).
 */
export declare const CONSENT_BUNDLE_HASH: string;
/**
 * The canonical path this bundle is served from — content-addressed, so a new
 * build is a new URL.
 *
 * This is the single source of truth for BOTH sides: the shell emits it as the
 * `<script src>`, and the worker routes it. Anything that hardcodes
 * `/consent.js` instead will silently drift from whatever is actually served.
 *
 * Serving a stable, unversioned URL with `Cache-Control: immutable` is what
 * pinned browsers to a stale consent UI indefinitely; a content-addressed path
 * makes that header safe.
 */
export declare const CONSENT_BUNDLE_PATH: string;