# Changelog

## Score

- CAI 66 → 64 (-2.1)
- Rubric changed (rubric-2026.10.1 → rubric-2026.10.5) — scores are not directly comparable.

## Lenses

- Code Health 97 → 74 (-22.7)
- Architecture 69 → 69 (+0.0)
- Maturity 56 → 55 (-0.6)
- Readiness 67 → 67 (+0.0)
- Security 99 → 99 (+0.0)

## Resolved (4)

- Ambiguous distinction between 'humanized_money' and 'humanized_money_with_symbol'. It is unclear if 'humanized_money' excludes the symbol by default or if the distinction is purely stylistic. If the symbol is optional via `options`, the separate method is redundant. If the symbol is always included in the latter, the naming is inconsistent with the former.
- Inconsistent parameter handling and naming. One method accepts `options` while the other does not, despite performing similar formatting tasks (stripping cents). This suggests a lack of unified formatting strategy in the view helpers.
- PR-triggered workflow without a permissions block
- Redundant method names for identical operations. 'add_money' and 'add_monetize' (and their 'remove' counterparts) appear to perform the same database schema modification. Similarly, 'Table.money' and 'Table.monetize' are likely aliases for the same DSL action. This forces users to guess which name is preferred or if they have different behaviors.

## New (6)

- Ambiguous distinction between similar view helpers. While 'with_symbol' is explicit, 'humanized_money' might imply inclusion of the symbol or not depending on global configuration. This creates confusion for developers who must guess the default behavior or check documentation to ensure the symbol is included/excluded.
- Duplicate intent with inconsistent naming. 'add_money'/'money' and 'add_monetize'/'monetize' appear to perform the same database migration operation (adding a money column and associated subunit/currency columns). The library exposes two parallel sets of methods for the same underlying schema change, likely due to historical naming changes or aliases, but exposes both without clear deprecation or distinction.
- Duplicate intent with inconsistent naming. Similar to the add operations, 'remove_money' and 'remove_monetize' are duplicated across SchemaStatements and Table contexts. This forces users to choose between two synonymous methods for dropping money columns.
- Orphaned file (lib/generators/templates/money.rb)
- Orphaned file (lib/money-rails/configuration.rb)
- PR-triggered workflow without a permissions block (.github/workflows/ruby.yml)

## Architecture

- 0 containers · 1 bounded contexts · 0 dependency edges (baseline)