# Changelog

## Score

- CAI 56 → 55 (-0.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 89 → 89 (+0.0)
- Maturity 46 → 46 (+0.0)
- Readiness 55 → 55 (+0.0)
- Security 70 → 67 (-2.9)

## Resolved (3)

- Ambiguous naming convention: In many Ruby libraries, methods ending in `?` are predicates returning booleans, while methods without the suffix may return the matched object or nil. However, having both `match` and `match?` on the same object often implies one is a deprecated alias or a specific variant (e.g., regex vs string). Without distinct return type documentation, this creates confusion about which method to call for a simple boolean check versus a match extraction.
- Duplicate intent: Both the module-level `Whois` class and the `Client` class expose a `lookup` method with identical signatures. It is unclear whether `Whois.lookup` is a convenience wrapper around `Client.new.lookup` or a separate implementation, leading to confusion about which entry point to use.
- Potential semantic overlap: `available?` and `registered?` are likely inverse operations (if a domain is registered, it is not available, and vice versa). However, exposing both as top-level convenience methods can be confusing. More critically, if `available?` is implemented as `!registered?`, having both adds unnecessary API surface. If they have different underlying logic (e.g., checking against different sources), this should be explicit, but typically these are two sides of the same coin.
