# Changelog

## Score

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

## Lenses

- Code Health 100 → 100 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 44 → 50 (+5.8)
- Readiness 42 → 42 (+0.0)
- Security 67 → 67 (+0.0)

## Resolved (3)

- Ambiguous Method Name `schemaVersion`. The method `schemaVersion` takes a schema and returns a version (int). This is effectively a 'lookup' or 'find' operation. However, the name `schemaVersion` is ambiguous: does it mean 'get the version of this schema' or 'get the schema for this version'? In contrast, `schemaForId` and `schemaForSubjectAndVersion` clearly indicate they return a schema. The naming convention is inconsistent: `schemaVersion` (returns int) vs `schemaFor...` (returns schema).
- Duplicate Registry Interfaces with Inconsistent Return Types and Semantics. There are five distinct registry types (`AsynchronousRegistry`, `Registry`, `BlockingRegistry`, `SynchronousRegistry`, `CachedRegistry`) that expose the exact same business operations (register, schemaId, etc.). Furthermore, the return types are inconsistent: `AsynchronousRegistry` returns `PromiseInterface`, `BlockingRegistry` and `SynchronousRegistry` return `int` (for registration/version) or `AvroSchema` (for lookups), while `Registry` and `CachedRegistry` have no return type specified (likely void or implicit). This forces users to choose between 5 different interfaces for the same logical domain, with confusing naming conventions (Blocking vs Synchronous vs Asynchronous vs Cached).
- Inconsistent Return Type for latestVersion. The `latestVersion` method returns `PromiseInterface` in the async registry, but returns `AvroSchema` in the blocking/synchronous registries. While this is technically correct for async vs sync, it is inconsistent with other methods like `schemaForId` which returns `PromiseInterface` vs `AvroSchema`. More importantly, `latestVersion` returning the full `AvroSchema` is a heavy operation compared to just returning the version number (int), which is what `schemaVersion` does. This suggests a potential semantic confusion between 'getting the latest version number' and 'getting the schema at the latest version'.
