# Changelog

## Score

- CAI 62 → 62 (+0.0)
- 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 51 → 51 (+0.0)
- Readiness 65 → 65 (+0.0)
- Security 100 → 100 (+0.0)
- Performance 85 → 85 (+0.0)

## Resolved (3)

- Confusing overlap between loading and querying state. `add` likely registers an item for loading, while `load` sets the result. However, `loaded_value` and `value_loaded?` are distinct methods that likely interact with the same internal state. The distinction between 'adding' an item to the batch and 'loading' its value is not immediately clear from the names alone, and `loaded_value` vs `value_loaded?` suggests a getter vs predicate pattern that could be simplified.
- Duplicate entry points for creating a batch loader instance. `GraphQL.for` and `GraphQL.initialize` appear to serve the same purpose of instantiating a loader, while `BatchLoader.for` is the primary public API. Having multiple ways to create the same object type within the same namespace is confusing.
- Inconsistent naming for synchronization operations. `BatchLoader` uses a double-underscore prefix (`__sync`) which typically implies private/internal implementation, while `GraphQL` exposes a clean public method (`sync`). If both trigger the same underlying batch execution logic, the naming convention is inconsistent regarding visibility.
