# Changelog

## Score

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

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 55 → 55 (+0.0)
- Readiness 74 → 74 (+0.0)
- Security 97 → 95 (-2.1)

## Resolved (4)

- Duplicate method signature `write_attribute` in different support modules. Both `ActiveRecordSupport` and `ActiveModelAttributesSupport` expose an instance method with the exact same signature. This suggests either redundant implementation or a lack of clear separation of concerns between ActiveModel and ActiveRecord support layers.
- Inconsistent signature for `reload`. `ActiveRecordSupport` accepts an `options` argument, while `MongoidSupport` does not. This inconsistency forces consumers to handle different argument lists depending on the underlying ORM, violating the principle of least surprise.
- Proliferation of 'enumerize' methods with identical signatures across many types. There are at least 11 different types exposing a method named `enumerize` (or similar) that takes `(name, options)` or `(attr)`. This creates significant confusion about which method is the 'primary' API entry point and which are internal or integration-specific implementations. `Enumerize.Base.ClassMethods.enumerize` is likely the core, but it is not clearly distinguished from the support/integration layer methods.
- Redundant and scattered 'included' hooks. The API exposes multiple distinct types/methods named 'included' across different namespaces (Enumerize, Base, Module, ModuleAttributes, Sequel.Plugins). It is unclear if these are separate extension points or if they represent a single conceptual hook that has been fragmented across the codebase. Specifically, `Enumerize.included` vs `Enumerize.Base.included` suggests a duplication of intent for module inclusion.
