v2.4.5
v2.4.5 — prefer OLDEST completed PR on retry
Tightens the AB#3228 reuse heuristic shipped in v2.4.4. When multiple Completed PRs match the same source/target branches, open-{mg,impl,evidence}-ado and create-feature-ado now reuse the one with the EARLIEST CreationDate rather than first-found.
Why this matters
ADO's pullrequests list endpoint returns newest-first by default. v2.4.4's first-found-wins logic could pick a phantom no-op duplicate PR (created during a retry, with permanently empty lastMergeCommit) instead of the real merge PR. The merge verb then re-trips missing_merge_commit, wedging the workflow.
The real merge is usually the FIRST attempt; phantoms are subsequent retries. Oldest-by-CreationDate selects the real merge deterministically.
Scope
Four sites: open-mg-ado, open-impl-ado, open-evidence-ado, create-feature-ado. +1 test at the symptom site.
3755 / 3755 passing.