# Changelog

## Score

- CAI 51 → 52 (+1.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 50 → 50 (+0.8)
- Architecture 87 → 86 (-1.4)
- Maturity 47 → 73 (+26.1)
- Readiness 50 → 46 (-3.5)
- Security 74 → 70 (-3.8)
- Accessibility 49 → 51 (+2.1)
- Performance 100 → 100 (+0.0)

## Resolved (8)

- Ambiguous caching API. `cache_store` suggests returning the store object (e.g., Redis, Memcached), while `cache` suggests a key-value access method. However, without seeing the return types, it's unclear if `cache` is a wrapper around `cache_store`. This is a minor inconsistency in naming convention (store vs. access).
- Ambiguous distinction between configuration mutation and retrieval. While `configure` implies setting and `configuration` implies getting, the lack of a clear `config` or `settings` alias for reading makes the API feel split. More critically, `InertiaRails.cache_store()` and `InertiaRails.cache()` suggest two different ways to access caching, but their relationship (is one a wrapper for the other? are they distinct stores?) is unclear from signatures alone, risking duplication of intent.
- Confusing overlap between `merge` and `deep_merge`. `InertiaRails.merge` and `InertiaRails.deep_merge` are both present. It is unclear if `deep_merge` is a specialized version of `merge` or if they are distinct operations. Additionally, `PropMergeable` is a module/class that seems to implement the logic for these, but its presence in the public API alongside the factory methods is redundant.
- Documentation: no project overview (README.md)
- Duplicate intent for 'defer' evaluation. `InertiaRails.defer()` is the factory, `DeferProp` is the class. This pattern repeats for `lazy`, `once`, `optional`, `merge`, `cached`, and `scroll`. The public API surface exposes both the convenience methods and the underlying prop classes, leading to a fragmented API where users don't know which to use.
- Duplicate intent for 'once' evaluation. Similar to `lazy`, `InertiaRails.once()` is likely a factory for `OnceProp`. Exposing both the module method and the class constructor is inconsistent with typical Ruby library design where the module method is the public API.
- Duplicate intent for lazy evaluation. `InertiaRails.lazy` appears to be a top-level helper for creating lazy props, while `LazyProp` is the underlying class. If `InertiaRails.lazy` simply returns a `LazyProp` instance, exposing both the factory method and the class constructor in the public API surface creates redundancy for the user. Users might wonder if they should use `InertiaRails.lazy` or `LazyProp.new`.
- Off-boarding risk: anonymized user #1

## New (1)

- Off-boarding risk: anonymized user #1

## Changes since last survey

- 1 commits — 1 feature/other, 0 fixes

## By area

- (root) — 1 commit

## Notable commits

- change: Test Rails 8.1 against json 3 (#440)
