# Changelog

## Score

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

## Lenses

- Code Health 64 → 64 (+0.0)
- Architecture 97 → 97 (+0.0)
- Maturity 52 → 52 (+0.0)
- Readiness 58 → 58 (+0.0)
- Security 74 → 63 (-10.5)

## Resolved (6)

- Duplicate intent: CLI delegates to BuildIpa, but the signatures differ significantly. CLI takes a single `args` object (likely a hash/struct), while the internal class takes separate `_args` and `_options`. This suggests the CLI layer is not just a thin wrapper but performs argument transformation, creating a disconnect between the public entry point and the actual implementation signature.
- Duplicate intent: Similar to IPA, the CLI `build_apk` takes `args` while the internal `BuildApk` class takes `args` and `options`. This inconsistency in how arguments are passed from the CLI layer to the business logic layer is repeated across build commands.
- Inconsistent naming and parameter structure: `Info.info` takes generic `args`, while specific parsers like `ipa_info`, `aab_info`, and `apk_info` take a specific `path` and `options`. This forces the user to understand that `info` is a dispatcher while the others are specific implementations, but the naming doesn't clearly distinguish between 'get general info' and 'parse specific file type'.
- Inconsistent naming convention: `Apk` uses `full_info` and `basic_info`, while `Ipa.App` uses `full_info`, `basic_info`, AND `info`. The presence of `info` in `Ipa.App` alongside `full_info` is redundant, whereas `Apk` does not have this redundancy. This inconsistency makes the API feel uneven across similar parser types.
- Off-boarding risk: anonymized user #1
- Redundant methods: `App.full_info` and `App.info` appear to do the same thing. In many Ruby/Rails contexts, `info` might be a shorthand for `full_info`, but having both exposed creates ambiguity about whether `info` returns a subset or the same data.

## New (1)

- Off-boarding risk: anonymized user #1
