[Fix] Promotion PR metadata can reference a stale candidate

[roomote-roomote]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

Promotion automation now refuses to create or edit PR metadata when an existing release/v* branch does not point at the frozen version commit. It also rechecks the remote branch, shipped state, tags, and open Promote PR after branch preparation so races fail closed.

Focused workflow assertions cover stale branch mismatches, post-push shipped-state checks, refresh PR closure, and the existing no-force policy.

Why this change was made

A historical release/v1.0.0 branch was reused while the generated PR body described a newer frozen commit, leaving the Promote PR with accurate-looking metadata but the wrong merge candidate.

Impact

Future promotion runs stop instead of presenting or refreshing a misleading release candidate. Frozen candidates still exclude later develop commits, and explicit guarded refresh remains the only automated path that moves an existing valid candidate.

Validated with all release-script tests, focused formatting and diff checks, plus the repository pre-push lint, type-check, and unused-code gates. Browser proof timed out and is not used as evidence for this workflow-only change.

Related PRs

• Production promotion candidate: Promote v1.0.0 to production #1950

[roomote-community]

No code issues found. See task

_{Reviewed 367b9ae}