Game crash and error triage

Most errors players hit don't crash anything. The engine skips the rest of a function and carries on, so a pickup never adds its score, a menu never opens, or an effect never shows, and nobody writes in. Treat errors as seriously as crashes.

1. Collect and group

Group reports by fingerprint (the error message with numbers stripped, plus the top stack frame), not by occurrence. One loop can log the same error 500 times in one session. Rank each group by sessions or players affected, then by whether it's fatal, then by count.

For each group, get:

• the message, the stack, and the file and line (minified web builds need source maps to be readable);
• the events just before it (breadcrumbs): level start, pickup, menu opened, purchase;
• the version it first appeared in, and whether it's still happening in the latest one;
• the devices: OS, GPU, renderer, screen. Errors on one GPU family are a device problem, not your logic.