[Bilb]

sogs-ban asked Continue? [y/N] without showing who the ids belonged to, so a moderator could not check a ticket's ids against the accounts before banning them.

Before the prompt, and in a dry run, each id is now listed with the display name from its newest post:

  05abc...def  posted as 'Mallory'
  05123...456  posted, with no display name
  05789...abc  no recent posts

• Where the name comes from: SOGS stores no profiles, so the name exists only in the profile a client attaches to each message. names.py reads each room's last 256 messages (the most /messages/recent returns), matches them by either blinded form of the id, and decodes the display name from the message's protobuf. On our three rooms that is currently their whole history.
• Unreadable rooms: a room that does not answer 200 is named under the list, so its posters do not read as "no recent posts".
• Read-only: the lookup only issues GETs, and runs before anything is sent.

Tested with tests/sogs/test_names.py (decoding padded and unpadded content, newest post wins, deleted posts skipped, unreadable rooms reported) and with a live dry run against open.getsession.org; decoding was also checked against real posts there.

https://claude.ai/code/session_019cnvrsCXsqLykDyQburD2f

[Bilb]

Folded into #76 so the three changes can be iterated on together.