Summary

Scope renderer crash breadcrumbs and dedupe by the trusted Electron webContentsId so one renderer cannot make another renderer's crash look actionable.

This is a diagnostics-attribution fix. It does not claim to fix the underlying React #185, renderer OOM, native renderer, or Utility crash causes.

Why

Slack crash triage across 267 reports from 2026-08-20 through 2026-08-24 showed recurring renderer reports whose breadcrumb evidence could be global or sibling-renderer activity. The diagnosis thread is here. This matches the direction of PR #15709 and the React attribution caveat in PR #16153.

Changes

• Preserve trusted renderer origin through renderer breadcrumb IPC and process-gone events.
• Scope renderer error and process-gone dedupe per renderer while retaining child-process behavior.
• Filter renderer snapshots before applying the bounded recent breadcrumb budget.
• Keep suppressed and asynchronous failure breadcrumbs renderer-scoped.
• Include origin in in-memory coalescing/retained keys without persisting it to crash JSON or telemetry span breadcrumb attributes.
• Add deterministic regression coverage for sibling activity, dedupe, suppression, IPC sender routing, persistence scrubbing, and failure paths.

Validation

• pnpm test — 6,202 files, 58,274 tests passed; 40 files and 249 tests skipped by suite configuration.
• pnpm run lint — passed, including code-quality audits, reliability gates, max-lines ratchet, runtime-electron ratchet, skill manifests, and localization checks.
• pnpm run typecheck — passed.
• Focused crash-reporting suite — 25 files, 268 tests passed.
• Electron CDP smoke — candidate launched from this worktree; visible Orca UI rendered; real renderer breadcrumb and React error IPC flow recorded and dismissed a report; returned persisted report contained no internal renderer:<id> origin.
• Three fresh read-only delegated reviews — no blockers.

Risks and scope

• The retained high-water profile map remains globally capped at four entries; heavy multi-renderer activity can evict older historical profiles, but cannot cross-attribute them.
• Renderer reports intentionally omit sibling-renderer breadcrumbs, reducing some cross-renderer context.
• Per-renderer dedupe can retain more simultaneous reports, but all maps and persisted report storage remain bounded.
• No renderer UI, SSH/WSL, folder-workspace, mobile RPC, or remote-wire contract was changed.

Crash triage conclusion

React #185, OOM, generic renderer killed/crashed, and Utility clusters remain historical or inconclusive without a deterministic Orca-owned root cause. This PR improves the evidence needed for the next crash investigation; it is not an underlying crash-rate fix.