# Changelog

> **This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.**

## Score

- CAI 34 → 36 (+1.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 69 → 69 (+0.0)
- Architecture 86 → 86 (+0.0)
- Maturity 45 → 50 (+5.7)
- Readiness 36 → 40 (+3.8)
- Security 19 → 21 (+2.0)
- Accessibility 57 → 46 (-10.6)
- Performance 100 → 100 (+0.0)

## Resolved (8)

- Documentation: no usage examples (README.md)
- End-of-life runtime: .NET net7.0 (Project.UnitTest/Project.UnitTest.csproj)
- The method 'IsExistsForUpdate' is used to check for existence with specific criteria. While consistent across the service and repository layers, the name is verbose and grammatically awkward ('Is Exists'). Furthermore, comparing 'IsExists' (generic) and 'IsExistsForUpdate' (specific) shows a naming pattern where the generic check is 'IsExists' and the specific is 'IsExistsForUpdate'. This is internally consistent but stylistically poor. More critically, there is a potential confusion with 'IsExists<Tvalue>' in the repository which takes different parameters. However, the primary inconsistency is the use of 'IsExists' vs standard 'Exists'.
- The method name 'IsExists' is grammatically incorrect and non-standard for a predicate returning a boolean. The standard C# convention is 'Exists' or 'ExistsAsync'. While 'IsExists' appears in both the interface and implementation, it represents a deviation from the common 'Exists' pattern used in most .NET libraries (e.g., List.Exists, String.IsNullOrEmpty). However, since it is consistent between interface and implementation, it is a style issue rather than an inconsistency between symbols. A more significant inconsistency is found in the naming of the update-check variant.
- Vulnerable: AutoMapper
- XML-doc coverage: Project.Core (Project.Core/Project.Core.csproj)
- XML-doc coverage: Project.Infrastructure (Project.Infrastructure/Project.Infrastructure.csproj)
- XML-doc coverage: Project.UI (Project.UI/Project.UI.csproj)

## New (9)

- End-of-life runtime: .NET net7.0 (Project.Core/Project.Core.csproj)
- End-of-life runtime: .NET net7.0 (Project.Infrastructure/Project.Infrastructure.csproj)
- End-of-life runtime: .NET net7.0 (Project.UI/Project.UI.csproj)
- End-of-life runtime: .NET net7.0 (Project.UnitTest/Project.UnitTest.csproj)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- redundant comment (Project.Core/Services/ProductService.cs)

## API surface

- Unchanged — 1 HTTP endpoints

## Architecture

- Unchanged — 2 containers · 0 contexts · 0 edges
