[wizard-ci-bot]

Automated wizard CI run

Source: scheduled
Trigger ID: cc5471b
App: react-router/react-router-v7-project
App directory: apps/react-router/react-router-v7-project
Workbench branch: wizard-ci-cc5471b-react-router-react-router-v7-project
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-10-28T17:00:48.169Z
Duration: 410.3s

YARA Scanner

✓ 198 tool calls scanned, 0 violations detected

No violations: ✓ 198 clean scans

[wizard-ci-bot]

Now I have enough context to produce the evaluation.

---

PR Evaluation Report

Summary

This PR integrates PostHog into a React Router v7 framework-mode project by adding posthog-js as a dependency, initializing it via a side-effect import in entry.client.tsx, and adding identify/capture/reset calls across auth flows and country interaction pages. A custom logger wrapper and error tracking via capture_exceptions config are also included.

Files changed	Lines added	Lines removed
10	+163	-8

Confidence score: 4/5 👍

• Hallucinated logger API: posthog.logger.info/warn/error is not a documented posthog-js method. The documented method is posthog.captureLog(). The entire posthog-logger.client.ts module and its usage in countries.tsx likely produces runtime errors. [CRITICAL]
• ErrorBoundary not instrumented: The existing ErrorBoundary in root.tsx catches rendering errors but does not call posthog.captureException(error). Since React's error boundary prevents these from reaching window.onerror, the capture_unhandled_errors config won't capture them — leaving a significant gap in error tracking. [MEDIUM]
• No reverse proxy configured: No rewrite rules or proxy configuration added to route PostHog requests through the app's domain, making client-side tracking susceptible to ad blockers. [MEDIUM]

---

File changes

Filename	Score	Description
app/lib/posthog.client.ts	4/5	PostHog initialization with env vars, error tracking config, and defensive dev-mode errors
app/lib/posthog-logger.client.ts	1/5	Uses posthog.logger.info/warn/error which is not a documented API — likely hallucinated
app/entry.client.tsx	4/5	Side-effect import to initialize PostHog on client hydration
app/context/AuthContext.tsx	4/5	Identify on user load, reset on logout — well-structured with ref tracking
app/routes/login.tsx	4/5	Identify + capture on login
app/routes/signup.tsx	4/5	Identify + capture on signup
app/routes/profile.tsx	4/5	Capture logout event before calling logout
app/routes/countries.tsx	3/5	Good capture calls but also modifies button behavior (adds guards) beyond PostHog scope; uses broken logger
.env.example	5/5	Documents required env vars
package.json	5/5	Adds posthog-js dependency

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	PostHog files use .client.ts suffix for correct client-only bundling
Preserves existing env vars & configs	Yes	Existing configs untouched, only additions made
No syntax or type errors	No	posthog.logger.info/warn/error is not a documented API and will likely throw at runtime
Correct imports/exports	Yes	All imports resolve correctly; dynamic imports use proper paths
Minimal, focused changes	No	countries.tsx adds if (!isClaimed) / if (!isLiked) / if (!isVisited) guards that change button behavior beyond PostHog integration
Pre-existing issues	None	Base app appears functional

Issues

• Hallucinated posthog.logger API: The posthog-logger.client.ts module calls posthog.logger.info(), posthog.logger.warn(), and posthog.logger.error(). The documented method is posthog.captureLog({ body, level, attributes }). This will produce runtime errors when the logger is invoked in countries.tsx. Replace with posthog.captureLog() calls. [CRITICAL]
• Button behavior modification: The countries.tsx changes add guards (if (!isClaimed), etc.) that prevent re-clicking claimed/liked/visited countries. This is a functional change unrelated to PostHog integration. [LOW]

Other completed criteria

• Environment variables documented in .env.example
• Build configuration valid — package.json correctly adds posthog-js
• .client.ts suffix correctly prevents server-side bundling without needing ssr.noExternal in vite config

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.441.2 added to package.json
PostHog client initialized	Yes	posthog.init() in posthog.client.ts with api_host, defaults: "2026-08-30", and capture_exceptions config
capture()	Yes	user_logged_in, user_signed_up, user_logged_out, country_claimed, country_liked, country_visited
identify()	Yes	Called on login, signup, and page load (via AuthContext useEffect); uses user.id as distinct_id with email/username as person properties
Error tracking	No	capture_exceptions config is set but the existing ErrorBoundary in root.tsx is not instrumented with captureException(), leaving React rendering errors untracked
Reverse proxy	No	No reverse proxy or rewrite rules configured

Issues

• ErrorBoundary gap: The ErrorBoundary in root.tsx catches React rendering errors before they reach window.onerror. Without adding posthog.captureException(error) inside it, those errors are silently swallowed. Add posthog.captureException(error) to the ErrorBoundary component. [MEDIUM]
• No reverse proxy: No Next.js rewrites, middleware proxy, or other reverse proxy mechanism configured. Client-side events may be blocked by ad blockers. [MEDIUM]
• No PostHogProvider: The documented React Router v7 framework mode pattern wraps the app with PostHogProvider from @posthog/react. This PR uses direct imports instead, which works but prevents use of React hooks like usePostHog, useFeatureFlagEnabled, etc. [LOW]

Other completed criteria

• API key loaded from VITE_PUBLIC_POSTHOG_PROJECT_TOKEN environment variable — not hardcoded
• API host loaded from VITE_PUBLIC_POSTHOG_HOST environment variable
• posthog.reset() correctly called on logout in both AuthContext and profile.tsx
• Identify called on page load for returning users via AuthContext useEffect with ref tracking to avoid redundant calls
• defaults: "2026-08-30" config option set correctly

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
login.tsx	user_logged_in	Captures login with identify call using user.id
signup.tsx	user_signed_up	Captures signup with identify call using user.id
profile.tsx	user_logged_out	Captures logout before reset
countries.tsx	country_claimed, country_liked, country_visited	Captures country interactions with country_name property
countries.tsx	logger calls (broken)	Attempts to log countries_catalog_loaded, countries_catalog_api_rejected, countries_catalog_fetch_failed via hallucinated API
posthog.client.ts	captureException (auto)	Autocaptures unhandled errors and rejections

Issues

• Broken logger events: The three logger calls in countries.tsx (countries_catalog_loaded, countries_catalog_api_rejected, countries_catalog_fetch_failed) use the non-existent posthog.logger API and will fail at runtime. These should use posthog.captureLog() instead. [CRITICAL]

Other completed criteria

• Events represent real user actions (login, signup, logout, country interactions)
• Events enable product insights — can build signup→login→country_claimed funnel
• Country events enriched with country_name property
• No PII in capture() properties — email and username only in identify() person properties
• Event names are descriptive and use consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator