[CI] (1776c51) javascript-node/native-http-contacts

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 1776c51
App: javascript-node/native-http-contacts
App directory: apps/javascript-node/native-http-contacts
Workbench branch: wizard-ci-1776c51-javascript-node-native-http-contacts
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-07-10T23:25:49.116Z
Duration: 223.7s

YARA Scanner

✓ 23 tool calls scanned, 0 violations detected

No violations: ✓ 23 clean scans

[wizard-ci-bot]

PR Evaluation Report

Summary

This PR integrates PostHog's posthog-node SDK into a native Node.js HTTP contacts API. It adds event capture for all CRUD operations (contact and group creation, updates, and deletion), exception tracking in the global error handler, and graceful shutdown to flush queued events.

Files changed	Lines added	Lines removed
3	+84	-1

Confidence score: 4/5 👍

• Environment variables not documented: POSTHOG_API_KEY and POSTHOG_HOST are not added to .env.example or any equivalent file. The setup report itself acknowledges this as a TODO — it should have been done by the wizard. [MEDIUM]

---

File changes

Filename	Score	Description
index.js	4/5	PostHog initialization, capture calls on all mutating endpoints, captureException in error handler, and graceful shutdown on SIGINT/SIGTERM
package.json	5/5	Adds posthog-node dependency
posthog-setup-report.md	4/5	New setup report documenting events and next steps

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	No syntax errors; valid ESM imports; posthog-node correctly added to dependencies
Preserves existing env vars & configs	Yes	Existing routes, data structures, and logic are untouched
No syntax or type errors	Yes	All added code is syntactically valid JavaScript
Correct imports/exports	Yes	PostHog correctly imported from posthog-node
Minimal, focused changes	Yes	Only PostHog-related code added; no scope creep
Pre-existing issues	None	—

Issues

• Missing .env.example update: POSTHOG_API_KEY and POSTHOG_HOST are required but not documented in any environment file. The setup report even lists this as a "verify before merging" task, but the wizard should have handled it. [MEDIUM]

Other completed criteria

• Build configuration is valid — package.json is well-formed with the new dependency
• Existing app functionality fully preserved

---

PostHog implementation ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-node@^5.40.0 added to package.json
PostHog client initialized	Yes	new PostHog(process.env.POSTHOG_API_KEY, { host, enableExceptionAutocapture: true }) at module scope — correct singleton pattern for a long-running server
capture()	Yes	4 meaningful capture calls across all mutating endpoints
identify()	N/A	Server-only app — distinct ID sourced from x-posthog-distinct-id header with 'anonymous' fallback
Error tracking	Yes	enableExceptionAutocapture: true configured, plus manual posthog.captureException(err, distinctId) in the global catch block
Reverse proxy	N/A	Server-only app using posthog-node — no ad-blocker concerns

Other completed criteria

• API key loaded from process.env.POSTHOG_API_KEY (not hardcoded)
• Host loaded from process.env.POSTHOG_HOST
• Graceful shutdown via SIGINT/SIGTERM handlers calling posthog.shutdown() — ensures all queued events are flushed

---

PostHog insights and events ✅

Filename	PostHog events	Description
index.js	group created	Captured when a new contact group is created; includes group_id and group_name properties
index.js	contact created	Captured when a new contact is added; includes contact_id, has_phone, has_company, group_id
index.js	contact updated	Captured on PATCH; includes contact_id and updated_fields (list of changed keys)
index.js	contact deleted	Captured on DELETE; includes contact_id
index.js	captureException	Unhandled server errors captured in the global catch block

Other completed criteria

• Events represent real CRUD user actions in the contacts domain
• Events enable product insights — a full create→update→delete funnel can be built
• Events are enriched with contextual properties (IDs, boolean flags, field lists)
• No PII in event properties — names, emails, and phone numbers are excluded from capture properties
• Event names are descriptive and use a consistent noun verb convention

---

Reviewed by wizard workbench PR evaluator