# Changelog

## Score

- CAI 60 → 58 (-1.8)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 86 → 86 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 49 → 49 (+0.0)
- Readiness 58 → 58 (+0.0)
- Security 74 → 61 (-12.8)

## Resolved (7)

- Confusingly named/overlapping intent: Similar to colors, `UI.resolve_style` and `FrameStyle.lookup` likely perform similar lookups. `UI.resolve_style` suggests a higher-level API, while `FrameStyle.lookup` is type-specific.
- Confusingly named/overlapping intent: `UI.resolve_color` likely takes a string/input and returns a color object or code, while `Color.lookup` takes a name and returns a Color object. It is unclear if `UI.resolve_color` is a higher-level wrapper that calls `Color.lookup` or if they serve different purposes (e.g., parsing vs. lookup).
- Documentation: no architecture or design documentation
- Duplicate intent: Both `UI` and `Prompt` expose an identical `any_key` method signature. This is a low-level blocking input operation duplicated across two types.
- Duplicate intent: Both `UI` and `Prompt` expose an identical `confirm` method signature. `Prompt` appears to be a specialized subset or facade for interactive input, yet it duplicates the high-level UI interaction method.
- Duplicate intent: Both `UI` and `Prompt` expose an identical, complex `ask` method signature. This is the most significant duplication, as `ask` is a core interactive feature.
- Duplicate intent: `Printer` is a distinct type that exposes the exact same `puts` signature as `UI`. `Printer` appears to be an internal implementation detail or a facade that duplicates the public API of `UI`.
