# Changelog

## Score

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

## Lenses

- Code Health 98 → 98 (+0.0)
- Architecture 97 → 96 (-1.1)
- Maturity 68 → 73 (+5.0)
- Readiness 46 → 46 (+0.0)
- Security 100 → 100 (+0.0)
- Accessibility 47 → 47 (+0.0)

## Resolved (4)

- Inconsistent deserialization API. `RedisClient` provides specific overloads for generic decoding (`as:`) and JSON decoding (`asJSON:`), but the underlying `RedisCommand` only exposes a raw `RESPValue` getter. This forces the client layer to handle all decoding logic, making it difficult to compose commands or inspect raw data before decoding.
- Inconsistent naming and parameter structure for scanning operations. `scanKeys` does not take a `RedisKey` argument (it scans the whole DB), while `scanHash/Set/SortedSetValues` do. However, the method names are not parallel (`scanKeys` vs `scan...Values`), and the underlying `RedisCommand` uses a generic `scan` that doesn't reflect the specific data type scanning in the client layer.
- Inconsistent parameter types and overloads for unsubscription. `unsubscribe` has an overload taking a single `RedisChannelName`, while `punsubscribe` takes a single `String`. Additionally, there are no-argument overloads for both, but the typed overloads are inconsistent in their input types.
- Inconsistent typing for pattern subscription channels. Regular subscriptions use the strongly-typed `RedisChannelName`, while pattern subscriptions (`psubscribe`) accept raw `String`. This forces users to convert types or bypass type safety for pattern matching.
