[CI] (362fa9c) react-router/rrv7-starter

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: 362fa9c
App: react-router/rrv7-starter
App directory: apps/react-router/rrv7-starter
Workbench branch: wizard-ci-362fa9c-react-router-rrv7-starter
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-02-11T17:40:00.830Z
Duration: 471.5s

[wizard-ci-bot]

Now I have read all the files needed to evaluate this PR. Let me compile the evaluation report.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router v7 "CloutHub" fake influencer social network app. The integration adds client-side SDK initialization via entry.client.tsx, error tracking in the ErrorBoundary, and event tracking across the purchase funnel and user engagement flows.

Files changed	Lines added	Lines removed
17	+553	-143

Confidence score: 3/5 🤔

• Missing user identification: No posthog.identify() call implemented despite the app having a user concept (fakeUser). Users cannot be tracked across sessions. [MEDIUM]
• No reverse proxy configured: Events sent directly to PostHog will be blocked by ad blockers, reducing data collection reliability. [MEDIUM]
• No automatic pageview tracking: Missing capture_pageview: true in init config or manual `` events. Navigation between routes is not tracked. [MEDIUM]
• API key exposed in setup report: The posthog-setup-report.md file contains the API key in plain text which will be committed to the repo. [LOW]

---

File changes

Filename	Score	Description
app/entry.client.tsx	4/5	New file properly initializes PostHog with PostHogProvider, uses env vars for key/host, and wraps the app correctly. Uses modern defaults config option.
app/root.tsx	3/5	Adds error tracking via captureException() in ErrorBoundary. However, calling hooks inside the component body before conditional rendering could capture 404s as exceptions unnecessarily.
app/components/PostCard.tsx	4/5	Clean implementation of post_liked and post_unliked events with good property enrichment (post_id, author, verified status, like count).
app/components/header.tsx	4/5	Tracks header_buy_followers_clicked with current follower count. Mostly formatting changes.
app/routes/buy-followers.tsx	5/5	Excellent funnel tracking with follower_package_selected and follower_package_purchased events. Rich properties including price, amounts, and calculated price_per_follower.
app/routes/home.tsx	4/5	Tracks CTA clicks for both "View Feed" and "Buy Followers" buttons with source attribution.
app/routes/profile.tsx	4/5	Tracks user_followed events with username and verified status. Properly passes verified prop to FollowButton.
app/components/StatCard.tsx	5/5	Formatting changes only, no functional modifications.
app/routes/analytics.tsx	5/5	Formatting changes only, no functional modifications.
app/routes/feed.tsx	5/5	Formatting changes only, no functional modifications.
app/hooks/use-hydrated.ts	5/5	Formatting changes only (semicolons removed), no functional modifications.
app/lib/data/fake-data.ts	5/5	Minor formatting change (quote style), no functional modifications.
app/lib/utils/localStorage.ts	5/5	Formatting changes only (whitespace), no functional modifications.
package.json	5/5	Correctly adds posthog-js and @posthog/react dependencies.
pnpm-lock.yaml	5/5	Lock file updated correctly with all transitive dependencies.
vite.config.ts	5/5	Properly adds PostHog packages to SSR noExternal for dev mode compatibility.
posthog-setup-report.md	3/5	Good documentation but exposes API key in plain text.

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	Dependencies properly added, SSR config updated for PostHog packages
Preserves existing env vars & configs	Yes	Only adds new PostHog-related configs, existing Vercel env handling preserved
No syntax or type errors	Yes	All TypeScript/JSX syntax is valid
Correct imports/exports	Yes	All imports from @posthog/react and posthog-js are correct
Minimal, focused changes	Partial	Many formatting-only changes (whitespace, line breaks) mixed with functional changes

Issues

• Mixed formatting and functional changes: Many files contain formatting-only changes (removing trailing newlines, adjusting line breaks) alongside PostHog integration. This makes the diff harder to review and could mask unintended changes. [LOW]

Other completed criteria

• Clear, readable code with consistent patterns
• Appropriate null-safe access (posthog?.capture())
• Environment variables used for API key and host
• No hardcoded secrets in source code
• Build configuration properly updated for SSR compatibility

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.345.5 and @posthog/react@^1.7.1 added to dependencies
PostHog client initialized	Yes	Initialized in entry.client.tsx with PostHogProvider wrapping the app
capture()	Yes	8 custom events tracked across components
identify()	No	No user identification implemented despite having a user object (fakeUser)
Error tracking	Yes	captureException() called in ErrorBoundary for route errors
Reverse proxy	No	No reverse proxy configured; events sent directly to us.i.posthog.com

Issues

• No user identification: The app has a fakeUser object and user concept but never calls posthog.identify(). This prevents tracking users across sessions and linking events to user profiles. Should add identify call on app load or user "login". [MEDIUM]
• No reverse proxy: Events are sent directly to PostHog which will be blocked by ad blockers. Should configure a reverse proxy through the app's backend or use a rewrite rule in Vercel/Vite config. [MEDIUM]
• No pageview tracking: The capture_pageview option is not set (defaults to true for initial page only). For SPAs with React Router, manual pageview tracking on route changes is needed but not implemented. [MEDIUM]
• ErrorBoundary captures 404s as exceptions: The captureException(error) is called for all errors including 404s (which are RouteErrorResponse objects, not actual exceptions). This will pollute error tracking with non-error events. [LOW]

Other completed criteria

• API key loaded from environment variable (VITE_PUBLIC_POSTHOG_KEY)
• API host configured via environment variable (VITE_PUBLIC_POSTHOG_HOST)
• Modern SDK configuration with defaults: '2026-01-30'
• Tracing headers configured for localhost development
• Proper SSR handling in Vite config (noExternal for PostHog packages)
• Null-safe capture calls (posthog?.capture())
• No PII in event properties

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
app/routes/buy-followers.tsx	follower_package_selected, follower_package_purchased	Full purchase funnel tracking with rich properties (price, amounts, calculated metrics). Excellent for conversion analysis.
app/components/PostCard.tsx	post_liked, post_unliked	Engagement tracking with post metadata (author, verified status, like count).
app/routes/profile.tsx	user_followed	Social action tracking with target user info.
app/routes/home.tsx	view_feed_cta_clicked, buy_followers_cta_clicked	CTA performance tracking with source attribution.
app/components/header.tsx	header_buy_followers_clicked	Header CTA tracking with current follower count for context.
app/root.tsx	captureException	Error tracking for route errors and exceptions.

Issues

• No pageview tracking: Cannot build navigation funnel insights or understand user flow between pages. [MEDIUM]
• No session properties: Events don't capture session-level context that would enable cohort analysis. [LOW]

Other completed criteria

• Events represent meaningful user actions in the product flow
• Purchase funnel events enable conversion rate analysis
• CTA events with source attribution allow A/B testing different placements
• Engagement events (likes, follows) support engagement metrics
• Event properties are well-structured and enriched with contextual data
• Price-per-follower calculation enables value-based analysis
• Verified status tracking enables influencer tier analysis

---

Reviewed by wizard workbench PR evaluator