[CI] (4c70a79) nuxt/movies-nuxt-3-6

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 4c70a79
App: nuxt/movies-nuxt-3-6
App directory: apps/nuxt/movies-nuxt-3-6
Workbench branch: wizard-ci-4c70a79-nuxt-movies-nuxt-3-6
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-09-09T22:28:24.518Z
Duration: 428.8s

YARA Scanner

✓ 191 tool calls scanned, 0 violations detected

No violations: ✓ 191 clean scans

[wizard-ci-bot]

---

PR Evaluation Report

Summary

This PR integrates PostHog into a Nuxt 3.0–3.6 movies app using the posthog-js SDK via a client-side plugin. It adds custom event captures across several components (login, logout, media selection, trailer/video playback, search) and sets up error tracking. However, it is missing user identification (identify/reset) and a reverse proxy.

Files changed	Lines added	Lines removed
11	+103	-7

Confidence score: 5/5 🧙

• Missing posthog.identify() on login: The login handler captures user_logged_in but never calls posthog.identify() with the user's distinct ID. The login() composable returns { success, user } where user is the username — this should be used as the distinct ID (or passed as a person property). Without identify, all events remain anonymous and cannot be linked to a known user. [CRITICAL]
• Missing posthog.reset() on logout: The logout handler captures user_logged_out but never calls posthog.reset(). This means a subsequent user on the same browser inherits the previous user's identity. [CRITICAL]
• No reverse proxy configured: This is a client-only app using posthog-js in the browser. Without a reverse proxy, events are susceptible to ad-blocker interception. [MEDIUM]
• Several events lack enriching properties: search_submitted, user_logged_in, and user_logged_out are bare captures with no contextual properties. [MEDIUM]

---

File changes

Filename	Score	Description
plugins/posthog.client.ts	4/5	New PostHog client plugin with proper Nuxt 3.0–3.6 pattern, error tracking via vue:error hook, and env validation
nuxt.config.ts	4/5	Adds PostHog runtime config under runtimeConfig.public.posthog
package.json	5/5	Adds posthog-js dependency
.env.example	5/5	Documents both required env vars
pages/login.vue	2/5	Captures user_logged_in but missing posthog.identify() call
components/NavBar.vue	2/5	Captures user_logged_out but missing posthog.reset() call
components/media/Card.vue	5/5	Good event capture with media_id and media_type properties
components/media/Hero.vue	5/5	Good trailer_started event with media properties
components/video/Card.vue	4/5	Captures video_started with video_type
pages/search.vue	3/5	Captures search_submitted but with no properties
types/nuxt-app.d.ts	5/5	Proper type declaration for `` on NuxtApp

---

App sanity check ✅

Criteria	Result	Description
App builds and runs	Yes	No syntax errors; plugin follows Nuxt 3.0–3.6 conventions
Preserves existing env vars & configs	Yes	Existing apiBaseUrl and all configs preserved; PostHog config added alongside
No syntax or type errors	Yes	Valid TypeScript throughout; type declaration file added for ``
Correct imports/exports	Yes	posthog-js imported correctly; useNuxtApp() and useRuntimeConfig() used properly
Minimal, focused changes	Yes	All changes are PostHog-related; minor formatting changes in login.vue are trivial
Pre-existing issues	None	—

Issues

No app sanity issues.

Other completed criteria

• Environment variables documented in .env.example with NUXT_PUBLIC_POSTHOG_PROJECT_TOKEN and NUXT_PUBLIC_POSTHOG_HOST
• Build configuration valid — posthog-js added to dependencies in package.json
• Plugin gracefully returns early with dev-only errors if env vars are missing

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js ^1.429.0 added to dependencies
PostHog client initialized	Yes	Proper Nuxt 3.0–3.6 plugin pattern in posthog.client.ts with posthog.init(), env-based key/host, defaults, and debug mode in dev
capture()	Yes	6 meaningful capture calls across login, logout, media selection, trailer, video, and search
identify()	No	No posthog.identify() on login and no posthog.reset() on logout
Error tracking	Yes	capture_exceptions configured with unhandled errors/rejections; vue:error hook calls captureException()
Reverse proxy	No	No reverse proxy configured; api_host points directly to us.i.posthog.com

Issues

• No user identification on login: login.vue captures user_logged_in but never calls posthog.identify(). The login() composable returns { success, user } where user is the username string. After a successful login, the code should call posthog?.identify(response.user, { name: response.user }) to link events to the authenticated user. [CRITICAL]
• No posthog.reset() on logout: NavBar.vue captures user_logged_out but never calls posthog?.reset() after the logout event. This means the next user session on the same browser will still be associated with the previous user. [CRITICAL]
• No reverse proxy: The api_host points directly to https://us.i.posthog.com. For a browser-based app, a reverse proxy should be configured to avoid ad-blocker interception. [MEDIUM]

Other completed criteria

• API key loaded from environment variable via runtimeConfig.public.posthog.publicKey
• Host correctly configured via runtimeConfig.public.posthog.host
• tracing_headers set to [window.location.hostname] for potential backend correlation
• defaults set to '2026-01-30'
• Dev-only error thrown if env vars are missing — good DX guard

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
pages/login.vue	user_logged_in	Captured on successful login, but no properties and no identify call
components/NavBar.vue	user_logged_out	Captured before logout, but no reset call
components/media/Card.vue	media_selected	Captures media_id and media_type when a media card is clicked
components/media/Hero.vue	trailer_started	Captures media_id and media_type when a trailer plays
components/video/Card.vue	video_started	Captures video_type when a video plays
pages/search.vue	search_submitted	Captured when a search is executed, but no properties
plugins/posthog.client.ts	captureException	Vue error boundary captures exceptions via vue:error hook

Issues

• Several events lack properties: search_submitted has no properties (could include result count or search category). user_logged_in and user_logged_out have no properties. Events with bare captures limit the ability to build useful funnels or breakdowns. [MEDIUM]

Other completed criteria

• Events represent real user actions (login, logout, media selection, trailer/video playback, search)
• Events enable product insights — can build login→search→media_selected→trailer_started funnel
• No PII in event properties — only media IDs and types
• Consistent snake_case naming convention across all events

---

Reviewed by wizard workbench PR evaluator