It was certainly the case that top level composites used to be built independently. Chaning back to this scheme would preserve the user defined composite name. In the distant past this did prevent inter-composite wiring but now we have the endpoint registry this shouldn't be an issue
However this won't fix the same problem that occurs with manually included composites. Maybe this is less of an issue as it happens less often and at least the user will be be aware of it when it does happen, i.e. it isn't the result of some runtime magic. The only alternative I can think of is, as you say, to cache the original composite name somewhere. Regards Simon
