having the python API as the primary interface sounds like the correct solution

only reason why I thought having something like `assembly.add_cli_applet` is that when going from the CLI to the python API for someone not intimately familiar with the project you would have to:
* find out where in the package the applet I am interested in is located
* figure out how cli args map to stuff in the python API for the applet

not a very high overhead thing at its face, but if I am doing a quick 30s script for trying something out then it removes some friction

again, just my perspective as someone completely new to everything, take me as a single data point :)