[CI] (e2f7ab0) react-router/react-router-v7-project

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: e2f7ab0
App: react-router/react-router-v7-project
App directory: apps/react-router/react-router-v7-project
Workbench branch: wizard-ci-e2f7ab0-react-router-react-router-v7-project
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-07-06T22:09:05.651Z
Duration: 193.6s

YARA Scanner

✓ 84 tool calls scanned, 0 violations detected

No violations: ✓ 84 clean scans

[wizard-ci-bot]

---

PR Evaluation Report

Summary

This PR integrates PostHog into a React Router v7 framework-mode project. It adds client-side initialization in entry.client.tsx with PostHogProvider, implements user identification on login/signup/page load, captures meaningful product events (country claim/like/visit, login, signup, logout), adds error tracking via the root error boundary, and configures Vite SSR compatibility.

Files changed	Lines added	Lines removed
9	+147	-5

Confidence score: 4/5 👍

• __add_tracing_headers is not a valid config option: The entry.client.tsx uses __add_tracing_headers instead of the documented tracing_headers option. The double-underscore prefix suggests an internal/private API that may not be stable or may not work at all. [MEDIUM]
• posthog-node installed but never used: The posthog-node package is added to package.json but no server-side PostHog code exists in the PR. This is unnecessary bloat. [LOW]

---

File changes

Filename	Score	Description
app/entry.client.tsx	4/5	PostHog initialized with PostHogProvider, env vars, and defaults. Uses __add_tracing_headers instead of tracing_headers.
app/context/AuthContext.tsx	4/5	Adds identify on page load for returning users and reset() on logout. Identify call in useEffect is appropriate here for syncing with external system.
app/root.tsx	4/5	Error boundary captures exceptions via captureException.
app/routes/login.tsx	5/5	Identifies user and captures user_logged_in in event handler after successful login.
app/routes/signup.tsx	5/5	Identifies user and captures user_signed_up in event handler after signup.
app/routes/countries.tsx	5/5	Captures country_claimed, country_liked, country_visited in click handlers with rich properties.
package.json	4/5	Adds posthog-js, @posthog/react, and unnecessary posthog-node.
vite.config.ts	5/5	Correctly adds noExternal for SSR compatibility per docs.
posthog-setup-report.md	5/5	Setup report with event table and next steps.

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	All syntax is valid, imports resolve, SSR config correct
Preserves existing env vars & configs	Yes	Existing config untouched, PostHog additions are additive
No syntax or type errors	Yes	All code is syntactically valid TypeScript/TSX
Correct imports/exports	Yes	usePostHog from @posthog/react, posthog from posthog-js — all correct
Minimal, focused changes	Yes	All changes relate to PostHog integration
Pre-existing issues	None	—

Issues

• Unused posthog-node dependency: posthog-node is added to package.json but no server-side PostHog code exists. Should be removed to avoid unnecessary dependency. [LOW]

Other completed criteria

• Environment variables use VITE_ prefix for client-side access, consistent with Vite conventions
• Build configuration includes proper ssr.noExternal for framework mode as documented

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js and @posthog/react added to package.json
PostHog client initialized	Yes	posthog.init() in entry.client.tsx with PostHogProvider wrapping the app — matches framework mode docs
capture()	Yes	6 meaningful capture calls across login, signup, logout, and country actions
identify()	Yes	Called on login, signup, and for returning users on page load. Uses currentUser.id as distinct_id. reset() called on logout.
Error tracking	Yes	captureException(error) in root ErrorBoundary — matches React Router framework mode docs
Reverse proxy	No	No reverse proxy configured (no rewrites in Vite config or middleware)

Issues

• __add_tracing_headers instead of tracing_headers: The init config uses __add_tracing_headers which is a private/internal option (double underscore prefix). The documented option is tracing_headers. This likely won't enable tracing headers as intended. [MEDIUM]
• No reverse proxy configured: No reverse proxy or rewrite rules set up. Events may be blocked by ad blockers. [MEDIUM]

Other completed criteria

• API key loaded from import.meta.env.VITE_POSTHOG_PROJECT_TOKEN environment variable
• API host loaded from import.meta.env.VITE_POSTHOG_HOST environment variable
• defaults: "2026-05-30" correctly set
• posthog.reset() called on logout to unlink future events
• Identify uses currentUser.id (real user ID from auth context), not fabricated values

---

PostHog insights and events ✅

Filename	PostHog events	Description
app/routes/login.tsx	user_logged_in	Captures login with country counts and points as properties
app/routes/signup.tsx	user_signed_up	Captures signup with initial user stats
app/routes/countries.tsx	country_claimed, country_liked, country_visited	Captures core product actions with country name, region, points, and counts
app/context/AuthContext.tsx	user_logged_out	Captures logout with final user stats
app/root.tsx	captureException	Captures unhandled errors from the error boundary

Issues

No issues.

Other completed criteria

• Events represent real user actions (login, signup, logout, country interactions)
• Events enable product insights — can build signup→claim funnel, engagement trends, retention analysis
• Events include rich contextual properties (country name, region, points, counts)
• No PII in event properties — email/username only in identify() person properties
• Event names are descriptive, consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator