capture reframe's whole write picks the previous distinct frame state in git log date order, so across a --no-ff merge where both parents moved the frame the before state is whichever parent's commit is newer, and changed depends on timestamps rather than topology: a record can under-report the surfaces the merged rewrite moved

capture reframe's whole write picks the previous distinct frame state in git log date order, so across a --no-ff merge where both parents moved the frame the before state is whichever parent's commit is newer, and changed depends on timestamps rather than topology: a record can under-report the surfaces the merged rewrite moved

Grounds

• pursued: a merge where the branch moves two surfaces and main a third records the branch's two in both timestamp orders, as a squash would; a before state or changed that moved with commit dates would show it wrong