# Changelog

## Score

- CAI 52 → 56 (+3.7)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 99 → 99 (+0.0)
- Architecture 85 → 85 (+0.0)
- Maturity 50 → 73 (+23.3)
- Readiness 41 → 41 (+0.0)
- Security 98 → 98 (+0.0)
- Domain Modelling 53 → 53 (+0.0)

## Resolved (5)

- Duplicate intent: Both methods appear to handle state restoration. Android standard is onRestoreInstanceState, but the custom onRestoreState suggests a parallel or redundant mechanism.
- Duplicate intent: Both methods appear to handle state saving in Fragment. Android standard is onSaveInstanceState, but the custom onSaveState suggests a parallel or redundant mechanism.
- Duplicate intent: Both methods appear to handle state saving. Android standard is onSaveInstanceState, but the custom onSaveState suggests a parallel or redundant mechanism.
- Inconsistent return type: Activity's onBackPressed returns Unit (void), while Fragment's and the marker interface's onBackPressed return Boolean. This inconsistency makes it difficult to create a unified handler for back press events across components.
- Redundant interface: AbstractViewModel implements lifecycle methods that are also defined in the ViewModelLifecycle marker interface. If AbstractViewModel is the base class, it should implement the interface, but the duplication of signatures in the public surface suggests confusion about whether users should interact with the class methods or the interface methods.

## Architecture

- Unchanged — 0 containers · 4 contexts · 1 edges
