# Changelog

## Score

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

## Lenses

- Code Health 83 → 67 (-16.3)
- Architecture 96 → 96 (+0.7)
- Maturity 59 → 37 (-22.6)
- Readiness 70 → 70 (+0.0)
- Security 80 → 80 (-0.0)
- Accessibility 58 → 58 (+0.0)

## Resolved (4)

- Ambiguous distinction between `version` and `full_version`. It is unclear if `full_version` provides additional metadata (like build info, git hash) or if it is just a more verbose string representation. This forces users to call both or guess which one they need.
- Redundant naming convention for side-effect vs pure operations. In Ruby, the `!` suffix typically denotes a 'bang' method that modifies state or raises errors, while the non-bang version might return a result or be safer. However, `optimize_image` and `optimize_image!` taking the same arguments suggests they perform the same core optimization logic. Without documentation, it is unclear if one is a wrapper for the other or if they differ in error handling. This creates cognitive load for users who must guess the semantic difference.
- Same redundancy issue as `optimize_image`/`optimize_image!`. The presence of both bang and non-bang variants for batch operations with identical signatures suggests inconsistent API design regarding side-effects or error handling.
- Workflow token grant is wider than its jobs use

## New (4)

- Ambiguous intent. It is unclear if `full_version` returns a more detailed string (e.g., including dependencies) or if it is a duplicate of `version`. If they return the same data, one is redundant.
- Redundant naming convention for identical operations. In Ruby, the `!` suffix typically implies a destructive or exception-raising variant, but here both methods appear to perform the same optimization logic on the same input type. Without distinct behavioral differences (e.g., one raising on failure, one returning nil), this creates API confusion.
- Same redundancy issue as above, but for the batch processing method. The `!` variant is likely a duplicate or a confusingly named strict variant.
- Workflow token grant is wider than its jobs use (.github/workflows/build-test-containers.yml)

## Changes since last survey

- 1 commits — 1 feature/other, 0 fixes

## By area

- .github/workflows — 1 commit

## Notable commits

- change: Bump ruby/setup-ruby from 1.327.0 to 1.328.0 in the non-major group (#247)