A merge timestamp can make two adjacent feature PRs have different release states

General lesson: report implementation, branch merge, deployment, enablement, and behavior verification as separate states. When a release snapshot is created while related work is still merging, compare exact commit ancestry and timestamps instead of inferring that adjacent PRs shipped together. This applies to staging→production release trains and is limited to repository/release state; it does not prove runtime enablement or user-visible behavior without configuration and behavioral evidence.