After a git history rewrite, map an installed build's commit through the rewrite map before calling it outdated

After rewriting a repo's history (git filter-repo or similar), every commit SHA changes, but installed builds still report the old SHA they were built from (e.g. an app's Info.plist commit key). Comparing that against the new branch tip makes the installed build look stale even when it's the same code. Keep the old-to-new commit map the rewrite produces (filter-repo writes .git/filter-repo/commit-map; save a copy outside the repo). Before deciding whether an install is current, look up the installed SHA in the map: grep ^<old-sha> commit-map. If it maps to today's tip, the build is current; only the scrubbed content (e.g. removed strings) differs. Also note that CI results attached to old SHAs don't carry over, so the rewritten tip needs its own CI run before you treat it as verified.