import type { FormatEntity, FormatEntityKind } from './types.js';
export type { FormatEntity, FormatEntityKind } from './types.js';
export { FormatEntityKindSchema } from './types.js';
export { extractCsvEntities } from './csv.js';
export { extractJsonEntities } from './json.js';
export { extractMarkdownEntities, scanMarkdownLines } from './markdown.js';
export type { MarkdownLineState } from './markdown.js';
export { extractTomlEntities } from './toml.js';
export { extractYamlEntities } from './yaml.js';
export declare const FORMAT_EXTENSIONS: readonly string[];
export interface FormatExtraction {
    entities: FormatEntity[];
    /** True only when a supported extractor rejected malformed input. */
    parseFailed: boolean;
}
export declare function formatForPath(relativePath: string): string | undefined;
/**
 * Extract entities from a data-format file, or nothing if the extension is not
 * one OCC models.
 *
 * These extractors are not registered as languages, so `occ code map`,
 * `dirtree`, and the code graph behave exactly as before; only the entity layer
 * consults them. Format entities get honest diff, blame, and history, and no
 * impact at all — they have no edges, and that is reported rather than
 * presented as "nothing depends on this".
 */
export declare function extractFormatEntities(relativePath: string, content: string): FormatExtraction | undefined;
/** Format kinds, for callers that need to enumerate what a format can produce. */
export declare const FORMAT_ENTITY_KINDS: readonly FormatEntityKind[];
