# Changelog

## Score

- CAI 58 → 61 (+3.4)
- 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 43 → 49 (+5.9)
- Readiness 69 → 69 (+0.0)
- Security 81 → 95 (+13.8)

## Resolved (3)

- Inconsistent naming for bulk vs single operations. `delete` takes keys (plural), while `remove` takes no arguments (implies clearing the whole hash). In other types, `clear` is used for emptying (e.g., List.clear, Set.clear). `remove` is ambiguous: does it remove the hash itself or its contents? `delete` is used for specific keys, but `remove` is used for the whole structure. This is inconsistent with `List.clear` and `Set.clear`.
- Inconsistent naming for collection modification. `prepend` and `append` are used in List, UniqueList, and OrderedSet. However, Set uses `add` and `remove`. While `add`/`remove` is standard for Sets, `prepend`/`append` is specific to ordered collections. The inconsistency lies in the fact that `OrderedSet` behaves like a Set (no duplicates) but uses List-like methods (`prepend`/`append`), whereas `Set` uses `add`/`remove`. This creates a cognitive load where the user must remember the collection type to know the method name.
- Inconsistent naming for state mutation vs query. `mark` sets the flag, but `remove` deletes it. In other types (e.g., Counter, Enum), `reset` is used to clear state. `remove` implies deletion of the object/key rather than resetting the state, which is inconsistent with `reset` used in Counter and Enum.
