export declare function envCommand(action: string | undefined, rawArgs: string[]): Promise<void>;
/** Parse `KEY=VALUE` or `KEY VALUE` from the positional operands. */
export declare function parseEnvAssignment(operands: string[]): {
    key: string;
    value: string;
} | null;
/** The prefix that makes `key` a build-time variable, or undefined. */
export declare function buildTimeEnvPrefix(key: string): string | undefined;
/** The flags `rebase cloud env set` takes, on top of the global cloud ones. */
export declare const ENV_SET_FLAGS: {
    readonly "--secret": BooleanConstructor;
    readonly "--force": BooleanConstructor;
};
/**
 * What `env set` was asked to store.
 *
 * The sharp one in this family: the old operand filter left `--project`'s value
 * in the operand list, so `rebase cloud env set KEY -p acme` parsed as the
 * `KEY VALUE` form and stored the project slug as KEY's value — a write that
 * succeeds, reports success, and is wrong. Strict parsing consumes `-p` with
 * its value, leaving `["KEY"]` and the documented empty value.
 *
 * A value beginning with `-` must use the `KEY=-v` form; the bare `KEY -v` form
 * is refused rather than guessed at, as everywhere else strict parsing is used.
 *
 * Exported so its tests drive the real parser rather than a copy of it.
 */
export declare function resolveEnvSetArgs(rawArgs: string[]): {
    flags: import("arg").Result<{
        readonly "--secret": BooleanConstructor;
        readonly "--force": BooleanConstructor;
    } & {
        readonly "--json": BooleanConstructor;
        readonly "--yes": BooleanConstructor;
        readonly "--help": BooleanConstructor;
        readonly "--project": StringConstructor;
        readonly "-p": "--project";
        readonly "-y": "--yes";
        readonly "-h": "--help";
    }>;
    assignment: {
        key: string;
        value: string;
    } | null;
};
/**
 * The variable `env unset` / `env reveal` names.
 *
 * `unset` is a delete, and the operand filter aimed it at the wrong variable:
 * `rebase cloud env unset -p acme` removed a variable called "acme" from the
 * linked project instead of reporting a missing KEY, and `env unset -p acme
 * KEY` removed "acme" instead of KEY. Both read `--project`'s value as the
 * operand — a plain word in the right position that no flag filter can catch.
 *
 * `action` is the word the caller used (`unset`, `rm`, `delete`, `reveal`); the
 * count of command words is the same for all of them.
 */
export declare function resolveEnvKeyArg(rawArgs: string[], action: string): string | undefined;
export declare function printEnvHelp(): void;