# Changelog

## Score

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

## Lenses

- Code Health 92 → 92 (+0.0)
- Architecture 95 → 96 (+0.7)
- Maturity 69 → 77 (+8.1)
- Readiness 40 → 40 (+0.0)
- Security 77 → 61 (-15.5)

## Resolved (2)

- Inconsistent naming for static-like factory methods. Configuration uses an instance method signature `load(from:)` which implies it might be called on an instance or is a class method, whereas Baseline uses the same pattern. However, looking at `Configuration.init(from: Decoder)` vs `Baseline.init(violations:)`, the loading mechanism is consistent (static/class method pattern disguised as instance method or actual static). The real inconsistency is between `Configuration.load` and `Configuration.init(from: Decoder)`. Usually, if `load` exists, `init(from:)` is for decoding, not file loading. This is actually consistent. Let's look closer. `Baseline` has `load` and `init`. `Configuration` has `load` and `init`. This is consistent.
- Inconsistent parameter signatures for check operations. `SecurityChecker` has two overloads: one taking only files, and another taking files, roots, and excluding. `VisibilityChecker` and `PlistATSCheck` only take roots and excluding, but no explicit file list (implying they discover files themselves or use roots to find them). This creates a confusing API surface where some checkers require you to provide the file list, while others do not, and the `SecurityChecker` has an ambiguous overload that might duplicate the functionality of the other checkers if the file discovery logic is similar.
