[BUG] Daily/weekly/monthly leaderboards can show negative solved counts and negative scores

[Tamcodes4]

Description

processTimeframe() in scripts/sync-leaderboard.js computes each user's period delta via plain subtraction with no floor at zero. If a user's cumulative LeetCode totals ever read lower than the previous snapshot, the leaderboard displays a negative count and negative score for that period.

Steps to Reproduce

1. Run sync-leaderboard.js to produce a baseline daily.json snapshot for a user.
2. Simulate a lower easySolved/mediumSolved/hardSolved value on the next sync for that same user (e.g. via a temporary API glitch, or by manually editing the previous snapshot's data to be smaller before the next sync run).
3. Run the sync again and inspect the resulting daily.json/weekly.json/monthly.json.

Expected Behavior

Period deltas should never go below zero, a user can't "unsolve" problems, so the displayed progress for that period should floor at 0.

Actual Behavior

The score and per-difficulty counts go negative and are rendered as-is (e.g. -3) on the leaderboard.

Root Cause

data[i].data.easySolved -= previousData[previousIndex].data.easySolved;
data[i].data.mediumSolved -= previousData[previousIndex].data.mediumSolved;
data[i].data.hardSolved -= previousData[previousIndex].data.hardSolved;
data[i].score =
  data[i].data.easySolved +
  data[i].data.mediumSolved * 3 +
  data[i].data.hardSolved * 5;

No Math.max(0, ...) guard, unlike equivalent delta logic elsewhere in the codebase (historical-graphs.js, compare.js) which already clamps correctly.

Suggested Fix

data[i].data.easySolved = Math.max(0, data[i].data.easySolved - previousData[previousIndex].data.easySolved);
data[i].data.mediumSolved = Math.max(0, data[i].data.mediumSolved - previousData[previousIndex].data.mediumSolved);
data[i].data.hardSolved = Math.max(0, data[i].data.hardSolved - previousData[previousIndex].data.hardSolved);

Affected Files

• scripts/sync-leaderboard.js

[github-actions]

Thank you for opening an issue.

Please review our CONTRIBUTING.md guidelines before getting started.

A maintainer will review this issue shortly. If you would like to work on the issue yourself, please leave a comment requesting assignment.

Issue Assignment Policy

• The issue creator is given the first priority to work on their issue.
• If the creator declines or does not request assignment, the issue will be assigned to others in the order of requests received.
• Please do not submit PRs or begin work until you are officially assigned.

Note: This project is currently maintained by a solo maintainer, so reviews, assignments, and responses may sometimes take a little time. Thanks for your patience.

[Tamcodes4]

Hi! I would like to work on this issue, kindly assign it to me under GSSOC26!

[Abhinav21Chauhan]

/claim

[Tamcodes4]

Hi @jagdish-15, flagging an assignment mismatch on this issue. I was assigned to #238 (see Assignees), but #249 was opened by another contributor for the same issue without being assigned, per the project's CONTRIBUTING.md policy ("do not start working on an issue or submit PRs until you are officially assigned"). I already have a fix ready that matches the suggested fix in the issue. Let me know if you'd like me to open a PR, or if you're going ahead with #249, happy to defer either way, just wanted to surface this before duplicating effort.

[jagdish-15]

@Tamcodes4

Thank you for reaching out. Since you opened this issue first and requested assignment before anyone else, this issue will remain assigned to you.

Feel free to open a PR with your fix.