A regression gate cannot see an already stale signature boundary PDFFence 1.17 could make one important condition review-visible: a semantic PDF signature's /ByteRange reached the file end before a comparison and does not now. That is a regression question. But review workflows often start after history has accumulated. If both sides already have a range behind their current physical file end, a regression-only rule correctly sees no new drop. PDFFence 1.18.0 adds the complementa...