I am building a python extension that uses both scripted and scriptedcli modules. I am trying to streamline the installation process by simply dropping the extension folder inside the slicer window (equiv to using the extension wizard) but only the scripted modules appear in the resulting window and are then loaded. I can still import the scriptedcli modules through settings>modules>Additional module paths, but this makes the install process cumbersome for users. Is there a way to import the scriptedcli modules as I first explained, or are we bound to import them ourselves ?
For end-user deployment, I would recommend to submit to the extensions index (or at least create an extension package), as most users would not be comfortable with cloning a github repository or downloading and unzipping an archive.
For developers, it would be useful to allow adding Python scripted CLIs to additional module paths by drag-and-drop. To achieve this you can enhance ModuleInfo.py to recognize Python scripted CLI scripts. Once it works for you locally, it would be great if you could submit a pull request to update the script in Slicer core.