# Changelog

## Score

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

## Lenses

- Code Health 75 → 75 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 56 → 56 (+0.0)
- Readiness 71 → 71 (+0.1)
- Security 80 → 71 (-9.3)

## Resolved (4)

- Ambiguous duplication: It is unclear if `config()` retrieves the current configuration object while `configure()` mutates it, or if they are redundant aliases for the same operation. In consistent APIs, getter/setter pairs are usually explicit (e.g., `get_config`/`set_config` or just `config` as a property), or distinct verbs are used clearly (e.g., `load_config` vs `apply_config`).
- Inconsistent naming for threshold operations: `transactions_threshold` uses Ruby-style setter syntax (`=`) for setting a global/default value, while `set_connection_threshold` uses an explicit verb for setting a connection-specific value. Meanwhile, `connection_threshold` is a getter for a specific connection. The naming scheme mixes implicit setters (`=`) with explicit verbs (`set_`), and `transactions_threshold` vs `connection_threshold` suggests a potential conceptual overlap or unclear distinction between 'transaction' and 'connection' thresholds.
- Outdated: test_after_commit
- Redundant bang/non-bang pairs without clear semantic distinction in signature: The API exposes both `enable`/`enable!` and `disable`/`disable!`. Typically, the bang (`!`) implies a side effect or a forceful action, while the non-bang might be a query or a safe check. However, `enabled?()` and `disabled?()` already exist for querying state. It is unclear why `enable` and `enable!` are both present as mutators. If `enable!` is 'force enable' and `enable` is 'enable', the distinction is missing from the signature. If they are identical, one is redundant.
