/**
 * "Is `<name>` installed?" answered with a filesystem lookup, not a subprocess.
 *
 * Extracted from `roadmap/sync/gh.ts` `resolveGhOnPath` when the herdr hand-off needed the
 * same answer for `herdr` (worktree-opens-in-herdr): a copy would drift on the one detail
 * that is easy to get wrong, Windows' `PATHEXT`.
 *
 * `env` is a parameter, not a read of `process.env`, so both branches are testable without
 * mutating the ambient environment. `PATH` entries are untrusted path fragments: they are
 * joined and permission-tested, never interpolated into a command.
 *
 * @module
 */
/** The first executable `name` on `PATH`, or null when there is none. */
export declare function resolveOnPath(name: string, env?: NodeJS.ProcessEnv): string | null;
//# sourceMappingURL=on-path.d.ts.map