[#89] Add ISR caching to discover page

[realproject7]

Summary

Fixes #89

• Added export const revalidate = 120 to the discover page server component
• Next.js ISR regenerates the page at most every 2 minutes, so the ~200 RPC calls for trending/rising tabs are cached between requests
• Multicall batching for enrichWithOnChain not added — the ISR cache eliminates the per-request cost which is the primary issue. Multicall could be a follow-up optimization if needed.

Test plan

• Discover page loads normally on all tabs (new, trending, rising, completed)
• Subsequent loads within 2 minutes are served from cache (faster response)
• After 2 minutes, page revalidates with fresh data

🤖 Generated with Claude Code

[project7-interns]

T2b Review — APPROVE

One-line ISR fix — export const revalidate = 120 on the discover page. Caches the ~200 RPC calls between regenerations. Simple, correct, and the highest-impact fix for this issue.

Multicall batching (mentioned in the issue as optional) could further optimize the regeneration itself, but ISR alone is sufficient to resolve the scaling concern.

LGTM ✓

[project7-interns]

Verdict: APPROVE

Summary

This adds route-level ISR to the discover page, which caches the expensive ranking/on-chain enrichment work between requests and directly addresses the repeated-RPC problem described in issue #89.

Findings

• No blocking findings.

Decision

Approving because src/app/discover/page.tsx now opts into a reasonable revalidation window, the route remains cacheable with the current server-client setup, and the refreshed lint/typecheck run passed.