[#569] Redesign profile page as social credibility trust dashboard

[realproject7]

Summary

• Trust dashboard grid replaces flat profile header with dedicated cards:
  • Farcaster card: username, FID, follower/following counts, Power badge, Pro subscriber badge
  • X/Twitter card: handle with link, follower/following counts, blue verification badge
  • Quotient Score card: score prominently displayed + rank
  • Wallet card: truncated address linking to block explorer, claimed royalties
• Graceful degradation for all scenarios:
  • Full FC + X: both cards shown
  • FC only: FC card, wallet card (no empty X section)
  • Wallet only: clean minimal profile with just wallet card
  • Each state looks intentional, never broken or empty
• Mobile responsive: single column on mobile, 2-column grid on sm+
• Terminal/monospace aesthetic: font-mono on all numeric stats
• Larger avatar (72px vs 56px) with border
• All data from existing users table — no new API calls
• Refresh button, agent metadata, bio all preserved

Fixes #569

Test plan

• Profile with full FC + X data shows all 4 cards
• Profile with FC only shows FC + wallet cards (no empty X)
• Wallet-only user shows clean minimal profile
• Power badge, Pro badge, X verified badge display correctly
• Mobile layout: single column cards
• Build passes (npm run build)

🤖 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		Mar 26, 2026 4:59pm

[project7-interns]

REQUEST CHANGES — one finding.

Farcaster profile link uses farcaster.xyz but per project conventions the correct domain is farcaster.com (not warpcast.com, not farcaster.xyz). Please update the link at the Farcaster card username href.

Otherwise the PR is clean: graceful degradation across all four data scenarios, responsive grid, terminal aesthetic on stats, no new API calls. Will approve after the URL fix.

[project7-interns]

T2b approves. Farcaster link corrected to farcaster.com. Trust dashboard is clean with graceful degradation across all data scenarios, responsive grid, and terminal aesthetic.

[project7-interns]

Verdict: REQUEST CHANGES

Summary

The trust dashboard redesign is close, but the wallet identity section still misses one of the explicit issue requirements.

Findings

• [medium] The wallet card never exposes a copy affordance for the connected address, so the PR does not satisfy issue #569's truncated + copy wallet identity requirement.
  • File: src/app/profile/[address]/page.tsx:381
  • Suggestion: add a small copy-to-clipboard control next to the truncated address while keeping the explorer link.

Decision

Requesting changes because the wallet identity acceptance criteria are still incomplete.

[project7-interns]

Verdict: REQUEST CHANGES

Summary

The wallet copy affordance is fixed, but the Farcaster dashboard can still render from live lookup data instead of the cached users row, which leaves the trust metrics inconsistent.

Findings

• [medium] ProfilePage still requests getFarcasterProfile(address), and that helper falls back to lookupByAddress(address) when there is no cached FID row. The header then treats any returned fcProfile as sufficient to render the Farcaster card, but follower/following counts and badges still come from dbUser with 0 / null fallbacks. For an address that resolves via the live Farcaster lookup but has no local users row yet, the new trust dashboard will show a Farcaster identity with misleading 0 followers / 0 following and no badges. That violates issue #569's users-table-only data-source requirement and the intentional degradation requirement.
  • File: src/app/profile/[address]/page.tsx:39
  • File: src/app/profile/[address]/page.tsx:208
  • File: lib/actions.ts:29
  • Suggestion: derive Farcaster-card presence and fields strictly from dbUser (fid, username, display_name, pfp_url, etc.), or suppress the card entirely when the cached users row is absent instead of falling back to live lookup data.

Decision

Requesting changes because the social-credibility dashboard can still display misleading trust data for uncached Farcaster addresses.

[project7-interns]

Verdict: APPROVE

Summary

The redesign now satisfies the remaining review findings. The wallet identity includes the required copy affordance, and the Farcaster trust card only renders from cached users-table data.

Findings

• No remaining blocking issues found.

Decision

Approving because the social-credibility dashboard now degrades intentionally and no longer shows misleading Farcaster trust metrics for uncached addresses.