# Changelog

## Score

- CAI 64 → 73 (+8.7)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 53 → 74 (+21.3)
- Readiness 80 → 80 (+0.0)
- Security 87 → 82 (-5.2)
- Performance 80 → 80 (+0.0)

## Resolved (4)

- Inconsistent naming and pluralization for exclusion operations. `Base` uses `exclude` (singular) and `excludes` (plural), while `View` uses `exclude_field` and `exclude_fields`. The verb form changes between the base class and the view class, and the pluralization strategy is inconsistent (`exclude` vs `exclude_field`).
- Inconsistent pluralization strategy for single vs multiple arguments. While providing both singular and plural methods is a common Ruby pattern (e.g., `include` vs `includes`), having both `include_view` and `include_views` on both `Base` and `View` creates API surface bloat. It is often cleaner to accept a single argument that can be a string or an array, rather than requiring two distinct method names.
- Off-boarding risk: anonymized user #1
- Redundant naming for configuration access. 'configuration' implies retrieval, while 'configure' often implies setting or a builder pattern. Without bodies, it is unclear if these are distinct (getter vs setter/builder) or duplicates. In many Ruby libraries, `configure` is the standard method for accessing/modifying a singleton configuration object.

## New (1)

- Off-boarding risk: anonymized user #1

## Changes since last survey

- 3 commits — 2 feature/other, 1 fixes

## By area

- (root) — 2 commits
- spec/benchmarks — 1 commit

## Notable commits

- fix: [Memoization Fix] fix: memoize field :if/:unless conditions (#608)
- change: docs: add codebase docs and agent guidance (#612)
- change: perf: add a render benchmark suite and run comparison (#622)
