/**
 * `fjall ci setup` vocabulary — the ONE spelling the CLI's `--provider`
 * option, its `CI_SETUP_SCHEMA` agent projection and the MCP's
 * `plan_ci_setup` / `apply_ci_setup` pin all derive from.
 *
 * The MCP shells out to the CLI and cannot import it (`@fjall/cli` publishes
 * a bin, no module exports), so until this module the two packages carried
 * the provider list and the TOON field names as separate literals kept "in
 * lockstep" by a comment. The MCP's pin reads the CLI's `--agent` output by
 * field NAME (`provider: …`, `app: …`) and gates a deploy-token mint on the
 * result, so a rename on one side silently un-pinned the other. Both sides
 * now read these tuples; a rename is a typecheck failure in both packages.
 *
 * Client-safe (no node built-ins) — exported from the root barrel.
 */
export declare const CI_PROVIDERS: readonly ["github", "buildkite"];
export type CiProvider = (typeof CI_PROVIDERS)[number];
/**
 * The fields `fjall ci setup --agent` renders as flat TOON `key: value`
 * lines (the CLI's `CI_SETUP_SCHEMA.defaultFields`, in render order). No token
 * field: the CLI never holds a deploy token — `mintUrl` is the hand-off to the
 * web app that mints it.
 */
export declare const CI_SETUP_FIELDS: readonly ["provider", "repo", "app", "workflowPath", "planned", "workflowWritten", "deployTarget", "mintUrl", "secretName"];
export type CiSetupField = (typeof CI_SETUP_FIELDS)[number];