[CI] (1776c51) vue/movies

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 1776c51
App: vue/movies
App directory: apps/vue/movies
Workbench branch: wizard-ci-1776c51-vue-movies
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-07-10T23:47:54.043Z
Duration: 200.7s

YARA Scanner

✓ 86 tool calls scanned, 0 violations detected

No violations: ✓ 86 clean scans

[wizard-ci-bot]

---

PR Evaluation Report

Summary

This PR integrates PostHog into a Vue 3 + Vite movies application. It adds posthog-js as a dependency, initializes it in main.js, implements user identification on login/page refresh, resets on logout, captures several meaningful product analytics events across search, media browsing, and trailer playback flows, and adds error tracking via captureException and a global Vue error handler.

Files changed	Lines added	Lines removed
9	+124	-7

Confidence score: 4/5 👍

• No reverse proxy configured: The app does not set up a reverse proxy (e.g., Vite rewrites) to route PostHog requests through the app's own domain, meaning ad blockers may intercept tracking requests. [MEDIUM]
• No .env.example updated: The PR introduces VITE_POSTHOG_PROJECT_TOKEN and VITE_POSTHOG_HOST env vars but does not add or update a .env.example file to document them. The report mentions this as a TODO but it should be part of the PR. [MEDIUM]
• Username used as distinct_id: posthog.identify(sanitizedUsername) uses the raw username string as the distinct ID. While functional for a demo app, in production this could cause collisions if usernames change or are reused. Acceptable for this demo context. [LOW]

---

File changes

Filename	Score	Description
package.json	5/5	Adds posthog-js dependency
src/main.js	4/5	Initializes PostHog with env vars and sets up global error handler
src/composables/useAuth.ts	4/5	Adds identify on login and page refresh, reset on logout, capture events for login/logout
src/views/MediaDetailView.vue	5/5	Captures media_detail_viewed and trailer_started events with rich properties
src/views/SearchView.vue	5/5	Captures search_performed with query metadata
src/components/media/MediaCard.vue	5/5	Captures media_selected on card click
src/components/carousel/CarouselAutoQuery.vue	5/5	Captures content_collection_loaded with collection metadata
src/components/NavBar.vue	5/5	Minor cleanup removing unused imports
posthog-setup-report.md	5/5	Wizard report documenting events and next steps

---

App sanity check ✅

Criteria	Result	Description
App builds and runs	Yes	No syntax errors; all imports are valid for a Vue 3 + Vite app
Preserves existing env vars & configs	Yes	Existing code and configs preserved; PostHog additions are additive
No syntax or type errors	Yes	All changed files use valid Vue 3 SFC and TypeScript syntax
Correct imports/exports	Yes	posthog-js imported correctly as default import in all files
Minimal, focused changes	Yes	Changes are tightly scoped to PostHog integration
Pre-existing issues	None	No pre-existing issues observed in the changed files

Issues

• No .env.example file: The PR introduces VITE_POSTHOG_PROJECT_TOKEN and VITE_POSTHOG_HOST environment variables but does not document them in a .env.example file. Collaborators won't know which env vars to set. [MEDIUM]

Other completed criteria

• All changes are relevant to PostHog integration
• Correct files modified for Vue 3 framework (main.js for init, composables for auth, components for events)
• Code follows existing codebase patterns (Vue 3 Composition API, <script setup> style)
• Build configuration valid — posthog-js added to package.json dependencies correctly

---

PostHog implementation ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js ^1.399.2 added to package.json
PostHog client initialized	Yes	posthog.init() called in src/main.js with env vars for token and host, and defaults: '2026-01-30'
capture()	Yes	7 meaningful capture calls across auth, search, media browsing, and trailer flows
identify()	Yes	posthog.identify() called on login and on page refresh when user exists in localStorage; posthog.reset() called on logout
Error tracking	Yes	Global app.config.errorHandler calls captureException; individual catch blocks also call captureException for carousel, media detail, recommendation, and search errors
Reverse proxy	No	No reverse proxy configured via Vite rewrites or other mechanism

Issues

• No reverse proxy: No Vite rewrite or other reverse proxy is configured, so PostHog requests go directly to us.i.posthog.com and are susceptible to ad blocker interception. [MEDIUM]

Other completed criteria

• API key loaded from import.meta.env.VITE_POSTHOG_PROJECT_TOKEN (not hardcoded)
• API host loaded from import.meta.env.VITE_POSTHOG_HOST with sensible fallback to https://us.i.posthog.com
• PostHog initialized before app mount, following Vue 3 docs pattern
• posthog.reset() correctly called on logout
• Identify called on page refresh for returning users (checks localStorage)

---

PostHog insights and events ✅

Filename	PostHog events	Description
src/composables/useAuth.ts	user_logged_in, user_logged_out	Tracks authentication flow with method property; identify on login and refresh, reset on logout
src/views/MediaDetailView.vue	media_detail_viewed, trailer_started, captureException	Tracks media page loads with type/title/trailer availability, and trailer plays; captures exceptions on load errors
src/views/SearchView.vue	search_performed, captureException	Tracks searches with query length, result count, and top result type; captures search errors
src/components/media/MediaCard.vue	media_selected	Tracks when a user clicks a movie/TV card with media type, ID, title, and collection context
src/components/carousel/CarouselAutoQuery.vue	content_collection_loaded, captureException	Tracks carousel content loads with title, type, query, and item count; captures load errors
src/main.js	captureException (global)	Global Vue error handler captures uncaught exceptions

Issues

No issues.

Other completed criteria

• Events represent real user actions (login, logout, search, browse, watch trailer)
• Events enable product insights — can build login→media_detail_viewed→trailer_started funnel
• Events include relevant contextual properties (media type, ID, title, counts, query length)
• No PII in event properties — username is used only in identify() person properties, not in capture properties
• Event names are descriptive and use consistent snake_case naming

---

Reviewed by wizard workbench PR evaluator