test(quota-monitor): add timezone boundary coverage

[pari-28]

Description

Fixes #2930

Added services/github/quota-monitor.timezone-boundaries.test.ts to provide isolated test coverage for timezone normalization and calendar boundary scenarios in the quota monitor.

Added Test Coverage

• UTC midnight reset timestamp handling
• EST calendar boundary timestamp preservation
• IST and JST boundary timestamp updates
• Leap-year reset timestamp processing
• Daylight-saving transition timestamp handling while preserving quota state

Validation

• Added 5 test cases
• Verified locally using Vitest
• npm run typecheck passes successfully
• All new tests passing successfully

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

N/A (test-only change)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have updated README.md if I added a new theme or URL parameter.
• I have starred the repo.
• I have made sure that I have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard.
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

@pari-28 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	3433.75 KB	3433.75 KB	0 B
Total CSS	258.05 KB	258.05 KB	0 B

[Aamod007]

I reviewed the PR title/description, linked issue #2930, checks, and the diff before labeling.

Labels applied:

• level:beginner: the change is a 69-line timezone-boundary test file in services/github/quota-monitor.timezone-boundaries.test.ts, and it stays focused on reset-time handling.
• quality:clean: the test cases are short, explicit, and close to the quota monitor API being exercised.
• type:testing: the PR is dedicated test coverage for quota-monitor timezone boundaries.
• type:logic: the assertions are about timestamp normalization and date-boundary behavior, which is the core logic under test.

I’m leaving this as a neutral comment rather than approving because the repo checks are green but the PR is still carrying a failing Vercel status context. That looks like a deployment integration/auth issue rather than a code failure.

To unblock it, the Vercel GitHub integration for the repo/team needs to be re-authorized or the status needs to be marked non-blocking by maintainers. Once the Vercel context is green, this can be reviewed normally.

[Aamod007]

Good narrow test coverage for the quota monitor. services/github/quota-monitor.timezone-boundaries.test.ts exercises the reset-time parsing across UTC, leap-year, and DST-style boundaries, which is exactly where this sort of state can get slippery.

[github-actions]

🎉 Congratulations @pari-28! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨