import type { Command } from '../args.js';
import type { Profile } from '../profiles.js';
import { type Io } from '../output.js';
import { type VerbServerFactory } from './fetch.js';
/**
 * Does the "your tab may be on a subdomain" hint apply to this rejection?
 *
 * Exported and pure for the reason `read-dom.ts` gives for its own gates: the
 * decision is worth pinning, and reaching it through the verb would mean
 * standing up a live server and IO to assert one sentence.
 *
 * Two wordings share the `no tab matching ` prefix and must NOT get it. The
 * content-script variant means a tab DID match, so a different host is not the
 * problem. And "one is still opening" (#291) means the extension is opening a
 * tab for this exact host right now — the first health check after a pair
 * routinely lands mid-open, and `--subdomain www` is the wrong thing to reach
 * for when the answer is to wait a moment.
 */
export declare function subdomainHintApplies(message: string): boolean;
export declare function runHealth(cmd: Extract<Command, {
    kind: 'health';
}>, profile: Profile, io: Io, makeServer?: VerbServerFactory): Promise<number>;
export declare function runPair(cmd: Extract<Command, {
    kind: 'pair';
}>, profile: Profile, io: Io, makeServer?: VerbServerFactory): Promise<number>;