export interface ProjectCommands {
    test?: string[];
    e2e?: string[];
    build?: string[];
    lint?: string[];
}
/**
 * Probe a bare command to see if it can be spawned. On Windows, walks PATH entries
 * to find the first executable, checking for the zero-byte App Execution Alias stub
 * (e.g. python.exe from the Microsoft Store stub when Python isn't actually installed)
 * that would open the Microsoft Store on spawn instead of executing or failing cleanly.
 *
 * Returns true if the command appears to be a valid executable, false if it is
 * a zero-byte stub or does not exist.
 *
 * @param command - The command name (e.g., "python")
 * @param platform - The platform to check for; defaults to process.platform
 * @param pathEnv - Optional PATH string; defaults to process.env.PATH
 */
export declare function isValidExecutableCommand(command: string, platform?: NodeJS.Platform, pathEnv?: string): boolean;
/**
 * Discover the test/e2e/build/lint commands for a repository as argv arrays.
 *
 * Node detection (package.json) takes precedence for e2e/build/lint. The test
 * command prefers `npm test`, but — matching the auditor's prior behavior —
 * falls through to Go (`go test ./...`) then Python (`python -m pytest`) when
 * package.json has no usable `test` script or is absent. Absent roles are
 * omitted from the result.
 */
export declare function discoverProjectCommands(root: string): ProjectCommands;
//# sourceMappingURL=testCommand.d.ts.map