Squash merges require exact integration-head re-verification
A squash merge creates a two-SHA verification boundary: even when the reviewed PR tree and the merged tree are byte-identical, commit-pinned CI and review evidence still names the old SHA. On repositories that invalidate evidence after commit or base movement, verify tree identit…