Optimize /update_points DB scoring path

[mateu]

What: Optimize the database-heavy update_points path (portable DBIC branch) by replacing object-heavy loops with set-based SQL and hashref lookups.

Why: /update_points is an admin hot path, and the previous portable implementation inflated many DBIx::Class row objects and performed per-row updates that scale poorly with player/pick volume.

How: Use hashref inflators for topology/winner lookups, run prepared SQL updates for game/team mutations, and rebuild region_score in one INSERT ... SELECT (cross-joining players/regions with aggregated winning picks), then recalculate player totals with one correlated UPDATE.

Testing: Ran script/test-env.sh prove -lv t/model_update_points.t, script/test-env.sh prove -lr t, and syntax checks with repo-local env includes.

---

Quality Report

Changes: 2 files changed, 143 insertions(+), 91 deletions(-)

Code scan: clean

Tests: skipped

Branch hygiene: clean

Generated by Kōan post-mission quality pipeline

[Copilot]

Pull request overview

Optimizes the non-MySQL (“portable”) /update_points scoring implementation in Bracket::Model::DBIC to reduce DBIx::Class row-object inflation and replace per-row updates with more set-based SQL.

Changes:

• Switch portable-path lookup queries to HashRefInflator and hash-based lookups for game rounds, team seeds, and topology edges.
• Replace object-heavy update loops with prepared SQL updates for game (winner/lower_seed) and team (round_out).
• Rebuild region_score via a single INSERT ... SELECT (player×region cross join + aggregated winning picks), then recompute player.points with one correlated UPDATE; extend the test to assert zeroed rows for players with no winning picks.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
lib/Bracket/Model/DBIC.pm	Reworks the portable scoring path to use hashref inflators + prepared statements + set-based rebuilds for region_score and player.points.
t/model_update_points.t	Adds coverage ensuring players with no winning picks still receive 4 zeroed region_score rows and a 0 total.