/**
 * Framework Detector
 *
 * Auto-detects the test framework used in a project by inspecting
 * well-known configuration files, without any LLM call.
 *
 * Detection order (first match wins):
 *   1. vitest     — package.json has vitest dependency
 *   2. playwright — package.json has @playwright/test dependency
 *   3. junit      — pom.xml (Maven) or build.gradle[.kts] (Gradle) exists
 *   4. gotest     — go.mod exists
 *   5. pytest     — pyproject.toml, setup.cfg, or pytest.ini exists
 *   6. gtest      — CMakeLists.txt contains GTest or googletest
 *   7. catch2     — CMakeLists.txt contains Catch2, or catch2 header exists
 *   → falls back to 'vitest' when nothing is detected
 *
 * Order rationale: JS/TS markers are checked first because a polyglot repo's
 * package.json names a specific runner; Java/Go build manifests are
 * language-unambiguous, so they precede the file-existence-only Python and
 * CMake checks.
 */
import type { TestFramework } from '../../types/test-generator.js';
export declare function detectFramework(rootPath: string): Promise<TestFramework>;
//# sourceMappingURL=framework-detector.d.ts.map