League Ties — Time-Capped & Single-Game Formats

Tied regular_season matches are now a first-class result. The score modal shows a 'Complete as Tie' confirmation when the game count is even; standings credit point differential without W/L; DUPR receives each game as its own submission so ratings still move. This update is designed for league organizers and players who want a better league play experience — less manual work, more control, and a smoother workflow.

What's Included

Tied matches recorded honestly — winner_id stays null, status='completed', tied?=true

Rung ladder ordering unchanged — existing wins → PD → H2H → prior_rung_rank chain handles ties naturally

Win percentage now follows USTA convention — ties excluded from the denominator (1W-1T = 1.000, not 0.500). No-tie leagues unchanged.

DUPR per-game submission — each LeagueMatchGame submitted as its own DUPR match with its own dupr_match_id; retries skip games already accepted (idempotent)

Parent dupr_submission_status='partial' when some game submissions fail; the next batch sweep retries only the failed games

Playoff, MLP encounter, and challenge-ladder matches still require a winner — validation rejects ties on those formats

Mobile + web scoring modals show 'Complete as Tie?' confirmation only when match.tieable is true (server-resolved per match)

Parity tripwire spec locks in the documented asymmetry: leagues allow ties, tournaments do not

Why This Matters

League Ties — Time-Capped & Single-Game Formats addresses a real need for league organizers and players. Tied regular_season matches are now a first-class result. The score modal shows a 'Complete as Tie' confirmation when the game count is even; standings credit point differential without W/L; DUPR receives each game as its own submission so ratings still move. By building this directly into the platform, league organizers and players save time and get a more reliable experience — no workarounds, no third-party tools, no spreadsheets.