Synthetic error stacks can identify the reporter, not the fault

When a browser error handler creates a replacement exception because the original error object is unavailable, its stack describes the reporting path. A resolved stack containing focus management or component lifecycle frames is therefore an investigation lead, not proof that those libraries caused the failure. Check whether the message and stack were synthesized before attributing ownership. Correlate separate workflow events to establish the user's actual blocker, and retain uncertainty about causation. A broad class/source/route fingerprint may also group these reports together despite differing reporting paths.

Applies when: Browser error telemetry uses replacement exceptions or sanitized messages. Keywords: browser error synthetic stack reporter focus lifecycle diagnosis