/**
 * The bundle ceiling — ONE number, reachable from everywhere that needs it.
 *
 * It used to live in `pack.ts`, which imports `node:child_process` to drive the `tar` binary. That
 * made it unreachable from the browser wizard, and the wizard is the surface where the limit
 * matters MOST: the CLI hits it after packing locally, while a browser would hit it after
 * uploading. `pack.ts` re-exports this, so every existing importer is unchanged.
 *
 * The history is why it is a module of its own: this path once had THREE ceilings — a 250 MiB
 * literal in the release route, 50 MiB at hosting, and Vercel's silent ~4.5 MB — and the one that
 * actually fired was the one nobody had written down.
 */
/** Hosting's intake cap. Matches the hosting service's own limit; it is not a client preference. */
export declare const BUNDLE_MAX_BYTES: number;