GC7D3PC checker is no longer qualifying previously accepted low elevations (-1000 to 0)

Question

My checker (https://project-gc.com/Challenges/GC7D2PC/29050) is no longer qualifying previously accepted low elevations (-1000 to 0):   

baloop  

before: 1. GC95BJE, 2. GC62JPJ, 3. GC50C11, 4. GC95BM1, 5. GC509ME, 6. GC99073, 7. GC95BJV, 8. GC50C24, 9.GC95BJT, 10. GC2TQ9N, 11. GC95BGZ, 12. GC62JQ1, 13. GC95BM5, 14. GC9906P, 15. GC49X7J, 16. GC999B9, 17. GC50C0M, 18. GC5ERJW, 19. GC95BJC, 20. GC509JY,

after: 20 * -1000-0: GC49X7J, GC62JPJ, GC49986, GC999B9, GC95BJV, GC95BJE, GC295AQ, GC2TQ9N, GC5ERJW, GC5ERNR,  

Aronel

before: 20 * -1000-0: GC58QBK, GC58H8A, GC5JNDM, GC9B0RW, GC234BX, GC7KRF8, GC8NFP6, GC62JPJ, GC1KKMX, GC6YAND, GC62JQ1, GC31B28, GC1GA93, GC2HTZA, GC90551, GC21A86, GC6ZC84, GC5PCRA, GC58BW3, GC2M0FA,

after: 20 * -1000-0: GC1GA93, GC7KRF8, GC62JPJ, GC1KKMX, GC51NVR, GC5JNDM, GC234BX,

Answer 1

I checked a handful of the mentioned caches and none of them had an elevation below 0 so to me this looks like a recalculation of data (something that's done occasionally as the point of Project-GC is to have active and correct data) and not a bug.