This change wires @sentry/browser into the chat flow and captures the returned value in the mutation success path, alongside updating the error callback signature for better debugging context. The goal is to surface runtime issues from the chat interface that would otherwise be hard to reproduce from user reports alone. In practice, this should make production failures easier to investigate and shorten the path from bug report to fix.