WFCORE-389 we are considering relaxing our unenforced rule against registering runtime-only operations against domain profile resources. The reason for such registrations would be to allow the DC to roll out the op to all servers that are using the profile, not to introduce some notion of runtime services that back the profile on the DC process itself. To help emphasize this point and to guard against mistakes where subsystems register such op but neglect to code them properly to not execute their runtime work on the DC, this issue proposes that the kernel explicitly reject OSH attempts to add Stage.RUNTIME steps that target /profile=* child resource in the /profile=* tree.
This acts as a primary line of defense, with
WFCORE-2815 acting as a secondary line.