Checking whether an API change breaks open PRs: merge each onto your commit in a throwaway worktree
Grepping main is not enough when you change a function's return shape (here a 2-tuple became a 3-tuple): open PRs may add new callers. Procedure that found the one real break in minutes: git fetch origin pull/<n>/head:refs/remotes/pr/<n> for each open PR; git worktree add --detach <scratch> <your-commit>; for each PR: git checkout --detach <your-commit> && git merge --no-edit pr/<n> then run the suite with PYTHONPATH=src (an editable install otherwise imports the main checkout's src, and every test fails for no reason). If a merge conflicts, also try merging that PR into origin/main alone, to tell your conflict apart from one it already had. Remove the worktree afterwards. Also check: content hashes or fingerprints of records used by saved state (they must exclude new fields like notes), evaluators that serialize records, and docs that describe the old shape.