Revoke access silently degrades shared face-to-face room #1072

Reproduce

SelfA1025 / SelfB1025 → social.botawaken.com, face room 846271, 2026-10-25 continue:

1. B has grant to A's Chief; both in face room 846271.
2. On B: Bot detail → People with access → Revoke Chief (SelfA1025).
3. Observe A's view of room 846271.

Expected

Revoke ends the grant cleanly. Shared face room either stays usable for local members or clearly shows the peer left / access ended — not a stuck loading state.

Actual

After Revoke (instant, no confirm):

• B Past rooms count rose; grant cleared ("Nobody has this Bot yet").
• A's 846271 degraded: stuck "Loading history…", header still Face-to-face · 846271, panel "1 person · 1 Bot, Waiting for others to join" while B is gone.
• Cross-home @ in that room then failed / unclear (retest needed in a fresh room after friendship restore).

Environment

• Social: https://social.botawaken.com
• Shots: /workspace/social-ui-deep-test/continue/

Suggested scope

On grant revoke, tear down or update peer membership in shared face rooms so the other home does not stick on Loading history / Waiting for others.

Source

product UI deep-test continue 2026-10-25 (owner: file + fix)