# Changelog

## Score

- CAI 52 → 52 (-0.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 89 → 89 (-0.0)
- Architecture 85 → 85 (+0.0)
- Maturity 64 → 70 (+6.5)
- Readiness 53 → 53 (+0.0)
- Security 43 → 41 (-2.4)
- Domain Modelling 67 → 71 (+3.4)
- Event-Driven 80 → 77 (-2.9)
- Performance 60 → 60 (-0.5)

## Resolved (47)

- Duplicate event types with identical structure and intent. Both events carry a FileId and BucketName, suggesting they represent the same domain concept (a request to delete a file/photo) but are split into two distinct types without clear differentiation in the signature.
- Inconsistent event naming and lifecycle representation. `CreateAdoptionChat` appears to be a command/intent (contains AdopterName, PetNickName), while `AdoptionChatCreated` and `AdoptionChatCreationFailed` are outcomes. However, `AdoptionChatCreated` lacks the `ChatId` in its signature (only has CorrelationId, ChatId, PetId), whereas `CreateAdoptionChat` does not have a ChatId. More critically, `AdoptionChatCreated` has a `ChatId` property, but `CreateAdoptionChat` does not, which is correct for command vs event, but the naming convention mixes 'Action' (Create) with 'State Change' (Created). A more consistent pattern would be `AdoptionChatRequested` (command) vs `AdoptionChatCreated` (event). The current mix of `Create...` (command-like) and `AdoptionChat...` (event-like) is slightly inconsistent with other pairs like `ReservePet`/`PetReserved`.
- XML-doc coverage: Account.Domain (Solution/Account/Account.Domain/Account.Domain.csproj)
- XML-doc coverage: Account.Handlers (Solution/Account/Application/Account.Handlers/Account.Handlers.csproj)
- XML-doc coverage: Account.Hosts.Consumers (Solution/Account/Hosts/Account.Hosts.Consumers/Account.Hosts.Consumers.csproj)
- XML-doc coverage: Account.Hosts.DI (Solution/Account/Hosts/Account.Hosts.DI/Account.Hosts.DI.csproj)
- XML-doc coverage: Account.Hosts.Endpoints (Solution/Account/Hosts/Account.Hosts.Endpoints/Account.Hosts.Endpoints.csproj)
- XML-doc coverage: Account.Infrastructure (Solution/Account/Account.Infrastructure/Account.Infrastructure.csproj)
- XML-doc coverage: Account.Services (Solution/Account/Application/Account.Services/Account.Services.csproj)
- XML-doc coverage: ApiGateway (Solution/ApiGateway/ApiGateway/ApiGateway.csproj)
- XML-doc coverage: Auth.Application (Solution/Auth/Auth.Application/Auth.Application.csproj)
- XML-doc coverage: Auth.Contracts (Solution/Auth/Auth.Contracts/Auth.Contracts.csproj)
- XML-doc coverage: Auth.Core (Solution/Auth/Auth.Core/Auth.Core.csproj)
- XML-doc coverage: Auth.Endpoints (Solution/Auth/Hosts/Auth.Endpoints/Auth.Endpoints.csproj)
- XML-doc coverage: Auth.Infrastructure (Solution/Auth/Auth.Infrastructure/Auth.Infrastructure.csproj)
- XML-doc coverage: Conversation.Domain (Solution/Conversation/Conversation.Domain/Conversation.Domain.csproj)
- XML-doc coverage: Conversation.Handlers (Solution/Conversation/Application/Conversation.Handlers/Conversation.Handlers.csproj)
- XML-doc coverage: Conversation.Hosts.Consumers (Solution/Conversation/Hosts/Conversation.Hosts.Consumers/Conversation.Hosts.Consumers.csproj)
- XML-doc coverage: Conversation.Hosts.DI (Solution/Conversation/Hosts/Conversation.Hosts.DI/Conversation.Hosts.DI.csproj)
- XML-doc coverage: Conversation.Hosts.Endpoints (Solution/Conversation/Hosts/Conversation.Hosts.Endpoints/Conversation.Hosts.Endpoints.csproj)
- …and 27 more

## New (5)

- doc comments repeat the names (Shared/PetFamily.SharedKernel.WebApi/Extensions/OpenTelemetryExtensions.cs)
- doc comments repeat the names (Solution/Auth/Auth.Application/Services/IAuthService.cs)
- doc comments repeat the names (Solution/Auth/Auth.Infrastructure/Services/Keycloak/IKeycloakAuthorizationClient.cs)
- doc comments repeat the names (Solution/Notification/Notification.Infrastructure/BackgroundJobs/NotificationLogCleanupService.cs)
- doc comments repeat the names (Solution/VolunteerManagement/VolunteerManagement.Infrastructure/Common/Contexts/VolunteerManagementDbContextFactory.cs)

## API surface

- Unchanged — 64 HTTP endpoints

## Architecture

- Unchanged — 16 containers · 4 contexts · 3 edges
