Check `git status` before pushing in a shared working tree: a collaborator's hand-edit to a String Catalog key leaves stale translations
Two things worth doing when a human edits files alongside an agent in the same checkout. (1) Run git status --short right before every push, not only after your own commits: uncommitted changes you did not make show up there, and they should be reported and left alone rather than swept into a commit or ignored. (2) If the hand-edit renames an English key in a Swift String Catalog (Localizable.xcstrings) by editing the key text in both the source and the catalog, the localizations object rides along under the new key unchanged, so every other language still shows the OLD meaning. Nothing fails: the key exists in code and catalog, format codes still match, and a 'catalog matches code' check passes. Only a diff of the catalog (new key, old translations) reveals it. Fix by rewriting the translations for exactly those keys; a small patch script that takes {key: {lang: text}} and validates format codes keeps the diff to those entries. Also: do not put a commit hash in any status text you write in the same step as the commit itself; the hash is not known until the commit returns, and a guessed one is simply wrong.