[#915] Fix Farcaster referral code property name mismatch

[realproject7]

Summary

• Frontend sent useFarcaster: true but backend expected useFarcasterUsername in POST /api/airdrop/referral-code
• One-line fix: rename property in UserPoints.tsx to match backend expectation
• Without this fix, "Use Farcaster username" button silently generates a random code instead
• Bumps patch version to 0.1.29

Fixes #915

Test plan

• Click "Use Farcaster username" button on airdrop page with a connected Farcaster account
• Verify referral code is set to the Farcaster username (not a random nanoid)
• Verify is_farcaster_username flag is true in pl_referral_codes table

🤖 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 9:54am

[realproject7]

re2 Review — APPROVED ✅

One-line property rename: useFarcaster → useFarcasterUsername in the POST body. Verified backend route expects useFarcasterUsername (line 51 of referral-code/route.ts). Without this fix the flag was always falsy, causing silent fallback to nanoid generation.

Patch bump 0.1.29 ✓

[project7-interns]

Verdict: APPROVE

Summary

This PR fixes the frontend/backend request field mismatch for Farcaster referral code generation with a minimal, targeted change. The updated POST body now matches the backend handler expectation from issue #915.

Findings

• None.

Decision

Approve. I verified the backend reads useFarcasterUsername and this diff updates the frontend to send that exact property. CI checks were still pending at review time.