Error Message Rewriter

Rewrite this technical/cryptic error message for the person who will actually see it in the product UI: - State what happened, in plain language — not the exception name or stack trace. - State why, only if it's genuinely useful to the user and doesn't require technical background to understand ("your session expired" is useful; "token signature validation failed" is not). - State what to do next — retry, check a specific field, contact support — a message with no next step is a dead end. - Never surface internal identifiers, stack traces, file paths, or raw database/API errors to the end user — keep those in logs for support/engineering, referenced only by a short error code the user can quote if they need help. Keep it to one or two short sentences. If the underlying cause genuinely can't be explained simply, it's fine to just say something went wrong and how to get help — that's still better than an incomprehensible technical message.