[CI] (3f39e0e) react-vite/court-booking

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 3f39e0e
App: react-vite/court-booking
App directory: apps/react-vite/court-booking
Workbench branch: wizard-ci-3f39e0e-react-vite-court-booking
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-09-23T22:30:06.184Z
Duration: 381.2s

YARA Scanner

✓ 78 tool calls scanned, 1 violation detected

  [BLOCKED] destructive_recursive_delete_high_risk (CRITICAL) — PreToolUse:Bash

No violations: ✓ 77 clean scans

⚠️ YARA violations detected — see report above

[wizard-ci-bot]

Now I have all the information needed. Let me produce the evaluation.

---

PR Evaluation Report

Summary

This PR installs posthog-js and initializes it in a new src/lib/posthog.ts module (imported from main.tsx) for a React+Vite padel court booking app that previously had no PostHog. The report explains that session replay enablement and all three scanners were blocked by missing MCP scopes — none were actually created. The SDK install itself is clean and minimal.

Files changed	Lines added	Lines removed
6	+102	-0

Confidence score: 5/5 🧙

• Scanners were not created: The report claims all three scanners were blocked by missing MCP scopes. Zero scanners exist in PostHog. The wizard's core job — creating three scanners tailored to this app — was not accomplished. [CRITICAL]
• Session replay not enabled: The server-side replay toggle was also blocked by the same scope issue. Recording is not active. [CRITICAL]
• No credit-spend estimates reported: Since no scanners were created, there are no credit-spend estimates, which is a required deliverable of the report. [MEDIUM]

---

File changes

Filename	Score	Description
posthog-replay-vision-report.md	2/5	Detailed report explaining blockers, but scanners and replay enablement are absent — the core deliverables
src/lib/posthog.ts	4/5	Clean PostHog init with env vars and dev-mode error throwing; uses defaults: '2026-05-30' correctly
src/main.tsx	5/5	Minimal import of posthog module at top — correct placement
package.json	5/5	posthog-js added as dependency
.env.example	5/5	Documents required env vars
.gitignore	5/5	Excludes .env

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	Report states pnpm build was verified clean
Preserves existing env vars & configs	Yes	No existing configs modified beyond adding posthog-js dep
No syntax or type errors	Yes	TypeScript code is valid
Correct imports/exports	Yes	posthog.ts exports default posthog, main.tsx imports side-effect module
Minimal, focused changes	Yes	Only PostHog SDK install + init, no app behavior changes
Pre-existing issues	None	—

Issues

• No app sanity issues found.

Other completed criteria

• PostHog init uses env vars (VITE_PUBLIC_POSTHOG_KEY, VITE_PUBLIC_POSTHOG_HOST) — correct for Vite
• Conditional init guards against missing key with dev-mode error
• Import placed before route imports in main.tsx

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.434.12 added to package.json
PostHog client initialized	Yes	posthog.init() called with env-read key/host and defaults: '2026-05-30'
capture()	N/A	replay-vision wizard is not supposed to add capture calls
identify()	N/A	replay-vision wizard is not supposed to add identify calls
Error tracking	N/A	Not in scope for replay-vision wizard
Reverse proxy	N/A	Not in scope for replay-vision wizard

Issues

• Session replay not enabled server-side: The wizard's primary deliverable — making session replay record — was blocked by MCP scope limitations. The client side has no disable_session_recording override (correct), but the server toggle was never flipped. [CRITICAL]

Other completed criteria

• SDK initialization is minimal (no identify, capture, dashboards added)
• defaults: '2026-05-30' config option used correctly
• Environment variables follow Vite naming convention

---

PostHog insights and events ❌

Filename	PostHog events	Description
N/A	N/A	No scanners were created; no events or insights were configured

Issues

• Zero scanners created: All three scanners (breakage monitor, frustration monitor, summarizer) were blocked by missing MCP scopes. The report describes planned specs but nothing was actually created in PostHog. [CRITICAL]
• No credit-spend estimates: Since no scanners exist, no monthly credit estimates are reported. [MEDIUM]

Other completed criteria

• Report does describe three scanner specs that reference correct app vocabulary (courts, slots, bookings)
• Planned breakage monitor correctly scopes to /book path (matching app's real routes)
• Planned frustration monitor uses `` as sole filter
• Planned summarizer targets 10% sampling
• Scanner names in the plan are product-specific ("Booking failures", "Court booking frustration", "Padel booking session recaps")

---

Reviewed by wizard workbench PR evaluator