[CI] (e2f7ab0) javascript-node/express-todo

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: e2f7ab0
App: javascript-node/express-todo
App directory: apps/javascript-node/express-todo
Workbench branch: wizard-ci-e2f7ab0-javascript-node-express-todo
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-07-06T21:59:32.803Z
Duration: 251.3s

YARA Scanner

✓ 21 tool calls scanned, 0 violations detected

No violations: ✓ 21 clean scans

[wizard-ci-bot]

PR Evaluation Report

Summary

This PR integrates PostHog into a server-only Express.js todo API using the posthog-node SDK. It adds event tracking for all CRUD operations (create, update, complete, delete), error tracking via setupExpressErrorHandler, request context propagation via setupExpressRequestContext, and graceful shutdown handling.

Files changed	Lines added	Lines removed
3	+98	-2

Confidence score: 4/5 👍

• Missing .env.example: Environment variables POSTHOG_API_KEY and POSTHOG_HOST are not documented in a committed .env.example file. The setup report acknowledges this as a "verify before merging" step, but the wizard should have done it. [MEDIUM]

---

File changes

Filename	Score	Description
apps/basic-integration/javascript-node/express-todo/index.js	5/5	PostHog initialization, request context middleware, capture calls on all mutating routes, error handler, and graceful shutdown
apps/basic-integration/javascript-node/express-todo/package.json	5/5	Added posthog-node dependency
apps/basic-integration/javascript-node/express-todo/posthog-setup-report.md	4/5	Setup report with event table and next steps; notes env vars need to be added to .env.example

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	No syntax errors; posthog-node added to dependencies correctly
Preserves existing env vars & configs	Yes	Existing Express routes, middleware, and in-memory store preserved; only additive changes
No syntax or type errors	Yes	Valid CommonJS imports and correct API usage throughout
Correct imports/exports	Yes	PostHog, setupExpressRequestContext, setupExpressErrorHandler correctly imported from posthog-node
Minimal, focused changes	Yes	Only PostHog-related additions; no unrelated refactors
Pre-existing issues	None	Base app is a straightforward Express API with no issues

Issues

• Missing .env.example: POSTHOG_API_KEY and POSTHOG_HOST are read from process.env but no .env.example file was committed. The report acknowledges this gap but the wizard should have created it. [MEDIUM]

Other completed criteria

• All changes are relevant to PostHog integration
• Code follows existing codebase conventions (CommonJS, Express patterns)
• Build configuration (package.json) is valid with correct dependency format

---

PostHog implementation ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-node ^5.39.4 added to package.json dependencies
PostHog client initialized	Yes	new PostHog(process.env.POSTHOG_API_KEY, { host, enableExceptionAutocapture: true }) — correct pattern for Node SDK
capture()	Yes	Four meaningful capture calls across CRUD routes
identify()	N/A	Server-only app — distinct_id correctly derived from x-posthog-distinct-id header or req.ip fallback
Error tracking	Yes	setupExpressErrorHandler(posthog, app) registered after routes, plus enableExceptionAutocapture: true in init
Reverse proxy	N/A	Server-only app — reverse proxy not applicable

Other completed criteria

• API key loaded from environment variable (process.env.POSTHOG_API_KEY), not hardcoded
• Host loaded from environment variable (process.env.POSTHOG_HOST)
• setupExpressRequestContext middleware registered before routes for automatic context propagation
• Graceful shutdown via SIGTERM handler calling posthog.shutdown()
• getDistinctId helper uses x-posthog-distinct-id header with req.ip fallback — reasonable for a server-only API

---

PostHog insights and events ✅

Filename	PostHog events	Description
index.js	todo_created	Captured when a new todo is created via POST; includes todo_id and title properties
index.js	todo_updated	Captured when a todo is patched; includes todo_id, title, and completed status
index.js	todo_completed	Captured specifically when a todo transitions from incomplete to complete; includes todo_id and title
index.js	capturedException	Unhandled Express errors forwarded via setupExpressErrorHandler

Other completed criteria

• Events represent real user actions (CRUD operations on todos)
• Events enable product insights — todo_created → todo_completed forms a natural funnel; todo_deleted tracks churn
• Events include enriched properties (todo_id, title, completed status)
• No PII in event properties — only todo metadata, no user emails/names/phones
• Event names use consistent snake_case convention and are descriptive of the action

---

Reviewed by wizard workbench PR evaluator