Hierarchy ready event; File System updates; WebGPU updates & more.
I am not a fan, this doesn't solve the problem to me then.
The issue is that the root node may not be known and will change all the time because I am using hierarchies often as modular pieces that can then be attached to other hierarchies. I for example have the same hierarchy once used on its own but in another case I add it as a child to an anchor object, so the on hierarchy ready is not useful again. Cases like these are everywhere as a hierarchy might be a module that is used inside other more complex hierarchy and I want the same init logic to work.
If it was called in reverse tree order (from leaf to root) the rule all children of the node the trigger ran on had their init already will be true.