# Changelog

## Score

- CAI 45 → 45 (+0.3)
- Rubric changed (rubric-2026.08.17 → rubric-2026.08.18) — scores are not directly comparable.

## Lenses

- Code Health 56 → 56 (+0.0)
- Architecture 89 → 89 (+0.0)
- Maturity 42 → 43 (+1.0)
- Readiness 34 → 34 (+0.0)
- Security 80 → 80 (+0.0)

## Resolved (2)

- Coverage not measured — analyzer environment
- Monorepo: only 1 of 2 solutions was scored

## New (3)

- Coverage not measured — analyzer environment
- Inconsistent naming for ViewModel/Context classes. The codebase uses 'Context' as a suffix for view-models (e.g., MainWindowContext, WelcomeDataContext), but the base class or interface naming is not explicitly shown, however, the pattern is consistent within the namespace. However, looking at the list, we see 'MainWindowContext' and 'WelcomeDataContext'. This is actually consistent. Let's look for actual inconsistencies.
- Inconsistent naming for interop/Windows API wrappers. Some members are static methods on the 'ReparsePoint' class (e.g., Create, Move, LookupPrivilegeValue), while others are nested types or separate classes. More importantly, the class 'ReparsePoint' is used for file system operations (symlinks), but the name 'ReparsePoint' is a specific Windows API structure/constant, not a general utility class name. This is a conceptual inconsistency where the class name reflects a specific API detail rather than the domain concept (e.g., 'SymlinkManager' or 'FileSystemLinker').

## Architecture

- Unchanged — 1 containers · 0 contexts · 0 edges