/**
 * Subtab-bar Strategy — JS-string emitter for the shared subtab pattern.
 *
 * Both the fit/sim Tool Tab (Sessions / Catalog / Recipes — three
 * subtabs) and the Code Paths Tab (Sessions / Explore — two subtabs)
 * need the same DOM/click-delegation behaviour: a `.subtab-bar` of
 * clickable headers, a stack of `.subtab-panel` containers, and a
 * single click handler that toggles the `active` class on both.
 *
 * Pre-F2, both call sites duplicated the same 20-line block. This
 * emitter declares one runtime helper, `renderSubtabBar(panel,
 * subtabs)`, that both consumers call. The Strategy is the
 * `subtabs` array — each entry is `{ id, label, render(panel) }` —
 * and `renderSubtabBar` returns the panel-element map so callers can
 * still reach into specific subpanels if they need to (Code Paths
 * does not, fit/sim's `renderToolTab` does not either after F2).
 *
 * The emitter must be concatenated BEFORE any caller (i.e. before
 * `dashboardToolTabsJs` and `dashboardCodePathsJs`) since both rely
 * on `renderSubtabBar` being declared in scope.
 */
export declare function dashboardSubtabBarJs(): string;
//# sourceMappingURL=subtab-bar.d.ts.map