Fix transitive category bracket resets

[cursor]

Bug and impact

Editing a completed upstream category knockout match could reset only its direct child while leaving deeper downstream matches (for example, the final in an 8-team bracket) completed with stale teams, scores, and winners. Bets on matches that were reset by bracket recomputation also remained settled.

Root cause

recomputeCategoryBracketAfterWinnerChange computed winners/losers from a single stale DB snapshot and performed one pass, so descendants still saw intermediate feeder matches as completed with their old winner.

Fix

• Recompute category bracket slots through an in-memory match graph until downstream state stabilizes.
• Reset every affected downstream match and return those match IDs.
• Re-settle/void bets for reset downstream matches after recomputation.
• Add a regression test for an out-of-order 8-team bracket where a quarterfinal winner change invalidates both a semifinal and the final.

Validation

• npm test -- --run tests/knockoutAdvance.test.ts
• npm run typecheck
• npm run lint (passes with existing warnings)
• npm test

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
matchpoint	Ready	Preview, Comment	May 27, 2026 10:41am