feat: Add Weekly Coding Insights card to dashboard #2747

[desireddymohithreddy0925]

Summary

This PR introduces the new "Weekly Coding Insights" card to the DevTrack dashboard, giving users a quick and rich overview of their past 7 days of development activity.

Closes #2747

---

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that changes existing behavior)
• 📝 Documentation update
• ♻️ Refactor / code cleanup (no functional change)
• ⚡ Performance improvement
• 🔒 Security fix
• 🧪 Tests only

---

What Changed

• src/app/api/metrics/weekly-summary/route.ts: Modified the weekly summary API to query and return closed issues count.
• src/components/WeeklyCodingInsightsCard.tsx: Added a new responsive component to display total commits, PRs opened/merged, issues closed, most active repository, and most productive day.
• src/app/dashboard/page.tsx: Integrated the new WeeklyCodingInsightsCard directly into the main Dashboard page under the 'Today Focus Section'.

---

How to Test

1. Start the local server and navigate to the dashboard.
2. Verify that the new "Weekly Coding Insights" card is visible below the "Today Focus" section.
3. Check if the metrics (Commits, PRs, Issues, Streak, Most Active Repo) are populated and accurate based on your past week's GitHub activity.

Expected result: The card should accurately reflect the user's weekly activity, or gracefully display a friendly empty-state illustration if no activity exists.

---

Screenshots / Recordings

Before	After
N/A	N/A

---

Checklist

• Linked the related issue above
• Self-reviewed my own diff
• No unnecessary console.log, debug code, or commented-out blocks
• npm run lint passes locally
• No TypeScript errors (npm run type-check)
• Added or updated tests where applicable
• Updated documentation / comments if behavior changed

---

Accessibility (UI changes only)

• Keyboard navigation works correctly
• Color contrast meets WCAG AA standard
• ARIA labels / roles added where needed
• Tested on mobile / responsive layout

---

Additional Context

N/A

[github-actions]

GSSoC Label Checklist 🏷️

@Umbrella-io — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[Priyanshu-byte-coder]

Thanks for the contribution! We are currently in a code cleanup sprint and not accepting new features. Please see the discussion for details: #2651

This PR will be revisited once the sprint ends. In the meantime, contributions to testing, refactoring, bug fixes, or documentation are welcome.

[Priyanshu-byte-coder]

New UI/feature PRs are on hold during the code quality sprint — see discussion #2651. PRs for tests, refactoring, bug fixes, docs, and performance are welcome.

[Priyanshu-byte-coder]

On hold — new features are not being merged during the code quality sprint. See discussion #2651.

[Priyanshu-byte-coder]

New feature/UI PRs are on hold during the code-quality sprint — see discussion #2651. We'll revisit after the sprint; tests, refactors, and bug-fix PRs are the priority right now.

[Priyanshu-byte-coder]

This overlaps the weekly-summary work — I'm consolidating that on #2717 (the focused analytics dashboard section). This branch also currently conflicts with main. If the "Weekly Coding Insights" card adds something distinct from #2717's stats/insights cards, please rebase and describe what's different; otherwise it's covered by #2717.

[Priyanshu-byte-coder]

Closing as stale. The last commit on this branch was 2026-06-25, over a month ago, and there's been no activity since. It also has merge conflicts against current main.

This isn't a rejection of the idea — DevTrack's PR queue grew past 110 open PRs, so I'm clearing branches that have gone quiet so the review tab reflects what's actually in progress.

If you still want to land this: rebase on current main, address any review feedback above, and reopen this PR (or open a fresh one) — I'll review it. Thanks for contributing to DevTrack.