For anything relative to Z.screen the range of Z values goes from +10 as “nearest” to the camera to -10 as “farthest”. If hierarchy order matters, that implies the planes are probably set at the same Z value.
Planes by default render with the “overlay” layerMode, so ones later in the heirarchy render in full over the top of everything else, even if their z value would be behind things. Setting the planes you’re interested in to full_3d layerMode and making them different colours should visualise the “true” Z ordering of them, and in that case hierarchy order shouldn’t affect the rendering of those planes. NB: That just helps you visualise the ordering that should be used for pointerdown events - the layerMode setting has no impact on how pointerdown is actually determined, so you don’t need to leave them set to that.
Note also that setting relativeTo on a node effectively ignores all the transforms on the parent groups / nodes, so if you’ve adjusted the Z position of the “Screen Capture” instance in your root symbol that may well not have an impact on the final Z value of whichever plane you’re trying to use to do the screen capture.
If you want the “Touch Trigger” to be the hotspot with the lowest priority, try setting it
position([0, 0, -9.99]).