/**
 * Validation for the `<mix flag="NAME">` / `<case anomaly="true">` pair — the
 * ground-truth label saying which rows came from a branch declared anomalous.
 *
 * Either half alone is silently useless: the config reads as if it labels
 * outliers while the runtime does nothing. That is the same trap TDC128 exists
 * for (conditional attributes on `<case>` that were accepted and ignored), so
 * it gets the same treatment — surface it rather than produce a dataset whose
 * labels are quietly all `false`.
 */
import { type Diagnostic } from '../errors/index.js';
import type { OpenCloseElementContext } from '../generated/TDCParser.js';
/**
 * Check one `<mix>`'s flag wiring. `named` is false for a nested (anonymous)
 * mix inside a `<case>`, which contributes only a value fragment and therefore
 * cannot own a sequence of its own.
 */
export declare function checkMixFlag(mixEl: OpenCloseElementContext, cases: readonly OpenCloseElementContext[], diagnostics: Diagnostic[], named: boolean): void;
//# sourceMappingURL=mix-flag.d.ts.map