/**
 * `lobu connector run` — execute a connector locally against a browser_session
 * auth profile, no feed row required, no events persisted.
 *
 * Why this exists: testing a device-bound browser_session profile end-to-end
 * (does Chrome launch, are we signed in, does the connector emit anything?)
 * used to require creating a real connections row + a feed + triggering it,
 * and even then events would commit. This command runs the same compiled
 * connector code the server runs, against the same SessionState shape, but
 * locally on the user's Mac (where the source Chrome profile lives) and dumps the
 * would-be events + would-be-next-checkpoint to stdout and a run artifact.
 *
 * Scope (v1): browser_session profiles only. OAuth / env / interactive
 * profiles need credentials the CLI doesn't have; they require gateway-side
 * execution (a separate trigger_feed dry_run path, not yet wired).
 *
 * Execution uses SubprocessExecutor (the same one the worker daemon uses),
 * not an in-process executor — bugs in connector code don't take the CLI
 * down, and we get the same isolation production gets.
 */
export interface ConnectorRunOptions {
    connectorKey?: string;
    authProfile?: string;
    config?: string;
    checkpointFromFeed?: string;
    fromFeed?: string;
    maxItems?: string;
    check?: boolean;
    json?: boolean;
    context?: string;
    url?: string;
    org?: string;
}
export declare function connectorRun(args: ConnectorRunOptions, positionalKey?: string): Promise<void>;
//# sourceMappingURL=connector-run-cmd.d.ts.map