# Changelog

## Score

- CAI 59 → 59 (+0.0)
- 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 43 → 43 (+0.0)
- Readiness 75 → 75 (+0.0)
- Security 95 → 95 (+0.0)

## Resolved (3)

- Conflicting naming for setting alignment. `alignment=` is a standard Ruby setter for a property. `align` is a method that takes multiple arguments (`val, position, length`), suggesting it might perform rendering or complex alignment logic rather than just setting a state. However, the name `align` is often used as a synonym for 'set alignment' in other libraries, causing confusion about whether it is a setter or a rendering helper.
- Inconsistent and unclear naming for border style setters. `border_x`, `border_y`, and `border_i` are cryptic abbreviations. `border_x` and `border_y` likely refer to horizontal and vertical lines, but `border_i` is unclear (possibly 'inner' or 'index'?). This contrasts with the explicit `border_top=`, `border_bottom=`, etc., which are clear.
- Redundant getter signatures. The presence of both `alignment?()` (likely returning nil if not set) and `alignment()` (likely returning a default or the value) creates ambiguity. In Ruby, `alignment()` is the standard getter. If `alignment?` is intended to be a predicate (boolean), it conflicts with the name `alignment`. If it is an optional getter, it duplicates the intent of `alignment` with a different return contract.
