[CI] (7c90ff9) react-router/react-router-v7-project

[wizard-ci-bot]

Automated wizard CI run

Trigger ID: 7c90ff9
App: react-router/react-router-v7-project
App directory: apps/react-router/react-router-v7-project
Workbench branch: wizard-ci-7c90ff9-react-router-react-router-v7-project
Wizard branch: feat-skill-based-integration
Examples branch: rearchitect-generator
PostHog (MCP) branch: feat-mcp-skill-deployment
Timestamp: 2026-01-14T21:15:54.339Z
Duration: 359.9s

[wizard-ci-bot]

The app builds successfully. Now I have all the information I need to write the evaluation report.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router v7 Framework mode application. It adds client-side SDK initialization with PostHogProvider, server-side middleware for session correlation, error boundary exception tracking, user identification on auth events, and comprehensive custom event tracking for country interactions (claim, like, visit, search, filter).

Files changed	Lines added	Lines removed
14	+803	-23

Confidence score: 3/5 🤔

• Invalid PostHog initialization option: defaults: '2025-11-30' is not a valid PostHog configuration option - should be person_profiles: 'always' or similar [CRITICAL]
• usePostHog hook in ErrorBoundary violates React rules: Calling usePostHog() and captureException() directly in the render body (not in useEffect) will cause repeated captures on every re-render [CRITICAL]
• Server middleware creates PostHog client but doesn't use it for any server-side events: The middleware sets up context but no routes actually use it for server-side tracking [MEDIUM]
• No reverse proxy configured: Events will be blocked by ad-blockers without a proxy setup [MEDIUM]

---

File changes

Filename	Score	Description
app/entry.client.tsx	3/5	PostHog initialized with PostHogProvider, but uses invalid defaults option and undocumented __add_tracing_headers internal API
app/lib/posthog-middleware.ts	3/5	New server-side middleware for session correlation - well structured but unused for actual server events
app/root.tsx	2/5	ErrorBoundary calls captureException in render body, violating React hooks rules - will cause duplicate captures
app/routes/countries.tsx	4/5	Good event tracking with debounced search, handlers for claim/like/visit with region properties
app/routes/country.tsx	4/5	Detail view tracking with ref guard to prevent duplicates - well implemented
app/routes/login.tsx	4/5	User identification and login tracking, includes failure tracking
app/routes/profile.tsx	5/5	Clean logout tracking with posthog.reset() for proper session handling
app/routes/signup.tsx	4/5	User identification, signup tracking, and exception capture on errors
app/routes/stats.tsx	4/5	Stats view tracking with user engagement properties
package.json	5/5	Correct PostHog packages added: @posthog/react, posthog-js, posthog-node
vite.config.ts	5/5	Proper SSR noExternal configuration for PostHog packages
react-router.config.ts	5/5	v8_middleware future flag enabled correctly
posthog-setup-report.md	4/5	Comprehensive documentation but references .env file not included in PR

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	Build completes successfully with no errors
Preserves existing env vars & configs	Yes	Original app structure maintained
No syntax or type errors	Yes	TypeScript compilation succeeds
Correct imports/exports	Yes	All imports resolve correctly
Minimal, focused changes	Yes	Changes are focused on PostHog integration

Issues

• ErrorBoundary React hooks violation: The usePostHog() hook and captureException() are called in the render body of ErrorBoundary, not wrapped in useEffect. This violates React rules and will cause the exception to be captured on every re-render. Should wrap in useEffect with error as dependency. [CRITICAL]

Other completed criteria

• Clear, readable code structure
• Consistent patterns across route files
• Proper TypeScript typing with Route types
• Error handling preserved in clientLoader functions

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	@posthog/react ^1.5.2, posthog-js ^1.321.2, posthog-node ^5.21.0
PostHog client initialized	Partial	Initialized in entry.client.tsx with PostHogProvider, but uses invalid defaults option
capture()	Yes	Multiple capture calls across routes for user actions
identify()	Yes	User identification on login and signup with user ID and properties
Error tracking	Partial	captureException in ErrorBoundary and signup, but ErrorBoundary implementation is flawed
Reverse proxy	No	No proxy configuration - events vulnerable to ad-blockers

Issues

• Invalid defaults configuration option: Line 10 in entry.client.tsx uses defaults: '2025-11-30' which is not a valid PostHog option. This may cause initialization warnings or unexpected behavior. Should remove or replace with valid option like person_profiles. [CRITICAL]
• __add_tracing_headers is internal API: Using undocumented internal API __add_tracing_headers is risky and may break with PostHog updates. [MEDIUM]
• No reverse proxy for ad-blocker circumvention: Events sent directly to us.i.posthog.com will be blocked by many ad-blockers. Should configure a /ingest proxy route. [MEDIUM]
• Server middleware unused: posthog-node is initialized in middleware but no server-side events are captured using the context. The server PostHog client is available but dormant. [LOW]

Other completed criteria

• PostHogProvider wraps the app correctly
• API host configured via environment variable
• posthog.reset() called on logout
• Debounced search tracking to avoid excessive events
• Ref guards to prevent duplicate page view tracking in StrictMode
• SSR noExternal configuration for PostHog packages

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
login.tsx	user_logged_in, login_failed	Tracks successful and failed authentication with username and reason
signup.tsx	user_signed_up, signup_failed, captureException	Tracks registration funnel with user properties and error capture
profile.tsx	user_logged_out	Clean session termination tracking
countries.tsx	countries_searched, countries_filtered_by_region, country_claimed, country_liked, country_visited	Core user engagement events with country and region properties
country.tsx	country_detail_viewed	Page view with country metadata (name, region, population)
stats.tsx	stats_viewed	User engagement snapshot with points, counts, and rank
root.tsx	captureException	Error boundary exception tracking

Issues

• No pageview auto-capture verification: While session replay may auto-capture pageviews, explicit `` tracking is not configured. [LOW]
• Missing for user properties: On identify, could use for first_seen properties. [LOW]

Other completed criteria

• Events capture real user actions (claim, like, visit, search, filter)
• Events enriched with relevant properties (country_name, country_region, search_query)
• Failure events track reasons (invalid_credentials, signup_returned_null, exception)
• User identification includes email and username
• Stats tracking includes engagement metrics for cohort analysis
• Debounced search tracking prevents event spam
• Events support funnel analysis (signup → login → claim)

---

Reviewed by wizard workbench PR evaluator