fix(analytics): stop capturing exceptions from local dev hosts

[posthog-eu]

Summary

• Who is hurt: the team, not users. Every refactor can mint a fresh production error-tracking issue from a developer laptop, and each one costs a triage and research cycle.
• Mechanism: the capture gate in src/services/posthog.ts skips analytics only when the Supabase host is local. A developer running the frontend against remote or preprod Supabase passes that gate, so transient compile and hot-reload errors from a Vite dev server reach production error tracking.
• Fix: extend the existing before_send suppression hook to also drop $exception events whose page host is a local dev host (localhost, 127.0.0.1, *.local), read from $host and, as a fallback, the host parsed from $current_url.
• Scope is intentionally narrow: no shipped bug is changed. disableRollout is correctly defined in current main; the reported ReferenceError came from one developer's dev server ($host = localhost:5175) mid-edit.

Test plan

• bunx vitest run tests/stale-asset-errors.unit.test.ts — 16 tests pass.
• New tests cover the isLocalDevHost helper (localhost/127.0.0.1/*.local with and without a port; production hosts and empty/undefined values rejected) and the host-based suppression path (drop by $host, drop by $current_url fallback, keep the same exception from the production host).

Screenshots

Not applicable — no user-facing behaviour changes. The change only affects which client-side exception events are sent to error tracking.

Checklist

• My code follows the code style of this project and passes
  bun run lint:backend && bun run lint.
• My change requires a change to the documentation.
• I have updated the documentation
  accordingly.
• My change has adequate E2E test coverage.
• I have tested my code manually, and I have provided steps how to reproduce
  my tests

---

Created with PostHog Desktop from this inbox report.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 1902cf67-d231-4d73-af3a-39d47be10c06

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codspeed]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing posthog-self-driving/fixanalytics-stop-capturing-exceptions-0c5e46 (13f6a34) with main (a8ca6fe)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud