# Changelog

## Score

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

## Lenses

- Code Health 73 → 73 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 38 → 38 (+0.0)
- Readiness 65 → 65 (+0.0)
- Security 99 → 98 (-0.7)

## Resolved (7)

- Consistent signatures for `model`, but `ArrayFilter` has `model` while `HashFilter` also has `model`. This is consistent. However, `ArrayFilter` has `hash` and `array` methods that differ from `HashFilter`. The inconsistency is specifically in `hash` and `array` methods between these two types.
- Duplicate intent with ambiguous distinction. Two methods exist with nearly identical names (`run` vs `run!`) but different signatures (one takes no args, one takes no args). The `!` suffix usually implies mutation or raising errors, but without seeing bodies, the API surface suggests redundant entry points for execution.
- Inconsistent arity and naming convention for execution methods. One takes arguments, the other does not, despite both being named 'run' variants. This suggests a confusion between 'building' a command with args vs 'executing' it, or a copy-paste error in signature design.
- Inconsistent method signatures for defining nested array structures. `ArrayFilter.array` takes `(options, block)` while `HashFilter.array` takes `(name, options, block)`. The `name` parameter is missing in `ArrayFilter`.
- Inconsistent method signatures for defining nested structures. `ArrayFilter.hash` takes `(options, block)` while `HashFilter.hash` takes `(name, options, block)`. The `name` parameter is missing in `ArrayFilter`, making the API inconsistent for defining nested hash inputs within an array context.
- Off-boarding risk: anonymized user #1
- While these are on different types, the naming `message` vs `message_list` is inconsistent across error container types. `ErrorAtom` has both, but `ErrorHash` and `ErrorArray` also have both. However, `ErrorAtom` is a single error, `ErrorHash`/`ErrorArray` are collections. The inconsistency lies in `ErrorAtom` having `message` (singular) and `message_list` (plural), whereas the collection types also have both. This is actually consistent, BUT `ErrorAtom.message()` and `ErrorHash.message()` returning different structures (string vs array of strings?) would be an inconsistency. Assuming they return strings, it's fine. However, `ErrorAtom` having `message_list` is semantically odd for a single atom.

## New (1)

- Off-boarding risk: anonymized user #1
