Find the integration points

The app is intentionally complete in mock mode. Before creating provider accounts, ask your AI to inventory the real boundaries.

Read agent-skills/integration-points.md. Run pnpm seams and pnpm setup:check,
inspect src/config/integrations.ts, and give me a table of every capability,
current adapter, included production adapter, account needed, server work, native
rebuild requirement, verification command, and matching skill. Do not change code.

Recommended activation order

1. Supabase auth, data, and deletion: establishes stable identity and RLS.
2. Private uploads: attaches files to the authenticated user.
3. RevenueCat: identifies the purchaser with the Supabase UUID.
4. AI chat, scan, and voice: uses authenticated server functions and private uploads.
5. Push: owns tokens by stable user and sends from trusted server code.
6. PostHog and Sentry: follows explicit privacy, retention, and opt-out decisions.

The contract rule

If your product needs a new field or action, extend the provider-neutral interface first, then the mock and production implementations, then callers and tests. Do not import vendor SDK types into a route.

Useful checks

pnpm seams
pnpm setup:check
pnpm verify:supabase
pnpm verify:revenuecat
pnpm verify:ai
pnpm verify:analytics
pnpm verify:sentry
pnpm verify:push
pnpm verify:deletion

The final pnpm verify:production is supposed to fail while placeholders, mock adapters, unsigned links, or missing evidence remain. That failure protects you from mistaking a pretty demo for a configured production app.