Personal best tracking per map

Description

Players should know their own best time/score on each individual map, independent of cup context. This feeds into the personal stats screen and motivates time-attack replaying.

Acceptance Criteria

• PersonalBestEntity stores: player UUID, map name, best score, best finish time (ms), date set
• After each map in a cup, if the player's score/time beats their stored PB, the record is updated
• On race end screen (title/chat), player is shown their PB delta: "New personal best! (+42 pts)" or "3 pts below your best"
• /stats command shows player their PB for each map they've raced
• Unit test: run map twice with improving score → verify PB updated; third run worse → PB unchanged

Technical Details

• PersonalBestEntity in shared/database
• PB check happens in EndPhase before the leaderboard update
• Delta displayed via actionbar or title packet in GlintSystem/HUD layer

Dependencies

• "Persist game results in EndPhase" must be done first

Estimate

S

Start with the dependency, "Persist game results in EndPhase," then inspect PersonalBestEntity in shared/database and the PB check in EndPhase. Trace the race-end display through GlintSystem/HUD and the /stats command. Done means PB records update only when improved, the race-end delta is shown, /stats lists raced maps, and the unit test covers improving and worse runs.