pub fn warn_if_unexpected_session_source(role: &str)Expand description
#284.4: at startup, a long-running inbox-owning role (daemon, mcp,
monitor, notify) calls this to surface the “the launcher meant
to hand us an explicit identity but didn’t” failure mode. Default
behavior is a loud, force-rendered stderr warning naming the
resolved source so operators see the silent-collision risk; setting
WIRE_STRICT_SESSION=1 upgrades it to a hard exit (code 2) so a
script wrapper can fail-fast instead of waiting for the downstream
init / bind / daemon call to block on a shared relay lock.
Roles that aren’t in the inbox-owning long-running set (whoami,
send, peers, …) deliberately skip this check — they’re meant to
run from a bare CLI on the machine-default identity, and warning
every one of them would drown legitimate ad-hoc usage in noise.