# Changelog

## Score

- CAI 38 → 38 (+0.0)
- Rubric changed (rubric-2026.08.18 → rubric-2026.08.19) — scores are not directly comparable.

## Lenses

- Code Health 73 → 73 (+0.0)
- Architecture 84 → 84 (+0.0)
- Maturity 56 → 56 (+0.0)
- Readiness 32 → 32 (+0.1)
- Security 25 → 25 (+0.0)
- Performance 79 → 79 (+0.0)

## Resolved (5)

- Inconsistent naming for the 'exists' check method. IOrderService and IProductService use 'IsExists', while ICustomerService uses 'IsExistsForUpdate'. This suggests a split in terminology for the same or similar validation logic.
- Inconsistent naming for the 'update' method. IOrderService uses 'Update', IProductService uses 'Update', ICustomerService uses 'Update'. This is consistent. However, IOrderService also has 'IsExistsForUpdate' while IProductService has 'IsExists'. This is the main inconsistency.
- Medium CVE: Azure.Identity 1.6.0
- Medium CVE: Azure.Identity 1.6.0
- The README begins outlining REST API components ('Controllers', 'Models/DTOs') before being clipped mid-sentence at the Models/DTOs line, so further sections like Getting Started, Project Features, Usage, Authors, Contributing, and License are present in the outline but not shown. (README.md)

## New (7)

- Inconsistent naming for creation and retrieval operations: some services use 'Create' while others might use 'Add' or 'Insert'; similarly, retrieval uses 'Get', 'GetOrders', 'GetProducts', 'GetCustomer' inconsistently.
- Inconsistent naming for order details: some use 'OrderDetails' as a collection or object, while others use 'OrderDetail' or 'OrderDetailsViewModel'.
- Inconsistent naming for product attributes: some are in 'Business' namespace as ViewModels, while others are in 'General' namespace as Entities.
- Inconsistent naming for the same or similar business logic: some services use 'IsExists' while others use 'IsExistsForUpdate' for checking existence, and some implementations use 'IsExists' while others use 'IsExistsForUpdate'.
- Inconsistent naming for update operations: some services use 'Update' while the base repository also uses 'Update', but the parameter types and signatures vary significantly, suggesting different underlying behaviors.
- Medium CVE: Azure.Identity 1.6.0
- Medium CVE: Azure.Identity 1.6.0

## API surface

- 0 added · 20 removed (a removed endpoint is potentially breaking)

## Removed endpoints (breaking) (20)

- DELETE /api/customer/{id}
- DELETE /api/order/{id}
- DELETE /api/product/{id}
- GET /api/customer
- GET /api/customer/paginated
- GET /api/customer/{id}
- GET /api/order
- GET /api/order/paginated
- GET /api/order/{orderId}
- GET /api/product
- GET /api/product/paginated
- GET /api/product/pricecheck/{productId}
- GET /api/product/{id}
- GET /runbenchmarks
- POST /api/customer
- POST /api/order
- POST /api/product
- PUT /api/customer
- PUT /api/order
- PUT /api/product

## Architecture

- Unchanged — 1 containers · 0 contexts · 0 edges