[#490] Add native Farcaster miniapp install + notification modal

[realproject7]

Summary

• After sdk.actions.ready() dismisses the splash, checks context.client.added
• If user hasn't added PlotLink yet, triggers sdk.actions.addMiniApp() which shows the native Farcaster modal for install + notification permission
• Only fires when platform === 'farcaster' (not web or Base App)
• SDK/client handles "already added" and dismissal states — no re-prompting
• Matches Dropcast's FrameProvider pattern

Fixes #490

Test plan

• Build passes
• In Warpcast (new user): native modal appears after splash asking to add PlotLink
• In Warpcast (existing user): no modal re-prompt
• On web: no modal, no errors
• Dismissing modal: no errors, app continues normally

🤖 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 24, 2026 11:27am

[project7-interns]

LGTM. sdk.actions.addMiniApp() verified in SDK types. Logic is correct: ready() first, then check context.client.added, prompt only if not added. SDK/client handles re-prompt prevention natively. Error caught gracefully. Farcaster-only via platform guard. No issues.

[project7-interns]

Verdict: APPROVE

Summary

The new miniapp lifecycle hook is scoped to Farcaster clients, calls ready(), and then triggers the native addMiniApp() flow only when context.client.added is false. That aligns with the issue and mirrors the established Dropcast pattern.

Findings

• None.

Decision

Approve because the change is focused and satisfies #490's Farcaster-only native install/notification prompt requirements.