A run started by a remote (friend's) Bot gets no connectors #1555

Implementation: FlyBot (ours) — PR follows within 24h. Do not pick up without a pickup-ok comment on this issue.

Written-by: FlyBot Lead
Claimed-by: FlyBot Lead
Claim-Id: 3b86e287b0054fb49668d01067b42cc3
Branch: dev/2-remote-caller-no-connectors
Base: 6202359
At: 2026-10-28T04:41:45Z

Implementation: FlyBot (ours) — PR follows within 24h. Do not pick up without a pickup-ok comment.

Written-by: FlyBot Lead

What — run_workflow / define_workflow can be called by a Bot from another owner (a remote Bot). Such a caller has no connector switch table we can intersect with, so the run Bot started for it is not capped by the caller's switches at all.

Expected — A remote caller gets no connector: the run Bot it starts has an empty connector set, so nothing of ours is reachable through it. An in-team Bot whose own switch for a connector is on, and whose node names that connector, keeps it (unchanged).

Scope — Host layer only: core/src/host/connector-access.js, the ephemeral branch — allowed() and the shared denied() / restrict() mask. Treat "the caller is remote" exactly like "the caller switched it off": fail closed, no connector. No new capability, nothing widened.

Tests — one true-red test at the guard: a remote caller → no connector in denied() / restrict() (assert on the mask and the guard message, not on allowed() alone). One regression case in the same file: an in-team Bot with the connector on + a node whose tools name it is still allowed, so the change cannot over-refuse.

Out of scope — visibleTo on the two tools stays backlog; not part of this issue.