Files
amethyst/commonsUI
Vitor PamplonaandClaude Opus 5.5 b1e87e7667 fix(concord): an open channel reacts to a key cut, ban or dissolution; say "removed" after a cut
The channel screen read canPost() once, from plain fields the revision tick
rewrites, so a key rotation that cut us out (or a ban, or a dissolution)
landing while the screen was open left the composer up until it was reopened.
It now observes the channel's metadata flow, which that tick invalidates.

A member cut from a Private Channel was told they "don't hold its key, so you
can't read it" — as if they never had access. The cut now has its own notice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-29 21:10:45 -04:00
..