Well, well, well. The problem persisted through several site re-builds but seems to have corrected itself on its own. Very peculiar. Anyway, for now, the problem is not reproducable. It's possible that the problem was nothing more "mysterious" than a simple page caching issue, and in my panic I didn't see the obvious. Never mind (for now).