# Changelog

## Score

- CAI 64 → 63 (-0.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 74 → 74 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 52 → 53 (+0.3)
- Readiness 69 → 69 (+0.0)
- Security 80 → 72 (-8.1)

## Resolved (6)

- Documentation: no architecture or design documentation
- Inconsistent API style for setting themes. There is a generic setter `theme=(options)` alongside multiple specific methods for predefined themes. This forces users to learn two different ways to apply a theme (one generic, one specific) when the specific ones could likely be implemented as wrappers around the generic one.
- Inconsistent accessor patterns. `minimum_value` and `maximum_value` are exposed as both Properties (likely getters) and Methods (likely getters or setters). In Ruby, this usually implies a getter method and a property accessor, but having both explicitly listed as distinct members with the same name creates ambiguity about whether one is a setter or if they are duplicates.
- Inconsistent naming and scope for background transparency. `Base` uses a setter property pattern `transparent_background=`, while `Renderer` uses a method `transparent_background` that also takes dimensions. The intent (making background transparent) is similar, but the API surface differs significantly in signature and naming convention (setter vs method).
- Off-boarding risk: anonymized user #1
- Redundant methods with overlapping intent. Both methods appear to perform normalization on the store's data. `norm_data` takes no arguments, while `normalize` takes keywords, suggesting one might be a convenience wrapper or they handle different normalization scopes, but the naming convention is inconsistent (abbreviated vs full word).

## New (1)

- Off-boarding risk: anonymized user #1
