/**
 * The infrastructure tier vocabulary — what `fjall apps create --type` accepts,
 * and the ONE spelling the generator's `AppTypeSchema`, the CLI's
 * `commandSchemas.ts` and the MCP's `plan_app_scaffold` input all derive from.
 *
 * Not the pattern tiers (`PATTERN_TIER_VALUES`: lightweight … custom), which
 * govern `--pattern-tier`. The two vocabularies overlap on three members and
 * were conflated on the MCP surface until Train 4 of the 2026-09-07 hardening
 * prompt; keeping both here, each naming the other, is what stops the next
 * reader picking whichever tuple is nearer.
 *
 * The MCP shells out to the CLI and can import neither it nor the generator at
 * runtime, so util is the seam all three read — the same rationale as
 * `ciSetup.ts` and `patterns/patternTypes.ts`.
 *
 * Client-safe (no node built-ins) — exported from the root barrel.
 */
export declare const INFRASTRUCTURE_TIER_NAMES: readonly ["tinkerer", "lightweight", "standard", "resilient", "enterprise"];
export type InfrastructureTierName = (typeof INFRASTRUCTURE_TIER_NAMES)[number];
/**
 * The escape hatch: an app that declares its own resources rather than taking
 * a tier preset. A member of `APP_TYPES`, never of the tier tuple — the presets
 * are a `Record<InfrastructureTierName, …>` and `custom` has no preset row.
 */
export declare const CUSTOM_APP_TYPE: "custom";
export declare const APP_TYPES: readonly ["tinkerer", "lightweight", "standard", "resilient", "enterprise", "custom"];
export type AppType = (typeof APP_TYPES)[number];