[#888] Add leaderboard component

[realproject7]

Fixes #888

Summary

• Leaderboard component: table showing top 50 users by PL points with rank, address/Farcaster username, total PL, and share %
• Current user's row highlighted with accent background and "(you)" label
• If user is outside top 50, their rank shown below the table ("Your rank: #N")
• Empty state when no participants yet
• Added to /airdrop page between UserPoints and MilestoneTrack
• 60s stale/refetch, shares query key pattern with other airdrop components

Test plan

• Verify top 50 entries display with rank, user, PL, share %
• Verify Farcaster usernames shown where available, truncated addresses otherwise
• Verify connected user's row is highlighted
• Verify "Your rank: #N" shown when user is outside top 50
• Verify empty state when no data
• Verify responsive table layout on mobile

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
plotlink	Ignored		Apr 21, 2026 5:52am

[project7-interns]

Verdict: REQUEST CHANGES

Summary

The leaderboard UI is close, but the current-user matching logic depends on exact address-string equality and can fail if the API returns checksummed addresses.

Findings

• [medium] The component lowercases the connected wallet address but compares it directly against entry.address without normalizing the entry values. If /api/airdrop/leaderboard returns checksum-cased addresses, the current user's row will not highlight and Your rank may render incorrectly even when that user is already in the top 50.
  • File: src/components/airdrop/Leaderboard.tsx:49
  • Suggestion: Normalize both sides before comparison, for example compare entry.address.toLowerCase() against the lowercased connected address in both inTop50 and isUser.

Decision

Requesting changes because the current-user highlighting and own-rank behavior can be incorrect depending on the API's address casing.

[project7-interns]

Verdict: APPROVE

Summary

The follow-up update resolves the address-normalization issue from my prior review. Current-user highlighting and own-rank logic now compare addresses case-insensitively, which matches the leaderboard requirement.

Findings

• No remaining code-level blockers in the changed files.

Decision

Approving because the leaderboard behavior I reviewed now matches issue #888.