import { ZapierSdkOptions } from '@zapier/zapier-sdk/experimental';
import { E as Extension, Z as ZapierSdkCli } from './extensions-D1NeCGqK.mjs';
import '@zapier/zapier-sdk';
import '@zapier/kitcore';
import 'zod';
import 'zod/v4/core';

/**
 * Experimental CLI SDK factory.
 *
 * Mirror of `./sdk.ts`, but built on top of
 * `@zapier/zapier-sdk/experimental` so the underlying SDK has every
 * `meta.experimental: true` plugin registered. The CLI's runtime
 * entry point (`cli.ts`) chooses between this and the stable factory
 * based on three equivalent triggers detected before Commander parses:
 * the `zapier-sdk-experimental` bin name (via `argv[1]`), the
 * `--experimental` flag, or the `ZAPIER_EXPERIMENTAL=1` env var.
 *
 * Plugin chain matches `./sdk.ts` literally, with future CLI-only
 * experimental plugins inserted at appropriate positions. Both
 * factories are kept in sync by shape tests.
 */

interface ZapierCliSdkOptions extends ZapierSdkOptions {
    /**
     * Extra plugins discovered from `@zapier/zapier-sdk` extension packages.
     * Pre-resolved by `cli.ts` (`utils/extensions.ts`) so this factory stays
     * synchronous. Each plugin is layered onto the chain after all built-in
     * CLI plugins, so its functions appear in `getRegistry({ package: "cli" })`
     * automatically.
     */
    extensions?: Extension[];
}
/**
 * Create a Zapier CLI SDK with experimental plugins registered. The
 * returned shape is a superset of the stable CLI SDK — same plugins
 * plus any marked experimental.
 */
declare function createZapierCliSdk(options?: ZapierCliSdkOptions): ZapierSdkCli;

export { type ZapierCliSdkOptions, createZapierCliSdk };