While interactively testing the HRD version of Sculpt 25.10, I noticed that the disabling of nodes via x has an unexpected effect on the preceding node. Instead of ignoring the entire content of the disabled node, (some) attributes are wrongly interpreted as belonging to the preceding node. E.g., when disabling the start node for the system shell in the window-manager preset, the preceding black_hole component gets restarted, but with the start-node content of the (presumably disabled) system shell.