The AI Automators module is a very powerful system doing an awful lot, akin to the AI module itself:
Due to it trying to be all things to all people in a single module, it does not list all of its dependencies (field_ui is required to link AI Automators to fields; ai_ckeditor is required to use AI Automator Chains outside of custom code) because not all users will be using that specific functionality. Whilst there are work arounds in place to warn users and prevent the UX getting too confusing, there is still a lot of database tables and code being used for functionality that at least some of its users won't want.
In order to give users as much control over what is added to their site - and to reflect the extreme flexibility of the AI Automators core functionality - this module should be split into its own project. It should be split into multiple (sub-)modules, each responsible for one part of the functionality:
In this way, users who want the current functionality can enable all modules, but users who only want a specific part of the functionality can enable a smaller sub-section of modules. This will give their sites a smaller footprint, and allow each module to properly declare its dependencies to assist with the installation process.
Active
1.0
AI Automators
Keeping the mMR in draft as there is further work to be done.