# Changelog

## Score

- CAI 42 → 44 (+1.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 60 → 60 (+0.0)
- Architecture 84 → 84 (+0.0)
- Maturity 47 → 53 (+5.4)
- Readiness 47 → 51 (+3.8)
- Security 33 → 33 (+0.8)
- Accessibility 47 → 47 (+0.6)
- Performance 100 → 100 (+0.0)

## Resolved (3)

- End-of-life runtime: .NET net7.0 (WebApp/WebApp.csproj)
- The interface `IRepository<T>` defines a method `Delete` taking an expression, while the implementation `EfRepository<T>` also defines `Delete` taking an expression. However, `EfRepository<T>` *also* defines `DeleteAsync(object)` and `DeleteAsync(object, T)` is not present but `UpdateAsync` is. More critically, looking at `IRepository<T>`, it has `Delete(Expression)` and `Update(T)`. `EfRepository<T>` has `Delete(Expression)`, `DeleteAsync(object)`, `DeleteAsync(Expression)`, `Update(T)`, `UpdateAsync(object, T)`. The naming is consistent between interface and implementation for the primary operations. However, there is a potential inconsistency in the `IRepositoryService<T>` vs `IRepository<T>` naming for similar concepts. `IRepository<T>` has `Get`, `GetMany`, `AddAsync`, `Update`, `Delete`. `IRepositoryService<T>` has `GetAsync`, `GetByIdAsync`, `UpsertAsync`, `DeleteAsync`. The service layer uses `Async` suffixes for all async methods, while the repository interface mixes `Async` (AddAsync) and non-async names for async operations (Get, GetMany, Delete, Update). This is a common pattern but technically an inconsistency in verb usage across the same conceptual layer of data access.
- Vulnerable: AutoMapper

## New (4)

- End-of-life runtime: .NET net7.0 (Application/Application.csproj)
- End-of-life runtime: .NET net7.0 (Domain/Domain.csproj)
- End-of-life runtime: .NET net7.0 (Infrastructure/Infrastructure.csproj)
- End-of-life runtime: .NET net7.0 (WebApp/WebApp.csproj)

## Architecture

- Unchanged — 2 containers · 1 contexts · 0 edges
