[T3445] FIX: prefer active/terminated sponsorships over cancelled/draft

[Danielgergely]

No description provided.

[greptile-apps]

Confidence Score: 5/5

Safe to merge; no confirmed issues remain in the changed sponsorship-selection behavior.

The completed execution check did not identify a reproducible failure.

Files Needing Attention: None.

T-Rex Logs

What T-Rex did

• Recreated the sponsorship ordering and active-only communication eligibility behavior in a focused executable check.
• Tested an active contract followed by a newer terminated contract, then the inverse input order, and confirmed that the active contract was selected in the active-then-terminated scenario.
• Ran the sponsorship-selection-01-before.py script to validate the pre-state, captured output in sponsorship-selection-02-after.log, and recorded the Odoo blocker capture in odoo-runtime-01-before.log with exit code 0.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "[T3445] FIX: prefer active/terminated sp..." | Re-trigger Greptile}