[codex] Fix leaderboard sorting, timelines, and duplicate claims

[B-EtterDigital]

Summary

• Fix leaderboard sort/filter transitions so token/cost switches fetch page 0 instead of reusing stale seeded or later-page rows.
• Key leaderboard hook results to their active request so stale page-2 responses cannot repaint a new page-0 sort/filter state.
• Render profile usage charts on continuous calendar days, filling missing days with zero values and showing when data is stale because the user has not uploaded recent usage.
• Fix duplicate CLI/OAuth identity claiming for unverified CLI aliases such as B-etter.Digital versus the real GitHub login B-EtterDigital.

Root cause

The leaderboard could reuse server-seeded default rows after user interaction, and older hook results were not tied to the request that produced them. That allowed later-page rows to appear as rank 1 after sort/filter changes.

Profile charts used the last recorded rows rather than the last calendar days. Sparse uploads compressed the timeline and hid missing recent days.

CLI submissions can store a raw X-GitHub-User value. If that value is a punctuation/case variant of the real GitHub handle, the existing exact github_username claim lookup misses it, leaving duplicate leaderboard identities.

Validation

• pnpm test passes on this branch: 19 ccusage tests and 19 site-bug tests.
• Combined merge simulation for PRs [codex] Fix leaderboard sorting, timelines, and duplicate claims #72, [codex] Add expandable profile model list #73, [codex] Make profile rank more prominent #74, [codex] Add custom open-to-work contact email #75 passes pnpm test: 19 ccusage + 9 open-to-work + 10 model-list + 6 rank + 19 site-bug tests.
• Combined production build passes in a temp worktree with dummy auth/Supabase env values.
• git diff --check passes.

Notes

Feature requests remain in separate PRs: #73 expandable model list, #74 rank presentation, #75 custom open-to-work email.

[vercel]

@B-EtterDigital is attempting to deploy a commit to the sculpt Team on Vercel.

A member of the Team first needs to authorize it.