Prerequisites

• This was not already reported in the past (duplicate check)
• It does reproduce it with code from main branch (latest unreleased version)
• I include a minimal example for reproducing the bug
• The bug is not trivial, as for those a direct pull-request is preferred
• Running pip check does not report any conflicts
• I was able to reproduce the issue on a different machine
• The issue is not specific to any driver other than 'default' one

Environment

n/a

What happened

stdout is for normal output: status messages, progress, and success reports.
stderr is for errors, warnings, and diagnostics.
For Python apps (including Molecule/Ansible):
INFO and DEBUG messages go to stdout.
WARNING, ERROR, and CRITICAL messages go to stderr.
This separation is typical and best practice for CLI tools.
End-of-run reports:
If the report indicates success, send it to stdout.
If it indicates failures or errors, send it to stderr.
This approach helps users and automation tools easily distinguish between successful output and problems.

Reproducing example