/**
 * `guuey.json#ggui` — optional cross-protocol integration section.
 *
 * Reserved for projects that use the ggui protocol (mcp.ggui.ai) for
 * rendering. The actual ggui-app identity (slug, gadgets, publicEnv,
 * etc.) lives in a separate `ggui.json` file owned by the ggui
 * ecosystem (`@ggui-ai/project-config`). This section provides the
 * reference from `guuey.json` to that sibling file.
 *
 * Two reference forms:
 *
 * - **File path** — `{ configFile: './ggui.json' }` resolves the sibling
 *   file at deploy time. Recommended for most projects.
 * - **Inline** — `{ inline: { ...ggui-json-fields } }` for projects that
 *   prefer a single config file. Schema validation defers to the ggui
 *   ecosystem (we only type the wrapper).
 *
 * Cross-ecosystem boundary: guuey-side does NOT validate the ggui section's
 * contents. The platform is MCP-server-agnostic — agents can use
 * `mcp.ggui.ai` and get rendering for free, or use a different MCP server
 * and skip this section entirely.
 */
import { z } from 'zod';
/**
 * The ggui integration section schema. Mutually exclusive forms:
 * `configFile` reference OR `inline` object. Both optional — projects
 * that don't use ggui rendering omit the whole `ggui` block.
 */
export declare const GguiSectionV1: z.ZodObject<{
    appId: z.ZodOptional<z.ZodString>;
    configFile: z.ZodOptional<z.ZodString>;
    inline: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
}, z.core.$strict>;
/** Static TypeScript type for the ggui integration section. */
export type GuueyGguiSection = z.infer<typeof GguiSectionV1>;
//# sourceMappingURL=ggui.d.ts.map