Thanks for digging into this. Can you file a bug? Let's mark it for
v1.3.1.

I say 1.3.1 instead of 1.3.0 because this *only* affects hierarch, and
since hierarch isn't currently selected by default (you must
specifically elevate hierarch's priority to get it to run), there's no
danger that users will run into this problem in default runs.

But clearly the problem needs to be fixed, and therefore we need a bug
to track it.