fix(cli): report actual emissions file path

[davidberenstein1957]

Description

codecarbon/cli/monitor.py now asks the tracker's output handlers for their save_file_path instead of reconstructing the path from config keys. This keeps the CLI correct if the path logic changes, prints nothing when CSV output is disabled (previously a confidently wrong path), and handles multiple file handlers.

Related Issue

Fixes #1322

Motivation and Context

The codecarbon monitor post-run report resolved the emissions file path from tracker._conf["output_file"], which is only the basename. os.path.abspath then resolved it against the current working directory, so any output_dir other than the default "." produced a path where the file does not actually exist. The CLI defaults to log_level="error", which suppresses the correct INFO line FileOutput logs, so the wrong path was the only one the user saw. This is a display-only change; no measurement or file-writing behavior is affected.

How Has This Been Tested?

Three new tests in tests/cli/test_monitor.py: test_run_and_monitor_reports_output_dir, test_run_and_monitor_reports_relative_path_from_cwd, and test_run_and_monitor_reports_no_path_without_file_output. The first and third fail on master and pass with this change. uv run pytest tests/cli/test_monitor.py -q → 10 passed.

Screenshots (if appropriate):

N/A

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

AI Usage Disclosure

• 🟥 AI-vibecoded
• 🟠 AI-generated
• ⭐ AI-assisted
• ♻️ No AI used

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the docs/how-to/contributing.md document.
• I have added tests to cover my changes.
• All new and existing tests passed.

Also includes a related fix reporting the BoAmps output path in the CLI summary, with a relative-path test in tests/test_boamps_output.py.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.70%. Comparing base (e5e46ab) to head (869852b).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1331   +/-   ##
=======================================
  Coverage   91.70%   91.70%           
=======================================
  Files          49       49           
  Lines        5157     5158    +1     
=======================================
+ Hits         4729     4730    +1     
  Misses        428      428           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[benoit-cty]

🤖 This review comment was written and posted by Claude Opus 5.5 (AI assistant), at the request of @benoit-cty. Findings were checked by reading the code and running tests locally (merged with current master where relevant), but please double-check before acting on them.

Verdict: ✅ Approve with nits

The bug is real. The CLI report used abspath(_conf["output_file"]), which ignores output_dir. The new tests fail on master. Reading save_file_path from each output handler, and printing no path when CSV output is off, is the right fix.

Nits:

1. BoAmps output also writes files but has no save_file_path, so its files are not reported. Consider giving it a save_file_path, or reporting every handler that has one.
2. The description lists test_run_and_monitor_reports_relative_path_from_cwd, which is not in the diff. Please update the description, or add the test.
3. The branch is behind master; please update it.

[davidberenstein1957]

Made the changes in 869852b: merged master, BoAmps reports now listed, added the relative-path test.

BoAmpsOutput sets save_file_path after writing its report, so the CLI summary picks it up with no special case.