Blender operator reporting lacks persistent severity filtering in Info editor

Current notification behavior

Blender's unified reporting system routes all operator messages through self.report() with severity levels (INFO, WARNING, ERROR) displayed in the Info editor, status bar, and console. While messages are categorized by severity, there is no built-in mechanism to persistently filter or suppress specific message types or sources across sessions.

Filtering limitations

The Info editor provides only a temporary text filter that matches message content but resets on restart. It cannot filter by severity level or operator origin, meaning users cannot hide recurring low-priority messages such as "Auto Save" INFO entries while retaining WARNING or ERROR output.

Persistence gap

Notifications are ephemeral and not logged to disk by default. No native history panel exists to review messages after they scroll out of view, and the only status-bar notification setting is a render-completion sound toggle.

Can the Info editor filter be extended to support persistent severity-based rules? Is there a supported way to route specific operator reports to a separate log file without capturing all console output? Would a Python add-on using the standard logging module integrate cleanly with the existing reporting pipeline for end-user configuration?