[CI] (6b2dc8b) nuxt/movies-nuxt-4

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 6b2dc8b
App: nuxt/movies-nuxt-4
App directory: apps/nuxt/movies-nuxt-4
Workbench branch: wizard-ci-6b2dc8b-nuxt-movies-nuxt-4
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-09-01T15:53:36.797Z
Duration: 476.3s

YARA Scanner

✓ 195 tool calls scanned, 0 violations detected

No violations: ✓ 195 clean scans

[wizard-ci-bot]

Now I have all the information needed to produce the evaluation.

---

PR Evaluation Report

Summary

This PR integrates PostHog into a Nuxt 4 movies app using a manual posthog-js client plugin. It adds event captures across several components (login, logout, search, media selection, trailer play, video play, tab selection) and sets up error tracking via a vue:error hook. However, it's missing identify() and reset() calls, and no reverse proxy is configured.

Files changed	Lines added	Lines removed
12	+111	-12

Confidence score: 5/5 🧙

• Missing identify() call: The app has login functionality (login.vue, useAuth composable) but never calls posthog.identify() after successful login, so all events remain anonymous and cannot be linked to known users. [CRITICAL]
• Missing reset() call on logout: The NavBar.vue captures a logout_completed event but never calls posthog.reset(), meaning the next user on the same browser inherits the previous session's identity. [CRITICAL]
• No reverse proxy configured: This is a client-side browser app using posthog-js, which benefits from a reverse proxy to avoid ad blockers. No proxy rewrites are set up. [MEDIUM]

---

File changes

Filename	Score	Description
plugins/posthog.client.ts	4/5	New client plugin initializing PostHog with runtime config, error tracking via vue:error, and helpful dev-mode validation
nuxt.config.ts	3/5	Adds PostHog runtime config under runtimeConfig.public.posthog; uses manual plugin approach instead of @posthog/nuxt module
package.json	4/5	Adds posthog-js dependency
.env.example	5/5	Documents required PostHog env vars
pages/login.vue	2/5	Captures login_succeeded but missing posthog.identify() call
components/NavBar.vue	2/5	Captures logout_completed but missing posthog.reset() call
components/media/Card.vue	5/5	Captures media_selected with relevant properties
components/media/Details.vue	5/5	Captures media_tab_selected with tab property
components/media/Hero.vue	5/5	Captures trailer_played with media properties
components/video/Card.vue	5/5	Captures video_played with video type; also adds null check
pages/search.vue	4/5	Captures search_submitted but no search term property
types/nuxt-app.d.ts	5/5	Type declaration for `` on NuxtApp

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	Valid Nuxt plugin pattern, correct imports, no syntax errors
Preserves existing env vars & configs	Yes	Existing BASE_URL env var preserved; existing modules and config untouched
No syntax or type errors	Yes	TypeScript types are correct; type declaration file properly augments NuxtApp
Correct imports/exports	Yes	posthog-js imported correctly in client plugin; useNuxtApp() used properly
Minimal, focused changes	Yes	All changes relate to PostHog integration; minor code quality improvements (null checks, formatting) are appropriate
Pre-existing issues	None	—

Issues

• Minor formatting changes in login.vue: The PR reformats catch/finally blocks and removes trailing whitespace, but these are trivial and don't affect functionality. [LOW]

Other completed criteria

• Environment variables documented in .env.example
• Build configuration valid — posthog-js added to dependencies in package.json
• Runtime config properly structured under runtimeConfig.public.posthog

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js added to package.json dependencies
PostHog client initialized	Yes	Initialized via posthog.init() in plugins/posthog.client.ts with api_host, defaults, and tracing_headers
capture()	Yes	Multiple meaningful capture() calls across 7 components
identify()	No	No posthog.identify() call after login — events remain anonymous
Error tracking	Yes	vue:error hook calls posthogClient.captureException(error)
Reverse proxy	No	No reverse proxy configured; api_host points directly to PostHog host

Issues

• Missing posthog.identify() on login: After login() succeeds in login.vue, there is no posthog.identify() call. The useAuth composable exposes a user string (username). At minimum, ?.identify(username) should be called after successful login, and also on app load when a user is already authenticated (e.g., in the plugin's loaded callback by reading the auth cookie). [CRITICAL]
• Missing posthog.reset() on logout: NavBar.vue handles logout but only captures a logout_completed event without calling ?.reset(). This means the anonymous ID persists across user sessions, potentially merging different users. [CRITICAL]
• No reverse proxy: The app uses posthog-js in the browser, which benefits from a reverse proxy to circumvent ad blockers. No Nuxt server routes or rewrites are configured. [MEDIUM]

Other completed criteria

• API key loaded from environment variable (NUXT_PUBLIC_POSTHOG_PROJECT_TOKEN)
• API host loaded from environment variable (NUXT_PUBLIC_POSTHOG_HOST)
• defaults configuration set (using '2026-01-30')
• tracing_headers configured with window.location.hostname
• Dev-mode debug logging enabled
• Helpful dev-mode error thrown when env vars are missing

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
pages/login.vue	login_succeeded	Captured on successful login; no properties attached
components/NavBar.vue	logout_completed	Captured before logout redirect; no properties
pages/search.vue	search_submitted	Captured when search is executed; no search term or result count properties
components/media/Card.vue	media_selected	Captured with media_id and media_type properties
components/media/Details.vue	media_tab_selected	Captured with tab property (overview/videos/photos)
components/media/Hero.vue	trailer_played	Captured with media_id and media_type properties
components/video/Card.vue	video_played	Captured with video_type property
plugins/posthog.client.ts	captureException	Error tracking via vue:error hook

Issues

• search_submitted lacks properties: The search event doesn't include the search query term or any context about what was searched. Adding { search_term: input.value } would enable search analysis funnels. [MEDIUM]
• login_succeeded lacks properties: No properties attached to the login event. Even without full identify, including the username would be useful (though it should go via identify, not capture properties). [LOW]

Other completed criteria

• Events represent real user actions (login, logout, search, media browsing, video playback)
• Events enable product insights — can build funnels (search → media_selected → trailer_played), engagement analysis
• Media-related events include enriched 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