Add secure POST /api/leaderboard/rebuild endpoint for scheduled builds

[Vikrant0207]

Summary

Enhanced the existing PULL_REQUEST_TEMPLATE.md to improve contribution quality, accessibility awareness, and reviewer guidance.

Closes #1798

---

Type of Change

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

---

Changes Made

• Improved PR template structure and readability
• Added accessibility checklist section
• Added additional notes section
• Enhanced contributor guidance for testing and review
• Improved consistency for future pull requests

---

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

---

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

I am a GSSOC 2026 Contributor . kindly add necessary labels and merge it

[vercel]

@Vikrant0207 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!

[Vikrant0207]

@Priyanshu-byte-coder kindly review and merge it

[Vikrant0207]

@Priyanshu-byte-coder branch updated

[Vikrant0207]

@Priyanshu-byte-coder pls review and merge

[Priyanshu-byte-coder]

This PR has merge conflicts with main (which has since received many merges). Please rebase:

git fetch origin
git rebase origin/main
git push --force-with-lease

[Priyanshu-byte-coder]

This PR has merge conflicts with main — please rebase:

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

[Vikrant0207]

@Priyanshu-byte-coder i have resolved the conflict kindly merge it if its okay

[Vikrant0207]

@Priyanshu-byte-coder kindly review this product pls

[github-actions]

🎉 Merged! Thanks for contributing to DevTrack.

If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers.

Keep an eye on open issues for your next contribution!