# Changelog

## Score

- CAI 62 → 61 (-0.3)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 61 → 61 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 55 → 58 (+3.0)
- Readiness 71 → 71 (+0.2)
- Security 72 → 59 (-12.6)
- Domain Modelling 100 → 100 (+0.0)
- Performance 95 → 95 (+0.0)

## Resolved (6)

- Confusingly similar names: `at` and `at_version` appear to do the same thing (retrieving a model state at a specific point in time/version). The distinction between passing `time` vs `version` is implicit in the name `at_version` but explicit in `at`, leading to potential confusion about which method to use for version-based lookups.
- Duplicate intent with inconsistent naming: The bang versions (`at!`, `at_version!`) mirror the non-bang versions but with the same signature inconsistency (`at` takes time/version, `at_version` takes version). This doubles the confusion of the non-bang methods.
- Duplicate intent: Both instance methods perform the same logical operation (clearing/resetting log data) on the model instance. While one is in a module and one in the main module, exposing both on the same class (via inclusion) creates ambiguity on which should be used or if they behave identically.
- Off-boarding risk: anonymized user #1
- Outdated: activerecord
- Outdated: railties

## New (1)

- Off-boarding risk: anonymized user #1
