# Changelog

## Score

- CAI 71 → 71 (+0.3)
- Rubric changed (rubric-2026.09.9 → rubric-2026.09.18) — scores are not directly comparable.

## Lenses

- Code Health 99 → 99 (+0.0)
- Architecture 100 → 98 (-2.2)
- Maturity 57 → 57 (+0.0)
- Readiness 64 → 69 (+4.9)
- Security 100 → 100 (+0.0)

## New (5)

- Inconsistent naming for error enrichment. 'Error.msg' suggests setting a message, while 'Context.context' and 'Context.with_context' suggest adding context. In the Anyhow library, 'context' and 'with_context' are the standard methods for adding context. 'Error.msg' is non-standard and potentially confusing as it might imply overwriting or setting a primary message rather than adding context. It breaks the 'context' naming convention used elsewhere.
- Internal dispatch methods with confusingly similar names. '__dispatch_ensure' is a private/internal method (indicated by double underscore) but is exposed in the public API surface. The types 'BothDebug' and 'NotBothDebug' suggest conditional compilation or feature flags, but exposing these internal dispatch methods directly is inconsistent with typical Rust/Anyhow design where such internals are hidden. It creates noise and potential for misuse.
- Inverted test pyramid
- Low cohesion: Error (LCOM4 4) (src/lib.rs)
- Redundant/Confusing naming for similar boxing operations. 'into_boxed_dyn_error' is the standard idiomatic name for consuming an error into a boxed trait object. 'reallocate_into_boxed_dyn_error_without_backtrace' is extremely verbose, uses 'reallocate' (implies memory management detail not usually exposed in high-level APIs), and explicitly mentions 'without_backtrace' which is a specific behavior variant. It is unclear if these are distinct performance optimizations or just poor naming for the same concept.

## Changes since last survey

- 1 commits — 1 feature/other, 0 fixes

## By area

- tests/ui — 1 commit

## Notable commits

- change: Update ui test suite to nightly-2026-09-29