/**
 * PZG Pro Generator Implementation
 *
 * This matches the main prisma-zod-generator pattern but loads Pro feature
 * modules lazily so the OSS build compiles without the private submodule.
 */
import type { GeneratorOptions } from '@prisma/generator-helper';
import { type LicenseFailureReason } from '../license';
export declare const PRO_HELP_MESSAGE: string;
/**
 * Remedy text for the case where the Pro modules *are* installed but the
 * license did not validate. Distinct from PRO_HELP_MESSAGE, which tells the
 * reader to initialize a git submodule — advice that cannot help an npm
 * consumer whose only problem is an unset or expired PZG_LICENSE_KEY.
 */
export declare function buildProLicenseMessage(status: {
    reason?: LicenseFailureReason;
    detail?: string;
}): string;
interface ProFeaturesConfig {
    enablePolicies?: boolean;
    enableServerActions?: boolean;
    enableSDK?: boolean;
    enableContracts?: boolean;
    enablePostgresRLS?: boolean;
    enableForms?: boolean;
    enableApiDocs?: boolean;
    enableMultiTenant?: boolean;
    enablePerformance?: boolean;
    enableFactories?: boolean;
    policies?: unknown;
    serverActions?: unknown;
    sdk?: unknown;
    contracts?: any;
    postgresRls?: unknown;
    forms?: unknown;
    apiDocs?: unknown;
    multiTenant?: unknown;
    performance?: unknown;
    factories?: unknown;
    outputPath?: string;
    configPath?: string;
    /**
     * Per-model settings, merged in from `configPath`. Only `enabled` is consulted
     * by the Pro packs; it uses the same shape as the core generator's config so a
     * single file governs both.
     */
    models?: Record<string, {
        enabled?: boolean;
    }>;
}
export declare function generateProFeatures(options: GeneratorOptions): Promise<void>;
/**
 * Exported for `tests/pro-config-parsing.test.ts`. Which packs run, and where that decision is read
 * from, is worth testing directly: the `config`/`configPath` mismatch it now tolerates failed by
 * enabling nothing and saying nothing, which no end-to-end assertion on generated files would catch.
 */
export declare function parseProConfig(options: GeneratorOptions): Promise<ProFeaturesConfig>;
export {};