[CI] (0ae2102) javascript-node/koa-notes

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 0ae2102
App: javascript-node/koa-notes
App directory: apps/javascript-node/koa-notes
Workbench branch: wizard-ci-0ae2102-javascript-node-koa-notes
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-04-15T19:13:51.552Z
Duration: 250.9s

[wizard-ci-bot]

Now I have all the information I need to produce the evaluation report.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a Koa.js notes API (server-only Node.js app). The posthog-node SDK is added to package.json, initialized in index.js with environment variables, and six meaningful capture events are added across all CRUD and search routes. Error tracking is implemented via app.on('error') with captureException, and graceful shutdown is handled via posthog.shutdown() on SIGINT.

Files changed	Lines added	Lines removed
3	+96	-1

Confidence score: 4/5 👍

• No .env.example or equivalent documentation for POSTHOG_API_KEY and POSTHOG_HOST: New environment variables are used but not documented in any .env.example file or README. Consumers of this app won't know which env vars to set. [MEDIUM]
• Search query included as event property: The notes_searched event includes the raw query property which could contain user-generated content or PII depending on what users type into the search. [LOW]

---

File changes

Filename	Score	Description
apps/javascript-node/koa-notes/index.js	4/5	Added PostHog import, initialization, getDistinctId helper, 6 capture calls across all mutating/search routes, error tracking via app.on('error'), and graceful shutdown
apps/javascript-node/koa-notes/package.json	5/5	Added posthog-node dependency; minor reordering of existing deps (alphabetical)
apps/javascript-node/koa-notes/posthog-setup-report.md	4/5	Wizard setup report documenting events and recommended dashboards

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	Valid ESM syntax, all imports resolve, no build step required beyond node index.js
Preserves existing env vars & configs	Yes	Existing PORT env var and all app logic preserved; only PostHog additions
No syntax or type errors	Yes	All JavaScript syntax is valid; method signatures match posthog-node API
Correct imports/exports	Yes	import { PostHog } from 'posthog-node' is the correct named export
Minimal, focused changes	Yes	Only PostHog integration code added; the koa-bodyparser reorder in package.json is cosmetic (alphabetical sorting)
Pre-existing issues	None	Base app is clean

Issues

• No .env.example for PostHog env vars: POSTHOG_API_KEY and POSTHOG_HOST are read from process.env but no .env.example or README documents these required variables. New developers won't know what to configure. [MEDIUM]

Other completed criteria

• Build configuration is valid — package.json has correct "type": "module", valid scripts, and parseable dependency list
• Existing app functionality fully preserved — all routes, data structures, and logic unchanged

---

PostHog implementation ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-node: ^5.29.2 added to package.json dependencies
PostHog client initialized	Yes	new PostHog(process.env.POSTHOG_API_KEY, { host: process.env.POSTHOG_HOST, enableExceptionAutocapture: true }) — correct constructor pattern for posthog-node
capture()	Yes	Six well-placed capture calls: folder_created, folder_deleted, notes_searched, note_created, note_updated, note_deleted
identify()	N/A	Server-only Koa app — identify is not applicable
Error tracking	Yes	posthog.captureException(err, distinctId) in app.on('error') handler with correct signature, plus enableExceptionAutocapture: true for uncaught exceptions
Reverse proxy	N/A	Server-only app — reverse proxy not applicable

Issues

None.

Other completed criteria

• API key loaded from process.env.POSTHOG_API_KEY — not hardcoded
• Host loaded from process.env.POSTHOG_HOST — correctly configured via environment variable
• getDistinctId helper reads x-posthog-distinct-id header with fallback to ctx.ip, providing reasonable server-side user correlation
• Graceful shutdown via posthog.shutdown() on SIGINT ensures events are flushed before process exits
• enableExceptionAutocapture: true enables automatic capture of uncaught exceptions and unhandled rejections

---

PostHog insights and events ✅

Filename	PostHog events	Description
index.js	folder_created	Captures folder creation with folder_id and folder_name
index.js	folder_deleted	Captures folder deletion with folder_id and folder_name
index.js	notes_searched	Captures search queries with query, result_count, and optional folder_id
index.js	note_created	Captures note creation with note_id, folder_id, and has_content boolean
index.js	note_updated	Captures note updates with note_id, folder_id, and updated_fields array
index.js	note_deleted	Captures note deletion with note_id and folder_id
index.js	captureException	Error tracking via app.on('error') handler and automatic uncaught exception capture

Issues

• Search query in event properties: The notes_searched event includes the raw query property, which could contain user-generated content. While search terms are generally acceptable for analytics, they could potentially include PII if users search for names or emails. Consider whether this is acceptable for your use case. [LOW]

Other completed criteria

• Events represent real user actions — each maps to a concrete CRUD or search operation in the notes app
• Events enable product insights — can build funnels (search → create), track engagement (updates over time), measure deletion rates
• Events include relevant enriched properties — IDs, names, result counts, field lists, content flags
• Event names are descriptive and use consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator