Q1How do you design REST error responses properly, and why is returning 200 OK with {"success": false} an anti-pattern
Use the right HTTP status code for the failure, return a consistent body with a stable error code, a human message, and a trace id, never leak stack traces, and centralise mapping with @RestControllerAdvice.