# Changelog

## Score

- CAI 42 → 42 (+0.0)

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 45 → 45 (+0.0)
- Readiness 48 → 48 (+0.0)
- Security 27 → 27 (+0.0)
- Performance 70 → 70 (+0.0)

## Resolved (4)

- Build action pinned to a mutable branch
- Inconsistent naming for greater-than-or-equal vs greater-than. The codebase uses 'IsGreaterOrEqualsThan' and 'IsGreaterThan', which is consistent, but there is also 'IsLowerOrEqualsThan' and 'IsLowerThan'. However, for equality, it uses 'AreEquals' instead of 'IsEqual' or 'IsEquals'. This creates a pattern mismatch: comparisons use 'Are' + plural, while state checks use 'Is' + singular.
- Inconsistent use of 'Are' vs 'Is' for equality checks. Some methods use 'AreEquals' while others use 'IsNotNull', 'IsLowerThan', etc. The plural 'Are' is used for comparison methods, but singular 'Is' is used for state checks. This is a minor inconsistency in verb form (plural vs singular) for similar comparison operations.
- Inconsistent use of 'Is' vs 'Are' for range checks. 'IsBetween' and 'IsNotBetween' use 'Is', which is consistent with other 'Is...' methods, but the equality checks use 'Are'. This creates a split where range checks use singular 'Is' while equality checks use plural 'Are'.

## New (5)

- Inconsistent naming for less-than comparisons. Some methods use 'IsLowerThan' while others use 'IsLessThan' (if present) or 'IsLowerOrEqualsThan' vs 'IsGreaterOrEqualsThan'. The term 'Lower' is used instead of 'Less', which is less common in C# for numeric comparisons (typically 'Less' or 'Greater').
- Inconsistent naming for null checks. Some methods use 'IsNull'/'IsNotNull' while others use 'IsNotBetween' or 'IsNotMinValue'. The null checks are consistent, but the non-null checks are 'IsNotNull' while other validations use 'IsNot...'. This is a minor inconsistency in prefix usage (IsNotNull vs IsNot...).
- Inconsistent use of 'Are' vs 'Require'/'Is' for equality checks. Some methods use 'AreEquals' (plural, present tense) while others use 'RequireTwo...AreNotEquals' or 'Requires...AreEquals' in tests, and 'IsNotBetween'/'IsGreaterOrEqualsThan' (singular, state-based) for other comparisons. The test suite mixes 'Are/Not' with 'Require/Is' prefixes.
- Inconsistent use of 'Between' vs 'NotBetween'. While this is technically correct (negation), the test methods use 'Requires...IsNotBetween' or 'Requires...IsBetween'. The inconsistency is in the test layer: some tests use 'Requires...IsNotBetween' while others use 'Requires...IsBetween'.
- Inconsistent use of 'Greater' vs 'Lower' vs 'Less'. The codebase uses 'Greater' for > and 'Lower' for <. However, 'Lower' is non-standard for numeric comparisons (usually 'Less'). Additionally, 'IsLowerOrEqualsThan' is used, but 'IsGreaterOrEqualsThan' is used, showing a mix of 'Greater' and 'Lower' which are antonyms but 'Lower' is an unusual choice for '<' in this context compared to 'Less'.

## Architecture

- Unchanged — 1 containers · 1 contexts · 0 edges