fix: resolve PostHog analytics health findings

[flamboh]

Note

🤖 GPT-5.6 Sol on behalf of Oliver

Problem

PostHog reported four analytics health findings: an outdated browser SDK, missing web vitals, an undetected reverse proxy, and no authorized app URLs.

What changed

• upgrade posthog-js; the lockfile resolves 1.426.2
• collect CLS, FCP, INP, and LCP without attribution details
• preserve the configured first-party ingestion host marker while continuing to reject untrusted hosts
• add tagium.app and save.tagium.app to the PostHog project through the CLI

The authorized URL finding has already cleared. The other checks need a production deployment and fresh events before PostHog can mark them healthy.

Review

1. Wait for the Cloudflare preview and open both app routes.
2. Upload a local audio file in tagium and confirm the editor still opens normally.
3. Open tagium save and confirm the URL import form still loads and accepts input.

Preview builds do not send analytics. The expected preview result is no user-facing regression or analytics-related console error.

The privacy boundary is intentional. Only numeric web-vital values pass the event sanitizer. Attribution selectors, page URLs, and a proxy host that does not exactly match the configured analytics host remain excluded.

Automated verification completed with bun run test at 661 passing tests, bun run build, and bun run lint. Lint reports only existing warnings outside this change.

Changes made by GPT-5.6 Sol using the Codex harness in T3 Code.

[github-actions]

React Doctor found no new issues. 🎉

_{Reviewed by React Doctor for commit 1e9ebe4.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	tagium	1e9ebe4	Commit Preview URL Branch Preview URL	Sep 03 2026, 11:29 PM