[CI] (4c70a79) angular/angular-saas

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 4c70a79
App: angular/angular-saas
App directory: apps/angular/angular-saas
Workbench branch: wizard-ci-4c70a79-angular-angular-saas
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-09-09T22:12:34.842Z
Duration: 366.9s

YARA Scanner

✓ 207 tool calls scanned, 0 violations detected

No violations: ✓ 207 clean scans

[wizard-ci-bot]

---

PR Evaluation Report

Summary

This PR integrates PostHog into an Angular SaaS application by adding posthog-js as a dependency, creating a PosthogService (initialized outside Angular's zone per docs), a custom PosthogErrorHandler for exception tracking, user identification tied to the credentials lifecycle, and meaningful capture events across login, logout, settings, and project management flows.

Files changed	Lines added	Lines removed
16	+130	-2

Confidence score: 5/5 🧙

• No reverse proxy configured: Client-side posthog-js events may be blocked by ad blockers without a reverse proxy. [MEDIUM]

---

File changes

Filename	Score	Description
posthog.service.ts	5/5	Core PostHog service with NgZone.runOutsideAngular init, defensive checks for missing env vars, and defaults: '2026-05-30'
posthog-error-handler.service.ts	5/5	Custom Angular ErrorHandler that forwards exceptions via captureException, preserves console.error
app.config.ts	5/5	Registers PosthogErrorHandler as the global ErrorHandler provider
credentials.service.ts	5/5	Adds identify() on load and credential change, reset() on logout and user switch
app.component.ts	5/5	Injects PosthogService to ensure early initialization
login.component.ts	5/5	Captures login_succeeded on successful auth
logout.component.ts	5/5	Captures logout_completed before setCredentials() triggers reset()
security-settings.component.ts	5/5	Captures two_factor_authentication_toggled with enabled property
notification-settings.component.ts	4/5	Captures notification_preferences_saved (no properties for what changed)
preferences-settings.component.ts	4/5	Captures preferences_saved (no properties for what changed)
add-member-modal.component.ts	5/5	Captures team_member_added with role property
create-project-modal.component.ts	5/5	Captures project_created with status property
environment.ts / environment.prod.ts	5/5	Adds posthogKey and posthogHost from env variables following existing pattern
.env.example	5/5	Documents required environment variables
package.json	5/5	Adds posthog-js dependency

---

App sanity check ✅

Criteria	Result	Description
App builds and runs	Yes	All imports resolve, Angular patterns are correct, no circular dependencies
Preserves existing env vars & configs	Yes	Only additive changes to environment files and app.config.ts
No syntax or type errors	Yes	TypeScript is valid, Angular decorators and DI patterns correct
Correct imports/exports	Yes	All imports from posthog-js, @angular/core, and app aliases are correct
Minimal, focused changes	Yes	Every change relates to PostHog integration
Pre-existing issues	The .env.ts file is a static object that doesn't auto-read OS env vars; NG_APP_* variables require a build-time tool like @ngx-env/builder to inject	Not introduced by this PR

Other completed criteria

• Environment variables documented in .env.example
• Build configuration is valid — posthog-js added to dependencies in package.json
• Code quality is high — follows existing Angular patterns (inject(), signals, services, providedIn: 'root')

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js ^1.429.0 added to package.json
PostHog client initialized	Yes	posthog.init() called inside NgZone.runOutsideAngular() with defaults: '2026-05-30' per Angular docs
capture()	Yes	8 meaningful capture calls across login, logout, settings, project creation, and member management
identify()	Yes	Uses credentials.id (stable string ID) as distinct_id; email, name, and role sent as person properties. Called on page load (constructor) and on credential change
Error tracking	Yes	Custom PosthogErrorHandler registered as global ErrorHandler, calls captureException()
Reverse proxy	No	No proxy configuration found (no proxy.conf.json, no angular.json rewrites, no Nginx/CDN config)

Issues

• No reverse proxy: Client-side PostHog requests will go directly to us.i.posthog.com (or whichever host is configured), making them susceptible to ad blockers. Consider setting up a reverse proxy using PostHog's managed service, Cloudflare, or a custom proxy configuration. [MEDIUM]

Other completed criteria

• API key loaded from environment variable (NG_APP_POSTHOG_PROJECT_TOKEN), not hardcoded
• Host correctly configured from environment variable (NG_APP_POSTHOG_HOST)
• posthog.reset() called on logout and on user switch (when credentials.id changes)
• Identify called on page refresh via constructor in CredentialsService
• Defensive client?. optional chaining throughout prevents errors if PostHog fails to initialize

---

PostHog insights and events ✅

Filename	PostHog events	Description
login.component.ts	login_succeeded	Tracks successful login
logout.component.ts	logout_completed	Tracks logout before reset
credentials.service.ts	identify(), reset()	Links events to authenticated users; resets on logout/user switch
security-settings.component.ts	two_factor_authentication_toggled	Tracks 2FA toggle with enabled boolean property
notification-settings.component.ts	notification_preferences_saved	Tracks notification settings save
preferences-settings.component.ts	preferences_saved	Tracks preferences save
add-member-modal.component.ts	team_member_added	Tracks member addition with role property
create-project-modal.component.ts	project_created	Tracks project creation with status property
posthog-error-handler.service.ts	captureException	Global error handler forwards all unhandled exceptions

Issues

• Some events lack properties: notification_preferences_saved and preferences_saved have no properties indicating what changed — adding a properties object with the changed settings would improve analytics utility. [LOW]

Other completed criteria

• Events represent real user actions that map to actual product flows (auth, settings, team management, project creation)
• Events enable product insights — can build login→action→logout funnels, track 2FA adoption, project creation rates
• No PII in capture() properties — email and name only used in identify() person properties
• Event names use consistent snake_case convention and are descriptive

---

Reviewed by wizard workbench PR evaluator