export interface McpEntry {
    command: string;
    args: string[];
}
/**
 * Options for resolving the MCP entry.
 *
 * - `argv1` undefined (or omitted) → falls back to `process.argv[1]`.
 *   This is the documented default.
 * - `argv1: ""` → treated as "no argv1 available" → forces dev mode.
 *   Useful in tests and unusual runtime contexts (e.g. embedded).
 * - `argv1: "/abs/path"` → used as-is (subject to realpath).
 * - `dev: true` → forces dev mode regardless of argv1. Escape hatch
 *   for fork checkouts that happen to live under a `node_modules/`
 *   ancestor (rare).
 */
export interface ResolveOptions {
    argv1?: string;
    dev?: boolean;
}
export type InstallMode = "npm" | "dev";
/**
 * Detects whether the running Lyse process was launched from an npm
 * install (under a `node_modules/` ancestor after realpath resolution)
 * or from a local dev build.
 *
 * @returns `"npm"` if the resolved argv1 contains a `/node_modules/`
 *   path segment; otherwise `"dev"`. Forced to `"dev"` if `opts.dev`
 *   is `true` or argv1 is missing/empty. See ResolveOptions for input
 *   semantics.
 */
export declare function detectInstallMode(opts?: ResolveOptions): InstallMode;
export declare function resolveLyseMcpEntry(opts?: ResolveOptions): McpEntry;