[wizard-ci-bot]

Automated wizard CI run

Source: scheduled
Trigger ID: cc5471b
App: python/meeting-summarizer
App directory: apps/python/meeting-summarizer
Workbench branch: wizard-ci-cc5471b-python-meeting-summarizer
Wizard branch: main
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-10-28T16:54:03.470Z
Duration: 411.9s

YARA Scanner

✓ 140 tool calls scanned, 0 violations detected

No violations: ✓ 140 clean scans

[wizard-ci-bot]

---

PR Evaluation Report

Summary

This PR integrates PostHog into a Python meeting summarizer HTTP server application. It adds the PostHog Python SDK with proper initialization, context-based request wrapping, user identification, multiple event captures for key user actions, exception autocapture, and OTLP-based log export to PostHog. The integration is well-structured overall, but contains a runtime bug in the set() call.

Files changed	Lines added	Lines removed
4	+164	-4

Confidence score: 4/5 👍

• posthog_client.set() called with positional distinct_id: The SDK's set() method accepts only keyword arguments (**kwargs: Unpack[OptionalSetArgs]). The call posthog_client.set(user.user_id, properties=properties) passes user.user_id as a positional argument, which will raise a TypeError at runtime. Must be posthog_client.set(distinct_id=user.user_id, properties=properties). [CRITICAL]
• user_logged_in and user_logged_out events lack properties: These captures have no contextual properties. Adding at least a login method or session-related property would improve analytical value. [LOW]

---

File changes

Filename	Score	Description
apps/basic-integration/python/meeting-summarizer/.env.example	5/5	Documents both POSTHOG_PROJECT_TOKEN and POSTHOG_HOST env vars
apps/basic-integration/python/meeting-summarizer/.gitignore	5/5	Correctly excludes .env from version control
apps/basic-integration/python/meeting-summarizer/requirements.txt	4/5	Adds posthog SDK and OTel deps for log export; OTel adds 3 packages for a secondary feature
apps/basic-integration/python/meeting-summarizer/server.py	3/5	Well-structured PostHog integration with context wrapping and meaningful events, but has a runtime bug in set() call

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	Dependencies are valid, code structure is correct
Preserves existing env vars & configs	Yes	Only adds PostHog-related code; no existing functionality removed
No syntax or type errors	No	posthog_client.set(user.user_id, properties=properties) passes distinct_id positionally to a **kwargs-only method — will raise TypeError at runtime
Correct imports/exports	Yes	All imports are valid (posthog, dotenv, opentelemetry packages)
Minimal, focused changes	Yes	All changes serve PostHog integration (analytics + log export)
Pre-existing issues	None	—

Issues

• set() positional argument bug: posthog_client.set(user.user_id, properties=properties) on line 215 passes user.user_id as a positional argument. The SDK's set() only accepts keyword arguments. Fix: posthog_client.set(distinct_id=user.user_id, properties=properties). [CRITICAL]

Other completed criteria

• App builds without errors (dependencies are installable, no syntax errors)
• Existing app code and configs preserved — only PostHog additions
• Environment variables documented in .env.example
• requirements.txt is valid with pinned versions

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog==7.78.0 in requirements.txt
PostHog client initialized	Yes	Posthog() constructor with project token, host, and enable_exception_autocapture=True; atexit.register(client.shutdown) ensures flush on exit
capture()	Yes	5 meaningful events: meeting_viewed, user_logged_in, user_logged_out, meeting_created, meeting_deleted
identify()	N/A	Server-only app; however, correctly uses identify_context() within request contexts for user attribution
Error tracking	Yes	enable_exception_autocapture=True in constructor; contexts wrap all HTTP handlers
Reverse proxy	N/A	Server-only app

Issues

• set() call will fail at runtime: The person property setting via posthog_client.set(user.user_id, properties=properties) will throw a TypeError because the SDK method only accepts keyword arguments. This means person properties are never set on login. Fix: use posthog_client.set(distinct_id=user.user_id, properties=properties). [CRITICAL]

Other completed criteria

• API key loaded from POSTHOG_PROJECT_TOKEN environment variable
• Host loaded from POSTHOG_HOST environment variable
• atexit.register(client.shutdown) ensures event flush on process exit
• Request context decorator (with_posthog_request_context) creates fresh context per request and identifies authenticated users
• Development mode validation raises errors for missing configuration

---

PostHog insights and events ✅

Filename	PostHog events	Description
server.py	meeting_viewed	Captures when a user views a meeting with duration, participant/action item/key point counts
server.py	user_logged_in	Captures successful login (no additional properties)
server.py	user_logged_out	Captures logout (no additional properties)
server.py	meeting_created	Captures meeting creation with transcript word count, action items, key points, participants, duration
server.py	meeting_deleted	Captures meeting deletion with meeting metadata properties
server.py	capturedException	Autocaptured via enable_exception_autocapture=True within request contexts

Issues

• No critical or medium issues with event quality.

Other completed criteria

• Events represent real user actions (view, login, logout, create, delete)
• Events enable product insights — can build login→create→view funnels, retention on meeting creation
• Most events include relevant properties (duration, counts, metadata)
• No PII in event properties — email/username/full_name correctly placed in set() person properties
• Event names are descriptive and use consistent snake_case convention
• OTLP log export captures meeting_analysis_completed and meeting_deleted structured logs

---

Reviewed by wizard workbench PR evaluator