# Changelog

## Score

- CAI 60 → 61 (+1.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 73 → 73 (+0.0)
- Architecture 91 → 91 (+0.0)
- Maturity 52 → 54 (+2.8)
- Readiness 56 → 56 (+0.1)
- Security 86 → 84 (-1.7)

## Resolved (5)

- Duplicate intent across similar types. `Slather.CoverageFile` and `Slather.ProfdataCoverageFile` share identical method signatures for `line_coverage_data` and `branch_coverage_data`. While they may handle different underlying formats (gcov vs profdata), the public API surface exposes redundant method names for the same logical operation (getting line/branch coverage). Additionally, `ProfdataCoverageFile` has `branch_region_data` which has no counterpart in `CoverageFile`, creating an asymmetry.
- Inconsistent method naming for report generation. `CoberturaXmlOutput` and `SonarqubeXmlOutput` use `create_xml_report`, while `HtmlOutput` uses `create_html_reports` (plural) and `create_html_from_file` (singular). The naming convention varies between 'create_[format]_report' and 'create_[format]s'.
- Inconsistent method naming for storing reports. Some output types use `store_report`, while others (like `HtmlOutput`) do not have this method, instead using `create_html_reports`. This suggests `store_report` is for saving to disk/cloud, while `create_*` is for generation. However, the lack of `store_report` in `HtmlOutput` and `SimpleOutput` makes the API inconsistent for the 'save' operation.
- Inconsistent naming convention for data retrieval methods. Some methods return a path (pathname), some return raw content (data), and some return processed coverage metrics. However, `source_file()` vs `source_file_pathname()` is ambiguous: does one return the string path and the other the file object? Similarly, `raw_data()` vs `source_data()` vs `gcov_data()` suggests overlapping or unclear distinctions between raw file content, parsed GCov format, and internal raw representation.
- Outdated: activesupport
