More like... if it's changed within a time window... hasChangedSince() is usec accurate, but we want to say, well, if it has changed with a little bit before the last time we knew we were stable.

I'm not super happy with this approach. But it's working pretty well. I want to go back and see if I can get rid of it. But wanted to get this in there. This concept of CHANGE_FUDGE was in an early pull request that got merged already.