feat(friend-comparison): add dedicated comparison page and enhanced the component

[narang24]

Summary

Enhanced the Friend Comparison functionality by introducing a dedicated comparison page (endpoint - /friend-compare) and improved UI/UX.

Closes #871

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor / code cleanup

Changes Made

• Since, Friend Comparison functionality deserves a broader and extended display, I have given it a dedicated route /friend-compare
• The FriendComparison component, as a whole, was hidden, unhighlighted and crowded among the other existing dashboard components, So, A button indicating the functionality is added alongside the quick button links like "Year in Code".
• I enhanced the metrics comparison display portion, github username + avatar for better UI.
• I replaced the 'View Commit activity' button with the 'contribution-activity' component(chart) rendering on clicking on compare. Also, added a Clear button in red color for a cleaner and improved overall functionality of the component.

---

How to Test

Steps for the reviewer to verify this works:

1. Create a new pull request
2. Verify the updated PR template appears automatically
3. Check that all checklist sections render properly
4. Ensure markdown formatting works correctly

---

Screenshots (if UI change)

Added a dedicated button and endpoint

Improved UI/UX

Replaced View Commit Activity with the contribution-activity component and added red Clear button

---

Checklist

• Linked issue in summary
• npm run lint passes locally
• No TypeScript errors (npm run type-check)
• Self-reviewed the diff
• Added/updated tests if applicable

---

Accessibility Checklist

• Proper keyboard navigation tested
• Responsive UI verified
• Accessibility labels added where needed

---

Additional Notes

This update standardizes pull request submissions and helps maintain consistent review quality across contributions.

[vercel]

@narang24 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.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — 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

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

[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

[narang24]

@Priyanshu-byte-coder please review

[Karanjot786]

Hey @narang24! Saw your work on GSSoC 2026.

We are building TermUI, a TypeScript terminal UI framework with React-style hooks and JSX, rendered entirely in the terminal.

We have 67 unassigned GSSoC issues open. 19 are marked good first issue. Your TypeScript background transfers directly.

• Open issues (GSSoC 2026)
• TermUI on GSSoC

Karanjot, TermUI maintainer

[Priyanshu-byte-coder]

This PR has developed merge conflicts after recent merges to main. Please rebase onto the latest main branch, resolve all conflicts, and force-push. Once the PR is conflict-free 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. Please rebase on the latest main to resolve them — the feature/fix is approved for GSSoC scoring.

[Priyanshu-byte-coder]

This PR has merge conflicts with main. Please rebase to unblock it:

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

[Priyanshu-byte-coder]

This PR has merge conflicts with main due to recent changes. Please rebase to continue:

git fetch origin
git rebase origin/main

Once you resolve the conflicts and CI passes, we can review for merge.

[Priyanshu-byte-coder]

Hi! This PR has merge conflicts with the main branch. Could you please rebase or merge main into your branch to resolve them? We'd love to get this merged! 🚀

git fetch upstream
git rebase upstream/main
# resolve any conflicts
git push --force-with-lease

If you're no longer working on this, let us know and we can close it. Thanks!

[Priyanshu-byte-coder]

This PR has merge conflicts with the main branch. Please rebase your branch on latest main and resolve the conflicts so it can be reviewed and merged.