feat: write renderer and main traces with crashreporter

[jonathanlab]

Problem

Changes

How did you test this?

Publish to changelog?

[jonathanlab]

• feat: write renderer and main traces with crashreporter #2003 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Security Review

• Crash primitives exposed in production (apps/code/src/main/preload.ts): window.__posthogCodeTest.crash() / window.__posthogCodeTest.abort() are registered via contextBridge.exposeInMainWorld unconditionally, making them available on window in production builds. Any XSS or renderer navigation to untrusted content can invoke these to crash the renderer or main process. Guard behind POSTHOG_CODE_IS_DEV.

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
apps/code/src/main/preload.ts:8-15
**`__posthogCodeTest` exposed in production builds**

`contextBridge.exposeInMainWorld` here runs unconditionally, so `window.__posthogCodeTest.crash()` and `window.__posthogCodeTest.abort()` are callable from any renderer page — including production. Any XSS or accidental navigation to untrusted content could invoke these to deliberately crash the renderer or main process. The env variable `process.env.POSTHOG_CODE_IS_DEV` is already set in `bootstrap.ts` and is accessible from the preload context.

```suggestion
if (process.env.POSTHOG_CODE_IS_DEV === "true") {
  contextBridge.exposeInMainWorld("__posthogCodeTest", {
    crash: () => {
      process.crash();
    },
    abort: () => {
      process.abort();
    },
  });
}
```

### Issue 2 of 2
apps/code/src/main/index.ts:60-82
**No retry limit on crash recovery — potential infinite reload loop**

If the renderer crashes deterministically on load (e.g., a startup bug, persistent OOM, or bad state in local storage), the `render-process-gone` handler will trigger, reload the page, which crashes again, and repeat indefinitely. Adding a small counter with a maximum attempt threshold (e.g., 3 retries within a 30-second window) would avoid spinning the process in a tight crash/reload cycle.

_{Reviews (1): Last reviewed commit: "feat: write renderer and main traces wit..." | Re-trigger Greptile}