# Changelog

## Score

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

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 43 → 54 (+11.5)
- Readiness 51 → 51 (+0.0)
- Security 94 → 90 (-3.9)
- Domain Modelling 100 → 100 (+0.0)
- Performance 80 → 80 (+0.0)

## Resolved (4)

- Ambiguous distinction between `auto_include` and `auto_include!`. In Ruby, the `!` suffix often implies a mutating or more aggressive action, but without documentation, it is unclear if these methods have different side effects or if one is just an alias. If they perform the same logical operation (setting auto_include), one is redundant.
- Orphaned file (lib/goldiloader/active_record_patches.rb)
- Orphaned files with no living knowledge
- Redundant getter methods. In Ruby, `enabled?` is the standard convention for boolean predicates, while `enabled` is typically used for the getter/setter pair (`enabled`/`enabled=`). Having both `enabled?` and `enabled` as separate methods creates confusion about which one to use for reading the state, especially since `enabled=` exists.

## Changes since last survey

- 7 commits — 7 feature/other, 0 fixes

## By area

- (root) — 7 commits

## Notable commits

- change: Auto eager load associations below includes that Rails joins (31 → 2 queries) (#178)
- change: Auto eager load associations of models loaded with load_async (11 → 2 queries) (#179)
- change: Document goldiload cache names that depend on method arguments (#180)
- change: Document uninstalling the gem with records cached by Marshal (#181)
- change: Forward arguments without allocating in CollectionAssociationPatch (#175)
- change: Keep belongs_to optional in the test app with combustion 1.6+ (#176)
- change: Release version 6.0.1 (#177)

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
