After recent changes to the report, the problem is no longer present. I still have no idea what the root cause was, nor what change made resolved this issue.
I have before and after versions of the report (though no easy way to diff them), which I can submit if desired.