[wizard-ci-bot]

Automated wizard CI run

Source: scheduled
Trigger ID: cc5471b
App: react-router/rrv7-starter
App directory: apps/react-router/rrv7-starter
Workbench branch: wizard-ci-cc5471b-react-router-rrv7-starter
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-10-28T16:59:02.282Z
Duration: 385.5s

YARA Scanner

✓ 182 tool calls scanned, 0 violations detected

No violations: ✓ 182 clean scans

[wizard-ci-bot]

Now I have enough context to evaluate the PR. Let me analyze:

---

PR Evaluation Report

Summary

This PR adds PostHog integration to a React Router v7 (framework mode) starter app called "CloutHub." It creates a PostHog client module with lazy initialization, adds custom event captures for post likes, follower package selection, follower purchases, and profile follows. However, it lacks a PostHogProvider, user identification, error boundary integration, and a reverse proxy — several foundational pieces of a proper React/React Router PostHog integration.

Files changed	Lines added	Lines removed
9	+112	-3

Confidence score: 4/5 👍

• No PostHogProvider: The integration initializes PostHog via a lazy-imported module in useEffect in root.tsx instead of using PostHogProvider from @posthog/react as documented for React Router v7 framework mode. The @posthog/react package is not even installed. [CRITICAL]
• No user identification: No posthog.identify() or posthog.reset() calls exist anywhere in the app, meaning all events are anonymous and cannot be linked to specific users. [CRITICAL]
• No error boundary integration: The existing ErrorBoundary in root.tsx does not call posthog.captureException(error), missing structured error tracking despite capture_exceptions being configured for unhandled errors. [MEDIUM]
• No reverse proxy configured: No reverse proxy is set up, making client-side events susceptible to ad blockers. [MEDIUM]
• posthog.logger is not a valid SDK method: The code calls posthog.logger.info() which does not exist on the posthog-js SDK. The correct method is posthog.captureLog(). This will throw a runtime error. [CRITICAL]

---

File changes

Filename	Score	Description
app/lib/posthog.client.ts	3/5	PostHog initialization with env var validation, error tracking config, but uses outdated defaults date and lacks PostHogProvider pattern
app/lib/posthog-logs.client.ts	1/5	Logger wrapper that calls non-existent posthog.logger.info() method — will error at runtime
app/root.tsx	2/5	Lazy-loads PostHog in useEffect instead of proper PostHogProvider setup; no error boundary integration
app/routes/buy-followers.tsx	4/5	Good event captures with enriched properties for package selection and purchase
app/routes/profile.tsx	3/5	Captures profile follow event; minor cleanup of unused username prop
app/components/PostCard.tsx	3/5	Captures post liked event, but only on like (not unlike)
.env.example	5/5	Properly documents new env vars
env.d.ts	5/5	Correct TypeScript declarations for new env vars
package.json	3/5	Adds posthog-js but missing @posthog/react

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	No	posthog.logger.info() is not a valid SDK method — will throw at runtime when any logging path is hit
Preserves existing env vars & configs	Yes	Existing VITE_SITE_URL preserved, new vars added alongside
No syntax or type errors	No	posthog.logger does not exist on the posthog-js type definitions
Correct imports/exports	Yes	Imports from posthog-js are correct; internal module imports are valid
Minimal, focused changes	Yes	All changes relate to PostHog integration
Pre-existing issues	None	Base app appears functional

Issues

• posthog.logger does not exist: The posthog-logs.client.ts file calls posthog.logger.info(message, attributes), but the posthog-js SDK has no .logger property. The correct method is posthog.captureLog({ body: message, level: 'info', attributes }). This will throw a runtime error whenever a user likes a post, follows a profile, or purchases followers. [CRITICAL]
• Outdated defaults date: defaults: '2026-01-30' is used instead of the latest '2026-08-30', missing newer default configuration improvements. [LOW]

Other completed criteria

• Environment variables properly documented in .env.example and env.d.ts
• Build configuration (package.json) is valid with correct posthog-js dependency

---

PostHog implementation ❌

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js added to package.json, but @posthog/react is missing
PostHog client initialized	No	Initialized via lazy module import in useEffect instead of using PostHogProvider from @posthog/react as documented for React Router v7 framework mode
capture()	Yes	Multiple meaningful posthog.capture() calls for user actions
identify()	No	No posthog.identify() or posthog.reset() calls anywhere — all events are anonymous
Error tracking	No	capture_exceptions is configured for unhandled errors, but the existing ErrorBoundary component does not call posthog.captureException(error) for caught route errors
Reverse proxy	No	No reverse proxy configured (no rewrites, middleware, or proxy setup)

Issues

• No PostHogProvider: The documented pattern for React Router v7 framework mode is to initialize PostHog in entry.client.tsx and wrap the app with PostHogProvider from @posthog/react. Instead, PostHog is lazily imported in a useEffect in root.tsx, which means PostHog may not be initialized when capture calls fire in child components. The @posthog/react package is not installed at all. [CRITICAL]
• No user identification: Without posthog.identify(), all captured events are anonymous. The app has a profile page with user data, suggesting identification should be possible. No posthog.reset() on logout either. [CRITICAL]
• ErrorBoundary not instrumented: The existing ErrorBoundary export in root.tsx catches route errors but does not forward them to PostHog via posthog.captureException(error). [MEDIUM]
• No reverse proxy: Client-side events will be blocked by ad blockers without a reverse proxy. React Router supports rewrites or middleware-based proxies. [MEDIUM]

Other completed criteria

• API key loaded from VITE_POSTHOG_PROJECT_TOKEN environment variable
• API host loaded from VITE_POSTHOG_HOST environment variable
• PostHog SDK correctly added to package.json dependencies

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
app/components/PostCard.tsx	post_liked	Tracks when a user likes a post (not unlikes). Also attempts logging via broken posthog.logger
app/routes/buy-followers.tsx	follower_package_selected, follower_purchase_completed	Tracks package selection with amount/bonus/price properties, and purchase completion with full details
app/routes/profile.tsx	profile_followed	Tracks when a user follows a profile. Also attempts logging via broken posthog.logger

Issues

• Logging calls will fail at runtime: All paths that use posthogLogger.info() call the non-existent posthog.logger.info() and will throw errors when triggered. [CRITICAL]
• Only captures "like" not "unlike": The PostCard component only captures when a post is liked (newLikedState === true), missing the unlike action which could be valuable for engagement analytics. [LOW]

Other completed criteria

• Events represent real user actions (liking, purchasing, following)
• Events enable product insights (can build funnels: package_selected → purchase_completed)
• Events include relevant properties (follower amounts, prices, bonuses)
• No PII in event properties
• Event names are descriptive and use snake_case consistently

---

Reviewed by wizard workbench PR evaluator