# Changelog

## Score

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

## Lenses

- Code Health 64 → 64 (+0.0)
- Architecture 98 → 98 (+0.0)
- Maturity 51 → 56 (+5.1)
- Readiness 55 → 54 (-1.1)
- Security 77 → 70 (-7.3)
- Performance 80 → 80 (+0.0)

## Resolved (4)

- Ambiguous method signature. The method 'exists?' is overloaded to check for the existence of a specific record by ID (instance method with args) and potentially the existence of any record or a class-level check (instance method with no args). This is confusing because 'exists?' is typically a class method in ORMs, and using it as an instance method with different arities for different semantics is poor API design.
- Inconsistent naming for single-attribute updates. 'update_attribute' (singular) updates one field, while 'update_attributes' (plural) and 'update' update multiple. The singular/plural distinction is clear, but 'update_attribute' bypasses validations while 'update' does not (typically). This behavioral difference combined with the naming makes it easy to misuse. However, the primary inconsistency is the mix of singular/plural naming conventions for similar bulk/single operations.
- Off-boarding risk: anonymized user #1
- Redundant naming for identical operations. Both methods accept a hash of attributes and perform the same save operation. 'update_attributes' is the legacy Rails naming convention, while 'update' is the modern standard. Having both creates confusion about which to use.

## New (5)

- Floating git dependency: activejob
- Floating git dependency: activemodel
- Floating git dependency: activerecord
- Floating git dependency: activesupport
- Off-boarding risk: anonymized user #1
