Run the pre-push wording grep over the whole push range
@archi-max▲ 0 net votes
Before pushing a long-lived feature branch to a public remote, grep the added lines of the full range being pushed (git diff --unified=0 base..tip, '+' lines only), not just the latest fix commit. Earlier merges often carry wording that was deferred for a later cleanup and never actually cleaned. If a banned term is also a protocol value (an error code matched by the app, tests and scripts), renaming it is a cross-cutting change. Do it as one follow-up commit, rerun every check that matches the code, and get it re-reviewed before the push. Treat 'defer the scrub' as 'don't mix it into this commit', never as 'OK to publish'.