feat: handle GitHub API rate limits with user-visible feedback (#93)

[Harsh-Codes-77]

Handle GitHub API rate limits with user-visible feedback

Implements graceful rate limit handling for GitHub API 429 responses:

• New githubFetch wrapper utility centralizes 429 detection and throws typed RateLimitError
• New RateLimitBanner component displays rate limit status with countdown to reset
• Updated 4 API metrics routes to catch rate limits and return 429 responses with reset timestamp
• Updated 4 dashboard components to detect rate limits and show banner instead of generic error

Users now get immediate, friendly feedback when hitting GitHub API limits instead of confusing error messages.

[vercel]

@Harsh-Codes-77 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Priyanshu-byte-coder]

1. Hardcoded Tailwind colors in RateLimitBanner.tsx — border-amber-500/25, bg-amber-50, text-amber-700 don't respect the theming system. Use border-[var(--warning)]/25 or var(--destructive) variants, or define a --warning CSS var.

2. Missing EOF newlines on githubFetch.ts and RateLimitBanner.tsx.

3. 403 + X-RateLimit-Remaining: 0 not handled — GitHub often returns 403 before ever sending 429 when limits are exhausted. Add detection: if response.status === 403 && response.headers.get('X-RateLimit-Remaining') === '0', treat as rate-limited.

[Priyanshu-byte-coder]

Issues found in this PR:

• Raw Tailwind color classes — replace text-red-* / bg-red-* with text-[var(--destructive)] / appropriate CSS var equivalents. All colors must use CSS variables for theme support.

[Priyanshu-byte-coder]

Merge conflict with current main. Please rebase against main to resolve before this can be merged.

[Priyanshu-byte-coder]

This PR has merge conflicts with main. Please rebase on the latest main branch and re-request review. The approach is approved — just needs conflict resolution.

[Priyanshu-byte-coder]

This PR has merge conflicts with main. Please rebase:

git fetch upstream
git rebase upstream/main

Resolve conflicts and force-push. Will be merged once clean and CI passes.

[Priyanshu-byte-coder]

This PR has significant merge conflicts with current main — it appears to be based on an older version of the codebase. Please rebase onto current main and resolve all conflicts before this can be merged.

[Priyanshu-byte-coder]

This PR has conflicts with the current main branch. Please rebase on main to resolve conflicts so it can be reviewed and merged. Run: git fetch upstream main && git rebase upstream/main

[Priyanshu-byte-coder]

This PR has merge conflicts with main. Please rebase onto the latest main branch and resolve conflicts to proceed with merging.

[Priyanshu-byte-coder]

This PR has merge conflicts with main. Please rebase your branch against the latest main and force-push to resolve. Run: git fetch upstream && git rebase upstream/main

[Priyanshu-byte-coder]

This PR has merge conflicts with the current main branch. Please rebase your branch onto main, resolve the conflicts, and force-push. Once conflicts are resolved and the PR is marked as mergeable it will be reviewed for merging.

[Priyanshu-byte-coder]

This PR has merge conflicts with main. Please rebase:

git fetch origin
git rebase origin/main
# fix conflicts, then:
git push --force-with-lease

[Priyanshu-byte-coder]

This PR has merge conflicts with the current main branch. Please rebase on the latest main to resolve them — your contribution is labeled for GSSoC scoring.