# Changelog

## Score

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

## Lenses

- Code Health 66 → 66 (+0.0)
- Architecture 97 → 97 (+0.0)
- Maturity 43 → 43 (+0.0)
- Readiness 35 → 35 (+0.0)
- Security 100 → 100 (+0.0)

## Resolved (4)

- Inconsistent naming for cache retrieval methods. Some use 'Lookup' while others use 'Get'. This suggests two different patterns for the same operation.
- Inconsistent naming for module information objects. One is named with 'Module' and 'Info', the other with 'Pe' (Portable Executable) and 'Dependency'. This suggests a lack of uniformity in how module/dependency metadata is named across the codebase.
- Inconsistent property naming for file paths. Some use 'Filepath' (camelCase) while others might use 'FilePath' (PascalCase) or 'ModuleFilePath'. The mix of 'Filepath' and 'FilePath' for the same concept is an inconsistency.
- The phnt README is a short 'This collection of Native API header files has been maintained since 2009...' note with no build instructions for the headers. (third_party/phnt/README.md)

## New (3)

- Inconsistent naming for dependency-related concepts: 'PeDependencyItem' vs 'PeDependencies'. One is singular, the other plural, suggesting the same or related concepts are named differently.
- Inconsistent naming for file path properties: some use 'Filepath' (camelCase) while others use 'ModuleFilePath' (PascalCase) or 'ModuleName' (different concept). Specifically, 'Filepath' vs 'ModuleFilePath' represents a naming inconsistency for the same or similar concept (file path).
- The phnt header collection README is a short 'This collection of Native API header files has been maintained since 2009...' entry with no usage example and only PHNT_VERSION defines; it does not explain how to use the headers or what symbols are exposed. (third_party/phnt/README.md)

## Architecture

- Unchanged — 1 containers · 0 contexts · 0 edges