/**
 * What a person did with the in-page HUD, as names only.
 *
 * The HUD is where a human meets Reticle, and nothing measured it: which controls get used, which
 * panel is open, whether the HUD spends its life as a bubble or open, which settings get changed.
 * Every id is the name of a control Reticle rendered, never text from the page, a flow name or a
 * URL: the telemetry contract's "names, never values". A control whose id is not listed here is
 * dropped at the daemon rather than counted, so a new control cannot leak free text by accident;
 * the browser test that walks the rendered HUD fails if any control has no id in this list.
 */
/** The attributes whose value is part of the id. Read by the browser to build one. */
export declare const HUD_KEYED_ATTRS: readonly ["setting", "check", "settings-cycle", "theme", "tour-target", "link", "annotation-tab", "chat-view-btn"];
/**
 * Is this a control id the HUD renders?
 *
 * The set is built on first use rather than at module scope: core's root entry is on every page
 * load, and a Set constructed at the top of a module is a side effect no bundler can drop.
 */
export declare function isHudControl(id: string): boolean;