/**
* 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 const ADMIN_CONSOLE_HTML = `
Every actor in this partition with the devices it syncs from. An actor opens its failed and warned requests; a device opens its client page: subscriptions, lease, failures, recent events, and a delivery trace.
The server's authoritative rows, table by table. A table opens a row browser filtered by scope; a row shows its values, its history, and which clients hold it.
The commit log, newest first, with the first changes of each commit. A commit opens every row change with its values. A client commit id from a bug report opens what happened to that write.
05 · Events
Event stream.
Server events from the in-memory ring, newest first, one row per sync request. A request opens all of its events. Kind and client filter on the server; family, level, and text filter the buffered tail.
06 · Reactions
Durable reactions.
The reaction queue of this partition, dead letters first, with attempts and the last failure code. Reaction rows carry application payloads.
07 · Storage
Storage.
Segment and blob store counters, and the commit log's retention state.
Segments
Blobs
Commit log
Find
Clients and actors whose id contains the text, rows whose id equals it in any table, the commit with that sequence number, and the writes logged under that client commit id.