✨ Deployment Consistency - Ensure production deploy includes PRs merged during deployment

[edkranz]

Requested by: @edkranz via YakShaver.ai 🦬
cc: @edkranz, @jakebayliss, @wicksipedia, @tiagov8, @adamcogan, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (1 min 18 sec)

Pain

When running a production deployment in Rules V3 (TinaCMS), the deploy can take ~20 minutes. During this window, content PRs can be merged into main, resulting in the production site finishing deployment with outdated content. Implement a solution to ensure any PRs merged during an active production deployment are included, or the deployment is retriggered/blocked to guarantee the deployed site is fully up to date.

Acceptance Criteria

1. Production deployments cannot complete with content that is older than the current main branch at deploy completion time
2. PRs merged into main during an active production deployment are automatically included or trigger a follow-up deployment
3. The solution is automated and does not rely on manual intervention
4. Deployment behavior is documented and clearly communicated to the team
5. No regression to existing deployment stability or performance