# Changelog

## Score

- CAI 39 → 38 (-1.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 43 → 38 (-4.3)
- Readiness 48 → 51 (+2.7)
- Security 23 → 20 (-2.9)
- Performance 70 → 77 (+7.4)

## Resolved (6)

- Inconsistent test method naming conventions within the same test class. Some tests use 'Is...' (IsNullOrWhiteSpace, IsLowerThan), some use 'Not...' (NotContains), and one uses 'AreNotEqualsLen'. This lack of uniformity in how test behaviors are named (predicate vs action vs result) makes the test suite harder to scan and understand.
- Inconsistent test method naming for equality/inequality assertions. Some tests use 'Require...AreNotEquals' (e.g., RequireTwoFloatsAreNotEquals) while others use 'RequiresDatesAreEquals' or 'RequiresDatesAreNotEquals'. The mix of 'Require' vs 'Requires' and 'AreEquals' vs 'AreNotEquals' (vs 'IsNotEqual') indicates a lack of consistent naming convention for test cases involving equality checks.
- Inconsistent test naming style across different test classes. One test uses a descriptive sentence structure ('ShouldNotUpdateACustomerWithoutAnEmail') while others use short predicate names ('AreNotEquals', 'AreEquals'). This suggests a lack of global test naming convention.
- Inconsistent verb usage for equality checks. The codebase uses 'Are' (plural) for equality comparisons (AreEquals, AreNotEquals) but switches to 'Is' (singular) for inequality/non-equality checks in other contexts (e.g., IsNotNull, IsLowerThan). While 'Are' is grammatically correct for comparing two values, the inconsistency with the broader 'Is...' predicate convention used for single-value validations (IsNull, IsEmpty, IsBetween) creates a fragmented API vocabulary.
- Low XML-doc coverage: Flunt.Samples (Flunt.Samples/Flunt.Samples.csproj)
- XML-doc coverage: Flunt (Flunt/Flunt.csproj)

## Architecture

- Unchanged — 1 containers · 1 contexts · 0 edges
