Accept invite: 'Talk through' copy implies a Bot is granted back; People with access stays stale; Helper appears ~10 s after the toast #228

Environment

Found by self-test on 38c00b40f0c3e6193c7a8abcfb7aad25673f40f7 (main after #217; core, plugins/social, plugins/tree) on @deepseek-ai/dsh@0.2.0-rc.2, Node 24. Two fresh installs on one Linux box: A :3080 (owner SelfA0333, @selfa0333.home, Bots Chief + Helper), B :3081 (owner SelfB0333, @selfb0333.home, Chief). Bot Social https://47-80-69-220.sslip.io. Scheduled product self-test in the browser, 2026-10-18 03:37–03:43 Asia/Shanghai. No model key in this run, so Bot replies were not tested. Screenshots were not saved; screens are described in text.

Repro

1. A: Helper → Settings → Sharing → copy invite link. Keep A's Helper Settings open.
2. B: + → Add friend. Hover the Talk through: Chief dropdown below the paste field.
3. B: paste the link → Accept invite.
4. Watch B's sidebar, and A's open Helper Settings → People with access.

Actual

• Talk-through copy implies a grant back. The tooltip on Talk through [Chief] says "Your friend only sees this Bot unless you invite them to another." That reads as: accepting gives A access to B's Chief. The earlier copy "(not shared unless you invite them to it)" (Per-Bot grants leak: accepting a Helper invite exposes the joiner's Chief; face-room Chief shows in Friends' Bots; Manage access wrong/raw #138, Regression of #138: joining a friend's invite still puts the joiner's Chief on the inviter's main list #161) said the opposite. The panel does not say plainly what accepting shares.
• People with access is stale. After B accepted, A's open Helper Settings still says "Nobody has this Bot yet. Invite a friend to grant it." It did not refresh.
• Late list update on B. The toast "SelfA0333 shared Helper with you." shows at once, but Helper appears in B's list only about 10 s later.

Expected (owner design: per-Bot grants, nothing published)

• Accepting an invite grants only the invited Bot (Helper → B). B's Chief is not shared with A unless B invites A to it.
• If a talk-through Bot is still needed by the protocol, the copy says plainly that it is not shared (e.g. "Chief talks for you. A can't use Chief unless you invite them."). Better: no picker unless B has more than one Bot.
• A's People with access shows B right after the accept, without reopening the page.
• Helper appears in B's list together with the success toast.

Hunch (code read, not verified)

• Tooltip: plugins/social/client.js ~L1323 (fs-join-as label title).
• ManageAccess (plugins/social/client.js ~L1373) loads social/access once in useEffect([bot.id]) and never polls, so a grant made while the page is open does not show.
• The accept handler shows the toast before the next roster refresh brings Helper in. The new Bot could be inserted from the remoteBots({ fresh: true }) result it already fetched.
• Whether B's talk-through side really creates a usable grant for A on B's Chief should be checked against Granted friend Bot never shows for the grantee: the talk-through grant hides it (regression from the #161 fix) #178 (that grant exists in B's state.json and caused Granted friend Bot never shows for the grantee: the talk-through grant hides it (regression from the #161 fix) #178).

Related

#138, #161 (joiner's Chief exposed, closed), #178 (talk-through grant, closed), #173 (Manage access wording/depth, open).