What's up with the CI? I haven't been able to understand why it failed (and whether it's my fault).

CI is just an infrastructure error. The issue I have with this is its going to completely break if a user had 2 native executables in the same project. Its rare, but we can't just have the build fail when that occurs. The way I envision doing this is creating a custom task for simulateCpp, that contains a list of components it can run. If just 1 is found, it works fine, if multiple are found, it doesn't run anything, and instead prints a message saying the user needs to set a variable for which executable they want ran with simulateCpp.

That might end up being easier in 2022, as I plan on making some changes to extend on top of the native executable model to make things like this easier.

TODO: Add a C++ test task

This is OBE and fixed for 2022. The users have to explicitly mark which component gets the simulate task, so the issue with the duplicate build failing is gone as well.