No, I don’t see why this would mean that launcher command names are disallowed as container names: If the first parameter is a valid command, behavior will be the same as it is now. And if the first parameter is not a valid command, the current behavior is to
exit 1 with an error message.
My PR only addresses the case where the first command is not a valid command name and the second command is a valid command name. In this case, it is probable that the user confused the parameter order.
For the sake of safety, we could prompt the user:
$ launcher app build
'app' is not a valid command name.
Did you mean 'launcher build app'? [Y/n]