# Changelog

## Score

- CAI 77 → 79 (+1.6)
- Rubric changed (rubric-2026.09.11 → rubric-2026.09.18) — scores are not directly comparable.

## Lenses

- Code Health 95 → 95 (-0.1)
- Architecture 96 → 99 (+3.4)
- Maturity 75 → 75 (+0.0)
- Readiness 67 → 71 (+3.9)
- Security 100 → 100 (+0.0)

## New (6)

- Coverage not measured — Swift suite
- Documentation: no installation or build instructions (README.md)
- Documentation: no usage examples (README.md)
- Duplicated block (8 lines × 2) (Sources/Public/DayRange.swift)
- Inconsistent naming convention for SwiftUI view customization. Some methods use the plural noun form indicating the element being customized (e.g., `days`, `dayBackgrounds`, `monthHeaders`), while others use the singular noun form indicating the provider mechanism (e.g., `dayItemProvider`, `monthHeaderItemProvider`). This creates two parallel APIs for the same intent: one returning a `CalendarViewRepresentable`/`Self` directly, and another returning a `CalendarViewContent` builder. While technically distinct return types, the naming `days` vs `dayItemProvider` is confusingly similar in intent but different in signature and return type, forcing users to choose between two similarly-named but structurally different methods.
- Inconsistent naming for the same UI event. The UIKit `CalendarView` exposes the event as `didEndDragging`, while the SwiftUI wrapper `CalendarViewRepresentable` exposes it as `onDragEnd`. While `onDragEnd` is more idiomatic for SwiftUI, the discrepancy with the underlying UIKit property name (`didEndDragging`) creates confusion about whether these are the same event or different ones, especially since the signatures are identical.