Reaction and prompt listeners feel very adhoc and unstructured.

[Gnuxie]

We create lots of reaction prompt listeners for protections and commands. Some of these are expected to implement parts of interface-manager, such as prompts for promptForDefault, promptForSuggeestions, and promptForConfirmation. Others are just there to implement functionality like in BanPropagationProtection, WatchRoomsOnInviteProtection, and ProtectRoomsOnInviteProtection.

The prompts that implement interface-manager prompts are pretty large and they'd be a pain to implement for someone with a different bot. So we should think about porting the ReactionHandler to interface-manager. This won't need very much, just callbacks for sending reactions to events and rendering DeadDocument with additional context.

The prompts that implement protection functionality really should be rewritten as commands. When their trigger happens (such as a ban or an invitation) they are basically rendering an event with a command continuation prompt. I'm not sure what code needs to be created to accept a command description and create such a prompt.
The other part of this is the command itself which will replace the adhoc prompt listener. This will save us a lot of pain.

We also need to consider replies or some kind of command as a method for reacting to the prompts, and not just reactions.