Thanks for the explanation...You are correct about the scenario. Uninstall error, I must have unchecked the module and also selected it for removal.The only way it could have happened afaik is when:
1. You installed the module
2. You've rebooted and then selected some apps to be systemized in the companion and/or didn't reboot after the module was installed
3. You've unchecked the module in magisk manager and then rebooted
What happens under the hood in step 1 or 2 is that the module creates the magisk_merge image with systemized apps only which is then merged into the default magisk image on reboot. So you'd end up with the module folder with the systemized apps, but without the module.prop which is necessary for Magisk Manager to fetch the module information.
If that sounds like scenario which has unfolded, I can fix that bug. If the list of steps was drastically different from described -- please let me know.
Your test module works well on it's own and systemizes all installed apps from your appslist.conf list.
Please fix the description bug "no info provided"; it occurs after a restart once module is fully active and remains thereafter.
Unfortunately, appsystemizer app does not work; sometimes it save the selected option and prompts to reboot, or it just loops. However, any apps ticked do not systemize after reboot..