thanks for your reaction.
By default, a day or week tree will assume that it is the only thing in a file when it is created and handled.
The exception is that if you have an Org entry with a property
that the date tree will be placed under that specific node. But since this is a specific property (key, not value), there was no way to target a different Org node as parent for a tree. This is now possible.
Another way to implement this would be to use different VALUES for the DATE_TREE/WEEK_TREE property - maybe that would actually be a somewhat cleaner implementation.
I'll rethink that and I will also define a test.