# Changelog

## Score

- CAI 64 → 64 (+0.3)
- Rubric changed (rubric-2026.09.11 → rubric-2026.09.18) — scores are not directly comparable.

## Lenses

- Code Health 97 → 97 (-0.2)
- Architecture 100 → 100 (+0.0)
- Maturity 53 → 53 (+0.0)
- Readiness 48 → 51 (+2.6)
- Security 97 → 97 (+0.0)

## Resolved (2)

- Documentation: no architecture or design documentation (README.md)
- Off-boarding risk: anonymized user #1

## New (10)

- Coverage not measured — Swift suite
- Duplicated block (16 lines × 2) (Sources/KeyboardShortcuts/Shortcut.swift)
- Duplicated block (38 lines × 2) (Sources/KeyboardShortcuts/Shortcut.swift)
- MethodTooLong: SpecialKey.appKitMenuItemKeyEquivalent (Sources/KeyboardShortcuts/Shortcut.swift)
- MethodTooLong: SpecialKey.presentableDescription (Sources/KeyboardShortcuts/Shortcut.swift)
- MethodTooLong: SpecialKey.swiftUIKeyEquivalent (Sources/KeyboardShortcuts/Shortcut.swift)
- Off-boarding risk: anonymized user #1
- Redundant overloads for single vs. collection input. Same issue as `disable` and `enable`.
- Redundant overloads for single vs. collection input. Same issue as `disable`.
- Redundant overloads for single vs. collection input. Swift APIs typically prefer a single collection-based overload (e.g., disable([Name])) which handles both single and multiple items via array literals or single-element arrays, or use a variadic parameter. Having both explicit overloads creates unnecessary API surface and potential ambiguity.