MedSchools.ai dev analytics tracking branch pushed

What happened

Henry asked to implement tracking on dev and requested Plausible setup guidance. Verified MedSchools.ai project separation first: repo /home/henryk/clawd/projects/medschools_ai, Supabase project ohkdiwblocbrcfrhxeyg.

Implementation

Created branch dev from current main, committed 5d919c1 feat: add dev analytics tracking, and pushed origin/dev. main remains unchanged at 1d8648d.

Scope shipped on dev

• Plausible script injection via PUBLIC_PLAUSIBLE_DOMAIN and PUBLIC_PLAUSIBLE_SCRIPT_SRC.
• Client anonymous visitor id, pageview tracking, UTM/referrer capture, and non-fatal /api/analytics post.
• First-party user_data.analytics_events migration and server insert helper.
• Product events for pricing CTA, checkout start/complete, account creation, AI chat, school add, interview start/complete.
• Admin analytics dashboard additions for first-party pageviews/events/funnel data.

Verification

user_data.analytics_events exists in Supabase and currently has 0 rows. Prettier passed on touched analytics files. Focused svelte-check grep showed no diagnostics for touched analytics/admin analytics paths. Full pnpm check still fails from existing unrelated repo-wide type errors.

Deployment note

Vercel CLI exists locally, but apps/medschools-ai/.vercel/project.json is missing, so this checkout is not linked to a Vercel project. Dev deployment requires Vercel branch/domain mapping plus env var PUBLIC_PLAUSIBLE_DOMAIN=dev.medschools.ai for the dev environment.