//#region src/cli/router.d.ts
/**
 * Top-level argv routing for the `doompi` binary.
 *
 * Deliberately tiny and dependency-free. It answers two questions before any
 * command module loads: which subcommand was named, and whether this run only
 * wants help or a version. Everything else, including the harness options and
 * the Pi passthrough, stays with `parseHarnessArgs`, which already knows the
 * harness vocabulary and forwards what it does not own.
 */
/** Subcommands that parse their own arguments instead of passing them to Pi. */
export declare const KNOWN_COMMANDS: readonly ['init', 'sync', 'api-export', 'compat', 'doctor', 'history-export', 'history-import'];
export type KnownCommand = (typeof KNOWN_COMMANDS)[number];
/**
 * The named subcommand, or undefined when this run is a Pi invocation.
 *
 * Reads argv[0] only. A token later in the line is a flag value or prompt text,
 * never a command, so scanning further would let `doompi --profile sync` look
 * like a sync.
 */
export declare function routeCommand(args: readonly string[]): KnownCommand | undefined;
/**
 * Whether this run asks for help or a version, before the passthrough boundary.
 *
 * The scan stops at the first bare `--` so a provider's own `--help` reaches
 * the provider rather than printing doompi's help and exiting.
 */
export declare function informationalRequest(args: readonly string[]): 'help' | 'version' | undefined;
/** Convenience for a subcommand that only needs to know whether to print help. */
export declare function wantsHelp(args: readonly string[]): boolean;
//#endregion
//# sourceMappingURL=router.d.cts.map