[wizard-ci-bot]

Automated wizard CI run

Source: scheduled
Trigger ID: cc5471b
App: nuxt/movies-nuxt-4
App directory: apps/nuxt/movies-nuxt-4
Workbench branch: wizard-ci-cc5471b-nuxt-movies-nuxt-4
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-10-28T16:54:29.925Z
Duration: 458.3s

YARA Scanner

✓ 246 tool calls scanned, 0 violations detected

No violations: ✓ 246 clean scans

[wizard-ci-bot]

Good — the OpenTelemetry versions are real, and the .logger API is a valid posthog-js feature. Now I have everything I need to write the review.

---

PR Evaluation Report

Summary

This PR integrates PostHog into a Nuxt 4 movies app using the manual posthog-js client plugin approach. It adds client-side event capture across multiple components (login, logout, media selection, search, video playback), error tracking via capture_exceptions and a vue:error hook, structured logging via posthog.logger, and server-side OpenTelemetry log export. However, it is missing user identification (identify/reset) and a reverse proxy.

Files changed	Lines added	Lines removed
14	+204	-8

Confidence score: 5/5 🧙

• Missing posthog.identify() call: The login page captures login_succeeded but never calls .identify() with the user's ID. Events cannot be linked to known users, breaking person-level analytics, session replays, and funnels. [CRITICAL]
• Missing posthog.reset() on logout: handleLogout in NavBar.vue captures an event but never calls .reset(). If users share a browser, the next user inherits the previous one's identity. [CRITICAL]
• No reverse proxy configured: Client-side PostHog requests go directly to us.i.posthog.com, making them susceptible to ad blockers. No Nuxt rewrite rules or proxy configuration is present. [MEDIUM]

---

File changes

Filename	Score	Description
plugins/posthog.client.ts	4/5	Client plugin with init, error tracking, logging config, tracing headers. Well-structured with env var validation.
nuxt.config.ts	4/5	Adds runtime config for PostHog under runtimeConfig.public.posthog.
package.json	4/5	Adds posthog-js and OpenTelemetry logging dependencies.
.env.example	5/5	Documents required env vars.
components/NavBar.vue	2/5	Captures logout event but missing posthog.reset().
pages/login.vue	2/5	Captures login events and logs, but missing posthog.identify().
components/media/Card.vue	5/5	Clean media selection tracking with properties.
components/media/Details.vue	5/5	Tab selection tracking with enriched properties.
components/media/Hero.vue	5/5	Trailer play tracking.
components/video/Card.vue	5/5	Video play tracking with type property.
pages/search.vue	4/5	Search tracking, though missing search query as property.
server/utils/posthog-logs.ts	4/5	OpenTelemetry log exporter for server-side structured logs.
server/api/auth/login.post.ts	4/5	Server-side login logging.
server/api/auth/logout.post.ts	4/5	Server-side logout logging.

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	All dependencies have valid versions; syntax is correct.
Preserves existing env vars & configs	Yes	Existing BASE_URL and configs preserved; PostHog additions are additive.
No syntax or type errors	Yes	TypeScript types are correct; optional chaining used appropriately.
Correct imports/exports	Yes	posthog-js imported client-side only; OpenTelemetry imports server-side only.
Minimal, focused changes	Yes	All changes relate to PostHog integration. The OpenTelemetry logging is extensive but PostHog-related.
Pre-existing issues	None	—

Issues

No app sanity issues.

Other completed criteria

• Environment variables documented in .env.example
• Build configuration valid with real package versions
• Plugin uses .client.ts suffix to ensure browser-only execution
• Proper error handling with dev-mode validation of env vars

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.441.2 added to dependencies
PostHog client initialized	Yes	Initialized in posthog.client.ts plugin with api_host, defaults, error tracking, and tracing headers
capture()	Yes	8 meaningful capture calls across components
identify()	No	No posthog.identify() call after login; no posthog.reset() on logout
Error tracking	Yes	capture_exceptions config + vue:error hook for manual exception capture
Reverse proxy	No	No proxy configured; direct requests to PostHog host

Issues

• No user identification: posthog.identify() is never called after login. The username is available from the auth system but not passed to PostHog. All events remain anonymous, breaking person-level analytics, session replay attribution, and cross-session tracking. Add ?.identify(username) after successful login. [CRITICAL]
• No reset on logout: posthog.reset() is not called in handleLogout(). Users who share a browser will have events attributed to the wrong person. Add ?.reset() in the logout handler. [CRITICAL]
• No reverse proxy: Client-side PostHog requests are sent directly to us.i.posthog.com and are vulnerable to ad blockers. Configure Nuxt server proxy or use PostHog's managed reverse proxy. [MEDIUM]

Other completed criteria

• API key loaded from NUXT_PUBLIC_POSTHOG_PROJECT_TOKEN environment variable
• Host correctly configured from NUXT_PUBLIC_POSTHOG_HOST environment variable
• Error tracking with both automatic exception capture and Vue error boundary
• tracing_headers configured with window.location.hostname for client-server linking
• Structured logging via posthog.logger API on client and OpenTelemetry on server

---

PostHog insights and events ✅

Filename	PostHog events	Description
pages/login.vue	login_succeeded, login_failed	Tracks login outcomes with structured logs
components/NavBar.vue	logged_out	Tracks logout action with structured log
components/media/Card.vue	media_selected	Tracks media selection with media_id and media_type
components/media/Details.vue	media_tab_selected	Tracks tab navigation with media_id, media_type, tab
components/media/Hero.vue	trailer_played	Tracks trailer playback with media_id
components/video/Card.vue	video_played	Tracks video playback with video_type
pages/search.vue	search_performed	Tracks search initiation
plugins/posthog.client.ts	captureException	Captures Vue component exceptions via error hook

Issues

• Search event lacks properties: search_performed has no search_query or results_count property, limiting funnel analysis and search quality insights. [LOW]

Other completed criteria

• Events represent real user actions (login, search, media interaction, video playback)
• Events enable product insights: login → search → select → play funnel is possible
• Events include relevant properties (media_id, media_type, tab, video_type)
• No PII in event properties
• Event names are descriptive and use consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator