# Changelog

## Score

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

## Lenses

- Code Health 59 → 59 (+0.0)
- Architecture 97 → 97 (+0.0)
- Maturity 41 → 41 (+0.0)
- Readiness 80 → 80 (+0.0)
- Security 95 → 92 (-3.2)
- Domain Modelling 100 → 100 (+0.0)

## Resolved (3)

- Duplicate method definition across different modules. Both `Impressionable` and `IsImpressionable` expose a class method `is_impressionable` with identical signatures. This suggests redundant module inclusion or copy-paste errors in the API surface.
- Naming collision and ambiguity. `ImpressionistController` has an instance method `impressionist` that takes arguments, while `Impressionable` (likely a model concern) has a class method `impressionist` that takes options. While the contexts differ (Controller vs Model), the shared name `impressionist` for both configuration (class method) and action (instance method) is confusing. Furthermore, `ImpressionistController` is a controller class, but the methods are defined in `ClassMethods` and `InstanceMethods` blocks, suggesting a mixin pattern, yet the naming implies a direct controller action.
- Redundant method names with identical intent. `impressionist_counter_caching?` and `counter_caching?` appear to check the same state. The prefix `impressionist_` is redundant given the context of the `Impressionable` module.

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
