Explain failed job errors to users

Goal:

1. Make the debugging experience better and easier for users by showing/explaining error clearly

Metric:
NPS

Problem Observations:

1. We have had reports of users not knowing what to do with errors don’t know what an error means e.g Killed or Crashed
2. We have implemented clearer error messages in logs but it can still be difficult for users to see the error messages
3. For a non-technical user, the logs can be verbose (even with the log filter) with error messages sandwiched

Constraints:
Adding a drawer or a new panel tab to the inspector might be expensive. We might consider adding this to the new layout when the implemented

Assumptions:
We already have error messages in the logs and it might be easier to extract them into a panel that communicates the error in simple language.

Solution Concepts:

• Final state based log filter
  Make the default log filter dependent on the job status. I should see an error when the job/step does not end in a successful state.

• Add a “What is this?” button or icon to job errors
  This will show the error message in a drawer or tab and allow users to see/hide AI recommendations when available.

The issue names no files, tests, or entry points. Review the existing job inspector and log experience, then clarify whether the selected scope is status-based log filtering, a “What is this?” error panel, or both; done should mean users can find and understand failed-job errors without scanning verbose logs.