Yep. Grandfathering, deprecation. It's a new implementation of the same concepts. And ditto for test coverage quality gates. I've seen that pattern used to get

Yep. Grandfathering, deprecation. It's a new implementation of the same concepts. And ditto for test coverage quality gates. I've seen that pattern used to get a frontend codebase from 5% coverage to >80%. It was just a cycle of Refactor -> Raise minimum coverage requirement -> Refactor again -> Ratchet again, with the coverage gate used to stop new work from bringing down the average.