Function remote_env_disagreement 

pub fn remote_env_disagreement(
    case_name: &str,
    span: Span,
    env: &BTreeMap<String, String>,
    vars: &BTreeMap<String, String>,
    secrets: &[String],
) -> Option<CompileError>

#2138 (end-to-end testing track §3.7): a case run against a named target. A deployed target already runs with its own variables, so the runner can’t apply the case’s env; the case runs only if its env and the target’s declared vars agree on every name either mentions. Refused (bynk.test.remote_unsupported_env), first match reported:

• an entry naming one of the target’s secrets — a secret comes from the environment, never from a suite;
• an entry the target doesn’t declare, or declares with another value;
• a declared variable the case doesn’t set, which would read as None in process, so the case wouldn’t promote unchanged.