# Changelog

## Score

- CAI 59 → 60 (+0.7)

## Lenses

- Code Health 62 → 62 (+0.0)
- Architecture 99 → 99 (+0.0)
- Maturity 50 → 52 (+1.5)
- Readiness 54 → 54 (+0.0)
- Security 93 → 93 (+0.0)
- Performance 100 → 100 (+0.0)

## Resolved (4)

- Inconsistent naming convention for getter/setter pairs. Most properties in this API surface use the property name directly (e.g., `boldTrait` / `setBoldTrait` implied or direct property access), but this specific pair uses explicit 'set' prefix for the setter and a method call for the getter, deviating from the standard Swift property pattern used elsewhere in the type.
- Inconsistent naming convention for getter/setter pairs. The getter uses the property name `overrideFontName` as the method name, while the setter uses `setOverrideFontName`. This is inconsistent with the `fallbackFontFamily` pair which also uses `setFallbackFontFamily` and `fallbackFontFamily()`, but the inconsistency lies in the fact that `overrideFontName` is a method, not a property, whereas other similar lookups might be properties. More critically, the parameter order in the setter `setOverrideFontName(String, forFontFamily: String...)` is different from the getter `overrideFontName(forFontFamily: String...)` which takes `forFontFamily` first. This is a significant API inconsistency.
- Redundant methods with identical signatures and intent. `objc_setFallbackFontFamily` appears to be a duplicate of `setFallbackFontFamily`, likely left over from Objective-C bridging or code generation artifacts.
- Workflow token permissions not restricted

## New (1)

- Workflow token permissions not restricted (.github/workflows/swift.yml)