# Changelog

## Score

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

## Lenses

- Code Health 93 → 93 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 48 → 51 (+2.8)
- Readiness 51 → 51 (-0.6)
- Security 80 → 100 (+20.0)
- Domain Modelling 48 → 48 (+0.0)

## Resolved (8)

- Duplicate intent between `Converter` and `Serializer`. Both provide a `toJSON` method that converts an entity/domain object to JSON. The distinction between 'Converter' and 'Serializer' is not clear from the signatures alone, and having two separate types with the same primary operation (`toJSON`) and inverse operation (`fromJSON`/`JSONToProps`) suggests a lack of clear separation of concerns or redundant abstraction.
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- Inconsistent parameter naming for the same logical operation across repository variants. `RepositoryCore` uses `entityIdentifier`, while `Repository`, `NonNullableRepository`, and `NullableRepository` use `entityId`. This forces consumers to remember different argument names for identical functionality depending on which repository interface they are using.
- Inconsistent return type for `delete`. `RepositoryCore.delete` and the specialized repositories return `void` (explicitly or implicitly), but `RepositoryCore.deleteById` exists while `RepositoryCore.delete` takes an entity. More importantly, `RepositoryCore.delete` has no return type annotation in the signature provided, while others explicitly say `: void`. This is a minor documentation inconsistency, but the bigger issue is the duplication of `delete` across all repository variants with identical signatures.
- Medium CVE: [GHSA redacted] (yarn.lock)
- Redundant method signatures across repository variants. `getAll()` is present in all four repository types with identical signatures. Since `NonNullableRepository` and `NullableRepository` appear to be specialized variants of `Repository` (which itself is likely related to `RepositoryCore`), having `getAll` duplicated in every class without distinct behavior or return type differences creates unnecessary API surface duplication. If these are meant to be distinct interfaces, the naming convention implies a hierarchy that isn't reflected in the method set (e.g., `RepositoryCore` has `getLastSaved` but others don't, yet `getAll` is everywhere).

## New (5)

- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (registry.npmjs.org unreachable)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- Pass-through layer (src/repository/NullableRepository.ts)
