# Changelog

## Score

- CAI 52 → 52 (-0.3)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 61 → 61 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 54 → 54 (+0.0)
- Readiness 72 → 71 (-1.1)
- Security 42 → 41 (-0.6)
- Domain Modelling 100 → 100 (+0.0)

## Resolved (5)

- Duplicate `campaigns` method across Database and Redis subscribers. Similar to `stats`, this indicates a fragmented API for retrieving campaign data without a shared abstraction.
- Duplicate `stats` method across Database and Redis subscribers with identical signatures. This redundancy suggests a lack of a unified statistics interface, making it difficult to swap backends without checking for method existence.
- Duplicate intent across subscriber implementations with identical signatures but different storage backends. While technically distinct implementations, the API surface exposes redundant method names for the exact same semantic action (tracking a send event) across different storage adapters without a shared interface or base class hinting at this polymorphism.
- Three different subscriber classes expose `track_click` with identical signatures. This creates a fragmented API where the same operation is available on multiple distinct types without a clear hierarchy or shared interface, leading to potential confusion about which subscriber to use in different contexts.
- Two different generator classes (for Clicks and Messages) both expose `copy_migration` with identical signatures. While the domains are distinct, the method name is generic and could be confusing if the generators were ever used interchangeably or if the method behavior differs subtly between domains.
