/**
 * The single static console page: no framework, no build step, one file.
 * It fetches the sibling JSON endpoints (relative to its own mount path)
 * and renders them in eight views: Overview, Clients, Commits, Rows,
 * Scopes, Events, Reactions, and Storage. Each view loads only the
 * endpoints it shows, so a refresh on one view costs one to five reads.
 *
 * Styling follows docs/STYLE.md and the docs shell: pure black, one amber
 * accent with phosphor/red status colors, hairline borders, square corners.
 * The page ships as one self-contained string with no network fetches, so
 * it uses the system font stacks (monospace for data, sans for prose); a
 * host with IBM Plex installed renders in Plex.
 *
 * The HTML is a single exported string so the routes module can serve it
 * with no filesystem read (works identically on Bun, Node, and Workers).
 * All fetches are same-origin and relative ('./clients', …), so the page
 * works under whatever prefix the host mounts the routes at, and the host's
 * `authorize` guard applies to the page's own XHRs (same cookies/headers).
 * `?transport=parent` sends the same route paths to a same-origin parent
 * frame. Static demos can reuse this page while their admin routes run in a
 * Web Worker.
 *
 * The event tail is live over SSE (`/events/stream`) when the ring is wired.
 * The parent transport carries no stream, and an SSE failure closes the
 * stream for good; both states poll `/events` on every refresh and say so
 * in the header and the Events view.
 */
export declare const ADMIN_CONSOLE_HTML: string;