# Changelog

## Score

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

## Lenses

- Code Health 74 → 74 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 52 → 49 (-2.5)
- Readiness 62 → 62 (+0.0)
- Security 82 → 69 (-12.3)

## Resolved (5)

- Documentation: no architecture or design documentation (README.markdown)
- Documentation: no project overview (README.markdown)
- Inconsistent Return Type for Rendering: All renderers implement `renderKeys` returning `Seq[String]`. However, `BuildInfoRenderer` trait defines `renderKeys(infoKeysNameAndValues: Seq[BuildInfoResult]): Seq[String]`. While consistent in signature, the naming `renderKeys` vs the input `infoKeysNameAndValues`/`buildInfoResults` is slightly inconsistent in parameter naming across implementations, though this is minor. More importantly, `Scala3CaseObjectRenderer` has an additional `toStringLines` method not present in others, which might be internal helper but is exposed.
- Off-boarding risk: anonymized user #1
- Redundant/Confusing TaskKey handling: `BuildInfoKey.apply` accepts `TaskKey` directly, but there is also a specific `outOfGraphUnsafe` method for `TaskKey`. It is unclear why `apply` handles `TaskKey` safely while `outOfGraphUnsafe` exists, or if `outOfGraphUnsafe` is just an alias for a specific unsafe behavior of `apply`. This creates ambiguity about which method to use for TaskKeys.

## New (1)

- Off-boarding risk: anonymized user #1
