# Changelog

## Score

- CAI 65 → 65 (+0.1)

## Lenses

- Code Health 56 → 57 (+0.2)
- Architecture 86 → 86 (+0.0)
- Maturity 74 → 74 (+0.0)
- Readiness 66 → 66 (+0.0)
- Security 76 → 76 (+0.0)
- Domain Modelling 100 → 100 (+0.0)

## Resolved (7)

- Inconsistent naming for identity-related context properties. Some use 'Identity' or 'IsAuthenticated' in different contexts, while others might use 'UserId' or 'UserName'. Specifically, 'Identity' vs 'IsAuthenticated' vs 'UserAgent' naming patterns vary.
- Inconsistent naming for the correlation/request ID concept. Some contexts use 'CorrelationId', others use 'RequestId' or 'TraceId'.
- Inconsistent naming for the user agent header. One interface uses 'UserAgent' while another uses 'UserAgent' but in a different namespace/implementation, suggesting potential duplication or confusion between 'UserAgent' and potentially 'RequestHeader' or similar.
- The Usage section only describes one dotnet new command ('create project') and its output; no guidance is given on how to configure templates, add features like DI or validation, or run the solution locally. (README.md)
- Thin analysable surface across projects
- Typo in generic type parameter name: 'TDatabseContext' instead of 'TDbContext' or 'TContext'. This typo is present in both the interface and the concrete class, but the misspelling itself is an inconsistency in the codebase's naming convention for database contexts.
- dormant codebase — no living knowledge left to concentrate

## New (2)

- There is no guidance on running locally or setting up Docker. (README.md)
- single-maintainer — knowledge-concentration (bus factor) risk

## API surface

- Unchanged — 4 HTTP endpoints