# Changelog

## Score

- CAI 64 → 66 (+2.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 75 → 75 (+0.0)
- Architecture 98 → 98 (+0.0)
- Maturity 58 → 62 (+4.4)
- Readiness 62 → 62 (+0.0)
- Security 70 → 70 (+0.0)

## Resolved (5)

- Ambiguous naming for validation methods. `validate()` and `validate?()` likely perform the same or very similar validation logic, with the `?` suffix potentially indicating a boolean return or a side-effect-free check, but the distinction is unclear from signatures alone.
- Overlapping retrieval methods for commands. `commands()`, `deep_commands()`, `public_commands()`, and `visible_commands()` all retrieve collections of commands but with different filtering/scoping logic. While distinct, the naming convention is inconsistent (some imply depth, some visibility, some access level) without a clear hierarchy or base method.
- Proliferation of filtered environment variable lists. Same pattern as flags and commands, leading to API bloat and potential confusion about which list to use.
- Proliferation of filtered flag lists. Similar to commands, there are multiple methods returning subsets of flags with unclear distinctions between 'public', 'visible', and 'default'.
- Redundant accessor methods for boolean settings. The class provides both a generic `enabled?(feature)` method and specific `enable_<feature>()` methods for each boolean setting. This duplicates intent and API surface.
