import type { IsolationStrategy } from './schema.js';
/**
 * Whether the test harness ever creates the app-role pool under `strategy`.
 *
 * Transaction isolation registers its single rolled-back connection as the pool
 * override under the database's *base* key (`src/test/plugin.ts`), and
 * `getOrCreate(config, 'app')` falls back to that base override when no
 * role-specific one is registered (`src/core/pipework.ts`) — so the app-role
 * pool is never constructed and `appUrl`/`appTestUrl` are never dialed by it.
 * Every other strategy resolves roles normally (`appUrl ?? url`) and creates it.
 *
 * This is the single statement of that fact: both the app-pair value-identity
 * carve-out (`resolveDbUrl`) and the RLS probe target (`rlsProbeTarget`) are
 * expressed in terms of it, so the two cannot drift apart.
 */
export declare function appPoolCreated(strategy: IsolationStrategy): boolean;
//# sourceMappingURL=app-pool.d.ts.map