# Changelog

## Score

- CAI 60 → 60 (-0.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 75 → 75 (+0.0)
- Architecture 90 → 88 (-1.7)
- Maturity 44 → 44 (+0.0)
- Readiness 67 → 67 (+0.0)
- Security 89 → 89 (+0.0)
- Domain Modelling 100 → 100 (+0.0)
- Performance 75 → 75 (+0.0)

## Resolved (3)

- Ambiguous distinction between `where` and `where!`. In Rails/ActiveRecord conventions, `where!` often implies raising an error on invalid options or strict validation, whereas `where` might be more permissive. However, without documentation, it is unclear if this is a standard Rails convention adoption or an arbitrary API choice. If it strictly mirrors Rails `where` vs `where!` behavior, it is acceptable, but if it's just internal variance, it's confusing. Given the rest of the API is explicit, this feels like a leaky abstraction of Rails internals.
- Both `KeyValue` and `Table` backends expose `translation_for(locale)`. While the signatures are identical, the semantic meaning might differ slightly (one returns a translation record object, the other might return a scope or a specific translation instance). If they return different types, the API is inconsistent. Assuming they both return the translation object/record, this is consistent.
- While signatures match, the implementation domain differs significantly (ActiveRecord Relation vs Sequel Dataset). The `VirtualRow` class in both plugins exposes `build_query`, but the return type and context are ORM-specific. This is less of an inconsistency and more of a necessary divergence, but the naming `build_query` might be misleading if it returns a scope/dataset rather than a raw query string. However, since both are consistent with each other, this is a minor point. A more significant issue is the duplication of `VirtualRow` logic across plugins.

## New (1)

- High CVE: [GHSA redacted] (Gemfile)
