Face-to-face: human messages still do not sync across two instances #124

Context

Cloud UI self-test on ThinkFlowLab/FlyBot 87c69408 (includes #118 / Fixes #117) with two box instances (3080 BoxA @boxa.home, 3081 BoxB @boxb.home) against production Bot Social https://47-80-69-220.sslip.io.

Bot Social API face-room send/list looked fine in an earlier API pass; the FlyBot client chat still does not show the other side's human lines.

Repro

1. Open both instances; join the same face-to-face room (both showed join lines: “BoxA's BoxA joined” / “BoxB's BoxB joined”).
2. On A type a short human message (e.g. ui-smoke ping from A) — appears only on A.
3. On B type ui-smoke ping from B (also observed via POST /api/session/prompt 200) — appears only on B.
4. Neither side ever shows the other's message.

Expected

The other instance sees human lines (as fixed / intended by #117 / #118 FLYBOT-FACE-HUMAN path).

Actual

Messages stay local. Sending also bumps “N turns N steps”, so a human line is treated as a bot turn.

Notes

• No model key on the box — Bot LLM replies were not tested; this is human↔human only.
• Related: Face-to-face: card clipped/stale, tiles lack owner name, second side misses join and messages #117, fix(social): Face-to-face card, join and messages across two instances #118, Face-room poll: empty handle norms to "@", GET as=@ 404 spam in web.log #122 (poll as=@).

Environment

SHA 87c69408bc7f2e0911b90a2804b717a72b0e46fd, dsh 0.2.0-rc.2, 2026-10-16 Asia/Shanghai.