# Changelog

## Score

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

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 86 → 84 (-2.0)
- Maturity 28 → 36 (+8.1)
- Readiness 65 → 65 (+0.0)
- Security 89 → 82 (-6.9)

## Resolved (5)

- Inconsistent constructor naming. 'Connection' uses the standard Ruby 'new' method, while 'Client' uses 'initialize'. While 'initialize' is the internal constructor in Ruby, exposing it as a public API signature alongside 'new' for similar objects is inconsistent.
- Inconsistent naming convention for search operations. 'search' and 'search_for_ids' use snake_case, while 'count' and 'facets' are short verbs/nouns without the 'search_' prefix, despite performing related query operations.
- Inconsistent naming convention in ActiveRecord class methods. Most methods are prefixed with 'sphinx_' and use 'search_' (e.g., 'sphinx_search', 'sphinx_search_for_ids'), but 'sphinx_facets' lacks the 'search_' component, and 'sphinx_search_none' uses 'none' instead of a verb like 'clear' or 'empty'.
- Inconsistent naming convention in AssociationProxy. It uses 'search' and 'search_for_ids', which is consistent with the main ThinkingSphinx module, but inconsistent with the ActiveRecord Base ClassMethods which use 'sphinx_search' and 'sphinx_search_for_ids'. While the context differs, the lack of 'sphinx_' prefix here while present in the main model interface is confusing.
- Redundant methods with ambiguous distinction. 'close' and 'close!' exist. In Ruby, '!' often implies a more forceful or destructive action, but without documentation, it's unclear if they do different things or if one is just an alias. This creates confusion for API users.
