It would be nice to generally clean up the public API:

• BotConfig could use a builder pattern to construct itself, with a few defaults.
• the run function might be split up, with the AppCtx being refactored into a TrinityBot that just contains what's needed to make the core things work. Then it's the responsibility of the library user to create a TrinityBot, and run it.
• Splitting the lib and binary into two different crates would also help trim down dependency usage in the lib.