# Changelog

## Score

- CAI 41 → 41 (+0.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 72 → 74 (+2.0)
- Architecture 69 → 69 (+0.0)
- Maturity 43 → 43 (+0.0)
- Readiness 45 → 45 (+0.0)
- Security 97 → 98 (+0.9)
- Accessibility 28 → 28 (+0.0)

## Resolved (3)

- Duplication of aggregation logic between Domain and View layers. `Activity` provides raw aggregation methods (e.g., `by_date`), while `ActivityCharts` provides identical methods (e.g., `activity_by_date`) that likely perform the same grouping. This violates DRY principles and creates two sources of truth for the same data transformation.
- Inconsistent naming and scope for author-based aggregations. `Repo` has a method for counting commits by author, while the View layer has a method for summing commits by author by date. The naming conventions differ (`commits_count` vs `commits_sum`), and the scope (total count vs time-series sum) is not clearly distinguished by naming, leading to potential confusion about which method to use for specific reporting needs.
- Redundant execution interfaces. Repo exposes both a direct `run` and a `run_and_parse` method, while also exposing a dedicated `CommandRunner` component. The `CommandRunner` class exists to encapsulate execution logic, but `Repo` duplicates this capability directly, creating confusion about whether to use the component or the direct method.

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
