/**
 * Locate the gate, preferring the copy that SHIPS WITH THIS PACKAGE.
 *
 * The in-package path is probed first and explicitly: a published
 * `create-fragment` install has no repo checkout around it, and package.json
 * "files" carries scripts/ precisely so the gate travels with the CLI. Falling
 * back to an upward walk keeps a repo checkout and a linked/hoisted install
 * working, without hardcoding a depth that rots when the build layout changes.
 *
 * HERE is <pkg>/dist/engine when built and <pkg>/src/engine under tsx, so two
 * levels up is the package root in both cases.
 */
export declare function resolveGate(): string | null;
export interface GateOptions {
    projectDir: string;
    cmd: 'init' | 'add' | 'connect';
    /** Surfaces this command was ASKED for — I1 checks these, not whatever is on disk. */
    surfaces?: string[];
    templatesDir?: string;
}
/** Runs the gate. Throws on FAIL so the caller's success print never happens. */
export declare function runGate(options: GateOptions): void;
//# sourceMappingURL=gate.d.ts.map