/**
 * Remediation wording — the "here's how to fix it" half of a configuration/auth error.
 *
 * The library's default text names CLI affordances (`--api-key`, `BFFLESS_API_KEY`,
 * `.bffless/config.json`). That is right for `bffless rules push` and wrong for every other
 * embedder of `bffless/lib`: the deploy-proxy-rules GitHub Action, for instance, has no
 * flags and no committed config — its user sets an `api-key` *input*. Telling that user to
 * "pass --api-key" sends them looking for a flag that does not exist.
 *
 * So the wording is data, not string literals baked into throw sites: pass
 * `deps.remediation` to override any subset of it (see `ClientDeps`).
 */
export interface Remediation {
    /** No API URL could be resolved from flags, env, or config. */
    apiUrl: string;
    /** No API key could be resolved from flags or env. */
    apiKey: string;
    /** No project was named by a flag or by config. */
    project: string;
    /** The API rejected the key (HTTP 401/403). */
    auth: string;
}
/** Default wording, phrased for someone running the `bffless` CLI. */
export declare const CLI_REMEDIATION: Remediation;
/** Fill any unspecified field from {@link CLI_REMEDIATION}. */
export declare function resolveRemediation(overrides?: Partial<Remediation>): Remediation;