fix(frontend): suppress posthog-js internal request-timeout abort

[posthog-eu]

Summary

• The error tracking issue AbortError: PostHog request timed out after 3000ms is telemetry noise: posthog-js aborts its own outgoing request on an internal timeout, and exception autocapture then files that abort as a page error, even though no application code raises it. No user-facing flow breaks.
• The abort is reported inside the bundled posthog-js core (buildOtlpLogRecord → _processInitTaskQueue), so the reverse proxy at psthg.capgo.app, an offline tab, or a page unload is enough to trip it.
• Fix: add one anchored pattern to TRANSIENT_NETWORK_ERROR_PATTERNS in src/services/staleAssetErrors.ts, which before_send in src/services/posthog.ts already uses to drop known noise.

The pattern is kept tight so a genuine app-side abort with a different message still reports:

/^(?:.*: )?PostHog request timed out after \d+ms$/i

• \d+ms covers both the 3000ms message and the earlier 10000ms variant.
• The optional (?:.*: )? prefix matches the wording either bare or with the AbortError: type prefix, consistent with the other transient-network patterns.

Test plan

• bun run vitest run tests/stale-asset-errors.unit.test.ts — 14 pass, including new cases for the timeout message, the 10000ms variant, the AbortError: prefix, and a negative case (PostHog request timed out after a while) that must still report.
• npx eslint src/services/staleAssetErrors.ts tests/stale-asset-errors.unit.test.ts — clean.

Screenshots

Not applicable — suppression logic only, no UI change.

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: 7d344c4f-6ea7-4a4f-a414-1600911c6827

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/fixfrontend-suppress-posthog-sdk-26c45b (7b4af7d) with main (eff31d2)}

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