/**
 * Repository map — a token-budgeted orientation view of the codebase.
 *
 * The map is built from the index's graph centrality (`file_rank`), not from a
 * filesystem walk. Two things follow from that:
 *
 *  - **It ranks by evidence.** The previous implementation never opened the
 *    index at all: it walked the tree and scored files by whether their name
 *    matched `index|main|app|server|…` plus a directory-depth bonus, stopping
 *    after ~500 files. On a repo of 8,412 that produced a map of whichever
 *    directories the walk reached first, ranked by filename. Centrality
 *    instead answers the question the map is actually asked — what does the
 *    rest of this codebase depend on?
 *  - **It can group.** `files.package` gives every file an ecosystem-derived
 *    cluster label, so the map opens with the shape of the repo (clusters and
 *    their hubs, then global hotspots) before descending into signatures.
 *
 * When the index has no ranks — a fresh clone, the first index run, a
 * directory that was never indexed — {@link generateFallbackRepoMap} takes
 * over and the output degrades to the old heuristic rather than to nothing.
 */
import type { RepoMapOptions, RepoMapResult } from './repo-map-types.js';
export { generateFallbackRepoMap } from './repo-map-fallback.js';
export type { RepoMapOptions, RepoMapResult } from './repo-map-types.js';
/**
 * Generate a graph-ranked, token-budgeted repository map.
 *
 * Falls back to the filesystem heuristic whenever the index cannot answer —
 * no ranks yet, or the store could not be opened at all.
 */
export declare function generateRepoMap(opts: RepoMapOptions): Promise<RepoMapResult>;
//# sourceMappingURL=repo-map.d.ts.map