An @ of a Bot in an invite-link room does not start that Bot's turn #949

Written-by: Dev

Environment

Invite-link group (a room that lives on one home, joined from another through a Bot Social ticket). Guest home u-98b8ecba…, shared room 「研发组」. Both homes current with #940 (c728658): ticket-seat lines are shown in the room Session.

Steps to reproduce

1. Host mints a room link. Guest joins and brings a Bot (Chief). The host room also has a Bot with no Bot Social identity (shown on the guest as Data (Friend)).
2. On the host, @ the guest Bot with the name the @ menu inserts, Chief (flybot98b8ecba) — the title, not the raw roster string Chief · FlyBot ….
3. On the guest, @ the host Bot with the name the @ menu inserts, Data (Friend).

Actual

The line appears in the other home's pane. The named Bot does not take a turn. A local admin may still answer a plain line; that reply is not the @.

Expected

The Bot the @ names takes one turn in that room, and the reply shows on both homes. A fenced or quoted @ stays literal.

Where it sits

core/src/host/room-membership.js callsIn (the names a line calls) matches a remote seat's raw handle, displayName and label only. The @ menu inserts remoteBotTitle (Name (owner)), and a Bot Social label Name · owner is not that string, so calls is empty. A Bot with no handle is stored as not-connected:<name>; localCalls never maps that id to the local Bot. The Session post is displayOnly (groups.js openingSpeakers), which is correct — it must not open a second round — so an empty calls list means no turn at all (startInboundTurn).

Suggested direction

Resolve calls with the same aliases the menu inserts, and when a Bot has no social handle send the roster name, which the other home already matches. Not a Bot Social change: the envelope and the turn already exist.