onerandomusername
Deeper integration between beta and primary instances
Configuration
The beta and primary instances should, in some cases, serve to reset the settings of the primary bot in such event of both having autoresponders enabled. With a future of user configurable autoresponders, this is an issue that must be solved.
Currently, both instances are completely separate in all regards: database, config files, everything. There are no interdependency links, and even so, detecting the other bot may be difficult due to a lack of guild intent.
Stats
The stats only show the statistics for one single bot: the one that is currently running. Most of those stats are public, and could be garnered from the app-info endpoint.
Source
The source command uses the current bot hash to show source code as it's currently running. A nice to have, but probably somewhat difficult command on both bots (but easy if only on production) would be to provide a link to a diff from the current branch to the future branch. A compare of the current code to the tip, stablised with a permanent ref. This can be named monty preview
Inviting
The invite command should be smarter. It should provide an invite link for each of the stable and the beta instances.
Documentation
Perhaps, in conjunction with a diff, the autodoc can take into regard what has changed since the last release, and add in some preview messaging to the documentation, implying it's not released yet.
