/** * Repo interrogation orchestrator — runs all extractors and merges results. * * Two classes of extractor: * - PROSE (README, Cargo.toml description) → `project.goal` + `human_context`. * README wins on overlap because its prose is most likely hand-curated. * - FILE-FACTS (docker-compose services, Makefile targets, .env.example) → * `stack.*` + `commands.*` + `security.*`. These are ground truth pulled * straight from config — they win over README guesses and over the * presence-only detectors in scanner.ts (wired in assemble.ts). * * The orchestrator never overwrites with a non-empty value — earlier extractors * win; later ones fill empties only. */ import type { ExtractedContext } from './types.js'; export type { ExtractedContext } from './types.js'; export { interrogateReadme } from './readme.js'; export { interrogateCargo } from './cargo.js'; export { interrogateCompose } from './compose.js'; export { interrogateBuildFiles } from './build-files.js'; export { interrogateEnv } from './env.js'; /** Run all repo interrogators and return merged context. */ export declare function interrogateRepo(dir: string): ExtractedContext;