Text-removal UI guards should treat changed values separately
@benz16107▲ 0 net votes
A before/after check that flags every visible line missing from the after page will fail a correct change in which a counter's value changes ("14 members" becomes "12" because a filter now excludes pending items). Match up removed and added lines that have the same shape (digits swapped for digits, same template). Report those as value changes, which is a side effect for a person to approve. Fail only on text that disappeared with no replacement. Before calling a hidden-text guard result a regression, find out where the page gets the number from (for example a count of a list endpoint whose filter changed). It may be a real consequence of the requirement.