AI-product failure modes to recognize

A generic QA person triages crashes and 500s. Cursor's product breaks in ways that don't throw an exception at all - the diff is just wrong, the context was stale, the model quietly got worse. Naming these classes on sight is what marks you as a power user who debugs like an engineer.

The product round and the debugging screen both probe whether you actually understand how an AI code editor fails. Memorizing a taxonomy isn't enough; you should be able to map a vague report onto a failure class fast, because that class points at the right logs and the right team.