/**
 * Parsers for `qfg run` env-var → config-key mappings.
 *
 * Two callers, one grammar:
 *   - `--env VAR=key.path`  (inline)
 *   - `--env-file=PATH`     (one VAR=key.path per line)
 *
 * Grammar choices that are intentionally narrow:
 *   - Separator is `=`, not `:`. Matches `docker -e VAR=value` muscle memory.
 *     A line like `VAR:key.path` is rejected, not silently re-interpreted.
 *   - Split on the FIRST `=` only, so future config keys can theoretically
 *     contain `=` (rare, but cheap to support).
 *   - VAR side trimmed; key side trimmed once (whitespace inside the key
 *     is preserved if it's somehow legal — but we don't go out of our way).
 *   - Env files: blank lines and `#` comments are skipped. Errors include
 *     the 1-based line number so users can `vim +N file.env` to the spot.
 */
export interface RunEnvSpec {
    configKey: string;
    varName: string;
}
export declare const parseInlineEnvSpec: (raw: string) => RunEnvSpec;
export declare const parseEnvFileContents: (contents: string) => RunEnvSpec[];