[CI] (6fb03e7) python/meeting-summarizer

[wizard-ci-bot]

Automated wizard CI run

Source: scheduled
Trigger ID: 6fb03e7
App: python/meeting-summarizer
App directory: apps/python/meeting-summarizer
Workbench branch: wizard-ci-6fb03e7-python-meeting-summarizer
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-05-13T17:37:28.020Z
Duration: 591.8s

[wizard-ci-bot]

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a Python HTTP-based AI Meeting Summarizer app. A shared analytics.py module initializes the PostHog client using the Posthog() constructor with environment variables and atexit shutdown. Events are captured across server.py (login, logout, meeting CRUD, stats) and user_service.py (registration, deactivation) with enriched properties. Person properties are set via posthog_client.set() on login and registration.

Files changed	Lines added	Lines removed
6	+144	-0

Confidence score: 4/5 👍

• Email used as distinct_id for user_login_failed: Using raw email as distinct_id leaks PII into PostHog's person system and creates orphaned/fragmented profiles that can't be linked to real users. Should use an anonymous identifier or a hash. [MEDIUM]
• No .env.example file: POSTHOG_PROJECT_TOKEN and POSTHOG_HOST are required but not documented in any .env.example or equivalent. Developers cloning the repo won't know what to set. [MEDIUM]

---

File changes

Filename	Score	Description
analytics.py	5/5	Well-structured shared PostHog client module with Posthog() constructor, env var config, exception autocapture, atexit shutdown, and graceful None fallback
server.py	4/5	7 PostHog capture calls added at correct locations; email used as distinct_id for login failures is problematic
user_service.py	5/5	Clean integration for user_registered and user_deactivated events with proper distinct_id usage
requirements.txt	5/5	posthog and python-dotenv added correctly
.gitignore	5/5	Excludes .env file
posthog-setup-report.md	4/5	Wizard-generated report with event catalog and dashboard recommendations

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	No syntax errors, valid dependencies, correct imports
Preserves existing env vars & configs	Yes	All existing code untouched; PostHog calls wrapped in if posthog_client: guards
No syntax or type errors	Yes	All Python syntax is valid
Correct imports/exports	Yes	from analytics import posthog_client is correct; from posthog import Posthog is valid
Minimal, focused changes	Yes	Only PostHog-related additions
Pre-existing issues	None	Base app appears functional

Issues

• No .env.example file: Two environment variables (POSTHOG_PROJECT_TOKEN, POSTHOG_HOST) are required but no .env.example exists to document them. Add a .env.example with placeholder values. [MEDIUM]

Other completed criteria

• Build configuration is valid — requirements.txt is parseable with correct package specifiers
• posthog_client is guarded with if posthog_client: throughout, so the app works even without PostHog configured
• atexit.register(client.shutdown) ensures clean flush on exit

---

PostHog implementation ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog>=3.0.0 added to requirements.txt
PostHog client initialized	Yes	Uses Posthog() constructor in analytics.py with env vars, enable_exception_autocapture=True, and atexit.register(client.shutdown)
capture()	Yes	9 meaningful capture() calls across server.py and user_service.py
identify()	N/A	Server-only app
Error tracking	Yes	enable_exception_autocapture=True in constructor
Reverse proxy	N/A	Server-only app

Issues

• No default for POSTHOG_HOST: host=os.getenv('POSTHOG_HOST') passes None if unset. While the SDK may fall back to a default, it's safer to provide one: os.getenv('POSTHOG_HOST', 'https://us.i.posthog.com'). [LOW]

Other completed criteria

• API key loaded from POSTHOG_PROJECT_TOKEN environment variable, not hardcoded
• Person properties set via posthog_client.set() on login and registration — correct pattern for server-side SDK
• Graceful degradation when PostHog is not configured (returns None, all calls guarded)

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
server.py	user_logged_in, user_login_failed, user_logged_out, meeting_created, meeting_deleted, meeting_stats_viewed, user_deleted	Core user lifecycle and meeting CRUD events with enriched properties (word count, duration, participant count, etc.)
user_service.py	user_registered, user_deactivated	User registration and deactivation events with contextual properties
analytics.py	capturedException (autocapture)	Automatic exception tracking via enable_exception_autocapture=True

Issues

• Email as distinct_id in user_login_failed: The user_login_failed event uses distinct_id=email, sending raw PII (email address) as a distinct ID. This creates orphaned person profiles that can't be merged with real user profiles, and exposes PII in PostHog's person system. Use a hashed value or capture the event with the server's own ID and include a non-PII reason property instead. [MEDIUM]

Other completed criteria

• Events represent real user actions mapping to actual product flows (registration → login → create meetings → view stats)
• Events enable product insights — funnels (registration → login), trends (meeting_created), retention (user_deactivated)
• Events include relevant enriched properties: transcript_word_count, duration_minutes, participant_count, action_item_count, reason
• Event names are descriptive and follow consistent snake_case naming convention

---

Reviewed by wizard workbench PR evaluator