docs(blog): publish it-found-the-dead-analytics-it-called-them-p2 - #87
Conversation
Git-Session-Id: 166c
🤖 AI code reviewThis PR publishes a new blog post, _posts/2026-09-15-it-found-the-dead-analytics-it-called-them-p2.md, describing a PostHog Self-driving run on gptme.ai that found six issues, including a P2-rated outage of frontend analytics. It also adds a corresponding Open Graph image asset, assets/images/og/it-found-the-dead-analytics-it-called-them-p2.png. The post discusses the root cause (missing VITE_PUBLIC_POSTHOG_KEY in production build), the duplicate PR problem from issue-triage fanout, and recommendations to keep reports but implement manually. Safe to merge — no P0/P1 findingsConfidence 5/5 ✅ No findings. The diff looks correct to me on this pass. Files changed (1) — the diff as I read it
Reviewed Maintainer commands
|
Publish It Found the Dead Analytics. It Called Them P2. from today's PostHog Self-driving teardown on gptme.ai.
PostHog's first run found six real problems and zero false positives. The important one was seven days of dead frontend analytics (last
$lib=webevent 2026-09-08 02:25 UTC); it rated that P2. The live production bundle still has nophc_key. Filing tracker issues also tripped our issue-triage fanout into three duplicate PRs.Validation:
--validate --stricton the source postorigin/master(/tmp/worktrees/website-posthog-166c)_site/blog/it-found-the-dead-analytics-it-called-them-p2/index.htmlBrain source:
knowledge/blog/2026-09-15-it-found-the-dead-analytics-it-called-them-p2.mdIndependent fact-check (2026-09-16 monitoring, live GitHub + production, not from the diff):
.env.productionhttps://gptme.ai/assets/index-Mxwz0FTr.jsis 4.3MB and contains 0phc_tokens (PostHog SDK present, no project key)app/posthog-eu: #959–#962prod/2026-09-08.1followsprod/2026-08-05.2(34 days)