Face rooms: another home's Bot answer doesn't count — local Bot forced to re-answer/re-plan; friend Bot's @all wakes all my Bots #475

Summary

In a face-to-face room (面对面房间, multi-home room via Bot Social), every home runs its own round over only its local Bots. The round logic in core/src/host/groups.js ignores what another home's Bots already posted, so:

1. Forced fallback after a friend already answered. answeredAlready(round) and fallbackDue(round) look only at round.slots (local Bots). When a friend's Bot (e.g. their Chief) has already answered or posted a plan for the person's line, and all local Bots reply [PASS], fallbackDue is still true and the first local Bot is forced to answer (route.forced, ROOM_REPLY_FORCED — "nobody else answered"). Result: a second plan for the same request.
2. A friend Bot's @all / @所有人 wakes every local Bot. openingSpeakers() only returns [] for face-room Bot posts when !all (if (isFaceRoom(room) && !all) return [], ~line 739); with @all it falls through to return admin ? [admin, ...] : members, so a Bot in another home can start a full round of all of my Bots. This is the gap left by Face rooms: a plain line should let every Bot in the room answer (one round, capped), not only the first (follow-up to #287) #295 (which made a person's plain line answerable in one capped pass) and Face-to-face: a human message that does not @ the Bot still starts a Chief model turn #167 ("only @name / @ALL calls a Bot") — Bots in two homes can still set each other off with @all.

Investigation: local clone at main bae4128.

Expected behavior

• Cross-home answers count. Any Bot line (local or another home's Bot) logged in the room after the current room.faceLine (the person's line that opened the routed round) counts as "answered":
  • answeredAlready is true, remaining local slots are not asked (no model call), and
  • fallbackDue is false, so no forced fallback when a friend's Bot already answered/planned.
• routeNote mentions it. When a friend's Bot already posted for this line (e.g. a plan) and a local Bot is still asked (broadcast-style line or explicit @name), routeNote() tells it: "<X> already posted a plan; add only your role's part" (do not re-plan, do not repeat).
• A friend Bot's @all / @所有人 does not wake all local Bots. In a face room, a Bot post from another home with @all starts no local round (same as a plain Bot post, Face-to-face: a human message that does not @ the Bot still starts a Chief model turn #167).
• A friend Bot's @MyBot still wakes only that Bot (unchanged).
• A person's @all (owner or attested friend line, Face rooms: a plain line should let every Bot in the room answer (one round, capped), not only the first (follow-up to #287) #295/Face room: friend's plain line bypasses face-room routing and no-follow-up rule #462) keeps its current behavior.

Acceptance criteria

• In core/src/host/groups.js, answeredAlready / fallbackDue consider Bot lines in room.log with seq > room.faceLine.seq (from any home, botId set, not notices/face-notice) as answered for the current face line.
• No route.forced slot is pushed when another home's Bot answered the current face line after it was posted.
• routeNote() names the friend's Bot that already answered and says to add only the local Bot's role-specific part.
• openingSpeakers(): a face-room post by another home's Bot containing @all / @所有人 returns [] (or only explicitly named local Bots); a friend Bot's @MyBot returns only MyBot.
• Tests in core/test/rounds.test.js cover:
  • friend's Bot answers a plain owner line → all local Bots PASS → no forced fallback, no local post;
  • friend's Bot posted a plan → local Bot still asked gets the "already posted a plan; add only your role's part" note;
  • friend Bot posts @all and @所有人 → no local Bot turn;
  • friend Bot posts @MyBot → only MyBot gets a turn;
  • existing Face rooms: a plain line should let every Bot in the room answer (one round, capped), not only the first (follow-up to #287) #295 / Face rooms: a plain line should be answered by the Bot(s) it is for, not by every Bot (follow-up to #295) #299 / Face room: friend's plain line bypasses face-room routing and no-follow-up rule #462 tests still pass (own-home fallback still fires when nobody in any home answered).
• Mirror the change in ds-bot/src/host/groups.js / ds-bot/test/rounds.test.js only if that copy shares the face-room code path (check; do not diverge silently).

File pointers (main @ bae4128)

• core/src/host/groups.js
  • routeFor() ~L339, answeredAlready ~L352, fallbackDue() ~L357, forced fallback in runRound() ~L403
  • routeNote() ~L202, roomPrompt() ~L222
  • currentFaceLine / openFaceLine ~L76–82 (room.faceLine)
  • openingSpeakers() ~L708, the face-room Bot-post rule ~L739
• core/test/rounds.test.js

Related

• Face rooms: a plain line should let every Bot in the room answer (one round, capped), not only the first (follow-up to #287) #295 (face rooms: plain line lets every Bot answer, capped) — this closes its cross-home gap
• Face rooms: a plain line should be answered by the Bot(s) it is for, not by every Bot (follow-up to #295) #299 routing (route/fallback), Face room: friend's plain line bypasses face-room routing and no-follow-up rule #462 (friend's plain line routing), Face-to-face: a human message that does not @ the Bot still starts a Chief model turn #167 (Bot posts only call by @name / @ALL)
• Team mode via groups: task layer step 1 - responsible-owner authority, FLYBOT-TASK envelope, workBotId #149 team mode via groups (responsible owner) — longer-term task layer
• [Team] Recover task handoffs without duplicate work #55 recover task handoffs without duplicate work
• Follow-up feature: Face rooms: selectable room lead (总负责人) picked by the room creator, cross-home roster with roles, one plan per request #476 selectable room lead for face rooms (depends on this)

Scope: bug fix only; no UI changes.