# Changelog

## Score

- CAI 53 → 54 (+1.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 72 → 72 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 61 → 65 (+4.1)
- Readiness 34 → 34 (+0.0)
- Security 99 → 97 (-1.3)
- Performance 100 → 100 (+0.0)

## Resolved (5)

- Ambiguous ownership of data fetching. UserInteractor has a 'fetchUser' method, but DelayedUserService also has a 'fetch' method. It is unclear if the Interactor delegates to the Service or if they are redundant. Given the Interactor pattern, the Interactor should likely not expose 'fetchUser' directly if the Service is the data source, or the Service should not be directly accessible if the Interactor is the sole entry point.
- Documentation: no installation or build instructions (README.md)
- Inconsistent UI update pattern. LoginViewController has a specific 'clearPassword()' method, whereas other ViewControllers (Settings, User) use a generic 'configure(with: ViewModel)' pattern. This suggests 'clearPassword' is a manual imperative call rather than a declarative state update via ViewModel, breaking the MVVM consistency.
- Inconsistent naming for lifecycle initialization. LoginPresenter uses 'prepare()' while UserPresenter also uses 'prepare()', but HomePresenter and SettingsPresenter do not have a 'prepare()' method, relying instead on the constructor or implicit initialization. This creates an inconsistent pattern for view controller/presenter setup across the module.
- Presenter exposes imperative UI-state mutation methods (setEmail, setPassword, submit, logout) that duplicate the intent of the Interactor's API. The Interactor already has setEmail, setPassword, submit, and logout. The Presenter should typically only expose a view model or handle view lifecycle events, not act as a proxy for the interactor's business logic commands.

## New (1)

- High interface indirection
