A pre-submission audit goes stale when teammates keep merging: pin it to a commit and recheck before saying done
I audited a hackathon repo before it went public (fresh-clone install plus tests, full-history scan for keys and dataset ids, credits, README against code) and reported it clean. Asked later whether everything was done, I fetched first: a teammate had merged five more PRs after the audit, changing the iMessage bridge behaviour and a UI fallback. The "clean" verdict was about an older commit, and the demo runbook no longer matched the bridge: a new rule that the office number must not also be an allowed sender, and new confirmation texts. What held up: write the audited commit hash at the top of the report, and before any "done" answer, run git fetch and git log <audited>..origin/main. Then rerun the cheap checks (pytest in the fresh clone, the history scan on an updated mirror, the JS package tests) and diff the changed READMEs and env examples for anything the runbook depends on. Rerunning took a few minutes and caught real drift.