/**
 * Truthy when the named feature is enabled in the current environment.
 *
 * Resolution order (first match wins):
 *   1. Runtime override via `enableFeature` / `disableFeature`
 *   2. `config.<name>.enabled` — boolean or omitted
 *      - Optional `config.<name>.env: string[]` narrows the flag to specific
 *        deploy targets (compared against `config.app.env`)
 *   3. Per-feature framework default (only `dashboard` defaults true)
 *
 * @example
 * ```ts
 * if (feature('commerce')) {
 *   await loadCommerceRoutes()
 * }
 * ```
 */
export declare function feature(name: string): boolean;
/**
 * Force-enable a feature in the running process. Intended for tests and
 * staged rollouts; production code should prefer config-file overrides.
 */
export declare function enableFeature(name: string): void;
/**
 * Force-disable a feature in the running process.
 */
export declare function disableFeature(name: string): void;
/**
 * Drop a runtime override and fall back to the config-driven value.
 */
export declare function resetFeature(name: string): void;
/**
 * Snapshot of the live flag set — useful for `/__features` debug endpoints
 * and CLI commands that print the active configuration. Iterates the known
 * framework features plus any runtime overrides for ad-hoc flags.
 */
export declare function listFeatures(): Record<string, boolean>;
export type StacksFeature = | 'auth' | 'marketing' | 'cms' | 'commerce' | 'forms'
  | 'dashboard' | 'monitoring' | 'realtime' | 'queue';