/**
 * An `<env>` with no `seed=`: a file that will not come out the same twice.
 *
 * Nothing about it is wrong, which is why it is a warning — some runs want fresh
 * data every time. But "same seed, same bytes" is the promise the rest of the
 * engine keeps, and a config handed to somebody else without a seed breaks it
 * silently: two runs, two different files, and `check` called both valid. An
 * agent writing a config for a person is the case that made this worth saying.
 *
 * What a RUN knows that a config does not: a seed given from outside (`--seed`,
 * or the API's `seed` option) fixes the file after all, and a run without one
 * prints the seed it drew. So the run takes this warning back in both cases —
 * see `TDC` — and it is `check` and the editor that show it.
 */
import { type Diagnostic } from '../errors/index.js';
import type { OpenCloseElementContext } from '../generated/TDCParser.js';
export declare const NO_SEED_CODE = "TDC309";
export declare function checkEnvSeed(envEl: OpenCloseElementContext, diagnostics: Diagnostic[]): void;
//# sourceMappingURL=env-seed.d.ts.map