🤖 feat: move telemetry reporting to backend

[ammar-agent]

Summary

Moves telemetry event capture from the browser (posthog-js) to the Electron main process (posthog-node). Events from the renderer are forwarded via ORPC to the backend TelemetryService.

Problem

Ad blockers can intercept and block network requests to PostHog's servers (us.i.posthog.com) from the browser/renderer process, causing telemetry to be silently dropped.

Solution

Move telemetry to the main process using posthog-node. The main process makes direct HTTP requests that aren't subject to browser-based ad blocking.

Architecture

flowchart LR
    subgraph Renderer["Renderer (Browser)"]
        A[useTelemetry hook]
        B[trackEvent calls]
    end
    
    subgraph Main["Main Process (Node.js)"]
        C[ORPC telemetry routes]
        D[posthog-node client]
    end
    
    E[(PostHog)]
    
    A --> B
    B -->|ORPC| C
    C --> D
    D -->|HTTP| E

Loading

Changes

• New: posthog-node dependency
• New: TelemetryService in src/node/services/
• New: ORPC telemetry.{track, setEnabled, isEnabled} routes
• Updated: Frontend client now calls backend via ORPC
• Simplified: Payload types no longer require base properties from frontend

What Stays the Same

• useTelemetry() hook API
• trackEvent() function signature
• Opt-out UX via localStorage
• All existing event types

Testing

• make typecheck ✅
• make lint ✅
• make static-check ✅
• make test (1 pre-existing failure unrelated to this PR)

Generated with mux

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.