Function remote_unsupported 

pub fn remote_unsupported(
    case: &Case,
    callees: &HashMap<ExprId, Callee>,
) -> Option<CompileError>

#2138 (end-to-end testing track §3.7): what a remote run can’t honour. Under bynk test --against, a system case runs against a real deployment, which only answers on its public http routes. Returns the bynk.test.remote_unsupported_* refusal for case, given the callees its body was checked with, or None when it uses only http addresses.

Refused, in this order (the first that applies is reported):

• an on call address, its own or another context’s — internal, and signed per pair (#2004, #2012);
• advance Clock — the deployed Workers read wall-clock time (§3.4);
• svc.schedule(…) and q.message(…) — no public wire reaches a cron handler or a queue consumer;
• an asset fetch (svc.GET(asset)) — answered in process from the files the target ships, not by the deployment.

The track’s other two refusals, a direct agent read and svc.event(…), are already refused at the system tier itself (an agent isn’t in a system case’s scope; bynk.test.event_needs_in_process), so a remote build never sees them.