/**
 * Browser-side `Indexes` builder — emitted as a JS string for the
 * inlined dashboard script. Mirrors v0.2's `pipeline/indexes.ts`
 * but ported to vanilla JS that runs in the page.
 *
 * The catalog persists only `functions[name][i].calls[].to[]`. v0.2's
 * O(1) `Indexes` is in-memory only; the dashboard rebuilds it on
 * panel-init time. Output: { byBodyHash, occurrencesByHash,
 * bySimpleName, callees, callers }.
 *
 * Blast radius is no longer computed here. The engine's features stage
 * (`pipeline/features.ts`, Plan C) is the single canonical home for the
 * bounded reverse-BFS blast score; a dashboard-bound run materializes it
 * into `catalog.features.function[bodyHash].blast` and the Hot view reads
 * it from there (falling back to the raw inbound-caller count when the
 * catalog carries no features). This builder now only assembles the
 * adjacency the views need for navigation and member resolution.
 *
 * Also emits `resolveCalleeOcc(target, callerOcc, indexes)` — the shared
 * call-target → callee-occurrence resolver. It lives here (not in any single
 * view) because more than one view needs it: the Coupling drilldown AND the
 * function-level Visualization both resolve a call target's bodyHash to the
 * occurrence the caller can actually reach, disambiguating body-hash
 * collisions across packages. Emitting it in the prelude (ahead of every
 * view) removes the load-bearing cross-view emission order it used to imply.
 */
export declare function dashboardIndexesJs(): string;
//# sourceMappingURL=indexes.d.ts.map