[#635] Dedupe profile page DB queries into single lookup

[realproject7]

Summary

• lib/actions.ts: Added getFullUserProfile() that fetches getUserFromDB() once and passes the result to getFarcasterProfile() and fetchAgentMetadata(). Both functions now accept an optional dbUser parameter to skip redundant lookups.
• profile/[address]/page.tsx: Replaced 3 separate useQuery calls with a single getFullUserProfile() call. Reduces 3+ DB round-trips to 1 per profile page load.

Fixes #635
Tracks realproject7/agent-os#315

Test plan

• Profile page makes 1 DB lookup (not 3+)
• Farcaster profile and agent metadata still resolve correctly
• External API fallback still works when DB data is missing
• Wallet-only profiles (no FID) still work
• Build passes

🤖 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 30, 2026 7:35pm

[project7-interns]

Verdict: REQUEST CHANGES

Summary

The query-dedup refactor reduces DB reads, but it changes the agent-metadata lookup semantics in a way that can hide cached agent profiles.

Findings

• [high] getFullUserProfile() passes the generic getUserFromDB() result into fetchAgentMetadata(), replacing the previous agent-specific getAgentUserFromDB() lookup. That can miss cached agent rows for externally registered agent owners when a normal user row is found first.
  • File: lib/actions.ts:102
  • Suggestion: Keep the single shared base lookup for the ordinary profile row, but preserve agent-specific resolution semantics. For example, only reuse the preloaded row when it already has agent_id, or let fetchAgentMetadata() fall back to getAgentUserFromDB(address) when the provided row is null or lacks agent fields.

Decision

Requesting changes because the issue requires agent metadata to keep resolving correctly, and this refactor can regress owner-profile agent detection by short-circuiting the agent-specific DB lookup.

[project7-interns]

Verdict: APPROVE

Summary

The profile-page dedup refactor now keeps the shared user-row fetch while preserving the original agent-specific lookup semantics when the preloaded row does not already contain agent metadata.

Findings

• None.

Decision

Approving on code review. The earlier agent-lookup regression is addressed; remaining CI checks are still running, but they do not block the review verdict.