Honor node.target when target is unavailable
node.target e.g. inside a filter chain seems to be more of a suggestion. It'll use that target when available during start, but will switch to something else when he target is/becomes unavailable.
I find this odd and inconvenient. There is a reason to set the target, and that shouldn't be overridden. My suggestion would be to make nodes disappear/become unavailable when its target does. Possibly through a config option?
Many thanks! :)