# Changelog

## Score

- CAI 65 → 65 (+0.0)
- Rubric changed (rubric-2026.09.8 → rubric-2026.09.16) — scores are not directly comparable.

## Lenses

- Code Health 93 → 93 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 55 → 55 (+0.0)
- Readiness 67 → 67 (+0.0)
- Security 98 → 99 (+0.4)

## Resolved (2)

- Documentation: no installation or build instructions (README.md)
- Documentation: no usage examples (README.md)

## New (4)

- Conflicting naming and signature for the same core functionality: `group_by_period` vs `group_by`. The `Enumerable` module exposes `group_by_period` with 4 args, while `Groupdate.Magic.Enumerable` exposes `group_by` with 2 or 4 args. This creates confusion about which method to use for grouping by time periods.
- Documentation: no architecture or design documentation (README.md)
- Duplicate operation: `process_result` is defined on both the main `Groupdate` module and the internal `Groupdate.Magic.Relation` class with identical signatures. This suggests either a delegation pattern that is not explicit or a copy-paste error leading to maintenance overhead.
- Inconsistent parameter ordering and naming for similar operations: `QueryMethods.group_by_period` takes `field` as the second argument, while `Magic.Enumerable.group_by` takes `enum` as the first. This inconsistency in argument position and naming (`field` vs `enum`) makes the API unpredictable for developers switching between query and enumerable contexts.