[CI] (4c70a79) javascript-node/hono-links

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 4c70a79
App: javascript-node/hono-links
App directory: apps/javascript-node/hono-links
Workbench branch: wizard-ci-4c70a79-javascript-node-hono-links
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-09-09T22:18:23.345Z
Duration: 307.2s

YARA Scanner

✓ 96 tool calls scanned, 0 violations detected

No violations: ✓ 96 clean scans

[wizard-ci-bot]

Now I have everything I need to evaluate. Here's the full review:

---

PR Evaluation Report

Summary

This PR integrates PostHog into a server-only Hono (Node.js) link management API using the posthog-node SDK. It adds event tracking for link CRUD operations and an error handler with captureException. However, every capture() and captureException() call is missing the required distinctId parameter, which means no events will be successfully sent to PostHog.

Files changed	Lines added	Lines removed
3	+63	-1

Confidence score: 4/5 👍

• All capture() calls are missing distinctId: The posthog-node SDK requires a distinctId on every capture() call. Unlike posthog-js in the browser, the server SDK does not auto-generate anonymous IDs. All three capture calls (link_created, link_updated, link_deleted) will throw or silently fail. [CRITICAL]
• captureException() called without distinctId: posthog.captureException(error) in the app.onError handler does not pass a distinctId, which is required by posthog-node. Error tracking will not function. [CRITICAL]
• enableExceptionAutocapture is not a valid posthog-node option: This configuration option belongs to posthog-js (browser SDK). The Node SDK does not have this option; it will be silently ignored but signals a confusion between the two SDKs. [MEDIUM]

---

File changes

Filename	Score	Description
apps/basic-integration/javascript-node/hono-links/index.js	2/5	Adds PostHog initialization, error handler, and capture calls — all missing required distinctId
apps/basic-integration/javascript-node/hono-links/package.json	4/5	Adds posthog-node dependency, re-sorts existing dependencies
apps/basic-integration/javascript-node/hono-links/.env.example	4/5	Documents required env vars for PostHog

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	Syntax is valid; the app will start, but PostHog calls will fail at runtime
Preserves existing env vars & configs	Yes	Existing code and routes are untouched
No syntax or type errors	Yes	All JS syntax is valid
Correct imports/exports	Yes	PostHog is correctly imported from posthog-node
Minimal, focused changes	Yes	Only PostHog-related additions
Pre-existing issues	None	Base app is clean

Issues

• enableExceptionAutocapture is a hallucinated option: This option does not exist in the posthog-node SDK. It belongs to posthog-js. It won't break anything (silently ignored), but it indicates the wizard confused the two SDKs. [MEDIUM]

Other completed criteria

• Environment variables documented in .env.example
• Build configuration (package.json) is valid
• Imports resolve to correct packages

---

PostHog implementation ❌

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-node v5.51.8 added to package.json
PostHog client initialized	Yes	new PostHog(token, { host }) pattern is correct for posthog-node, though enableExceptionAutocapture is invalid
capture()	No	All three capture calls are missing the required distinctId parameter
identify()	N/A	Server-only app
Error tracking	No	captureException(error) is missing distinctId; enableExceptionAutocapture is not a posthog-node option
Reverse proxy	N/A	Server-only app

Issues

• Missing distinctId on all capture() calls: posthog-node requires distinctId as a mandatory field in every capture() call. The server SDK does not auto-generate anonymous IDs. All three events (link_created, link_updated, link_deleted) are structured as posthog.capture({ event, properties }) without distinctId. Fix: extract a user identifier from the request (e.g., session, auth header, or IP) and pass it as distinctId. [CRITICAL]
• Missing distinctId on captureException(): The app.onError handler calls posthog.captureException(error) without a distinctId. The Hono error handler receives a context c, which could be used to derive a user identifier. [CRITICAL]
• No posthog.shutdown() on process exit: For a long-running Node server, events are batched. Without a graceful shutdown hook calling await posthog.shutdown(), the final batch of events may be lost when the process terminates. [LOW]

Other completed criteria

• API key loaded from environment variable (POSTHOG_PROJECT_TOKEN)
• Host correctly configured from environment variable (POSTHOG_HOST)

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
index.js	link_created	Tracks when a new link is saved, with tag_count and has_description properties — but missing distinctId
index.js	link_updated	Tracks link edits with updated_fields, is_favorite, tag_count — but missing distinctId
index.js	link_deleted	Tracks link deletion with no properties — but missing distinctId
index.js	captureException	Captures unhandled errors in app.onError — but missing distinctId

Issues

• Events are well-designed but non-functional: The event names are descriptive, properties are relevant and enriched, and no PII is included. However, none of these events will be successfully captured due to the missing distinctId parameter. [CRITICAL]

Other completed criteria

• Events represent real user actions (CRUD operations on links)
• Events could enable product insights (creation funnel, update patterns)
• Properties are enriched with contextual data (tag_count, updated_fields, etc.)
• No PII in event properties
• Event names follow consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator