# Changelog

## Score

- CAI 42 → 42 (+0.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 71 → 71 (+0.0)
- Architecture 73 → 73 (+0.0)
- Maturity 48 → 48 (+0.0)
- Readiness 28 → 28 (+0.0)
- Security 43 → 43 (+0.0)
- Domain Modelling 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)

## Resolved (4)

- Ambiguous distinction between Update and Upsert at the repository level. Both `UpdateTodo` and `UpsertTodo` have identical properties (`id`, `title`, `description`, `status`). Without seeing the implementation, it is unclear how the repository distinguishes between 'fail if not exists' (Update) and 'insert if not exists' (Upsert). If the signatures are identical, the API surface fails to communicate the distinct intent of the operation to the caller.
- Redundant DTOs with identical signatures. `UpdateTodoView` and `UpsertTodoView` have the exact same properties and constructor signatures. In most architectures, an 'Update' implies existence (requiring ID) and 'Upsert' implies upsert logic (also requiring ID). If the business logic for update vs upsert is identical at the DTO level, these should be merged into a single `ModifyTodo` or `TodoUpdate` type to reduce maintenance surface.
- Semantic mismatch in 'find' operations. The kernel repository `find` takes a full `TodoStatus` object (entity), while the use case `find_todo` takes a `SearchTodoCondition` containing only a `status_code` (string). This forces the use case to perform domain logic (lookup by code) that arguably belongs in the repository or requires awkward mapping, breaking the separation of concerns.
- Type mismatch in collection definition. `JsonTodoList` is named as a list/collection, but its property `todos` is typed as a single `JsonTodo` (singular), and the constructor accepts a single `JsonTodo`. This contradicts the plural naming convention and likely causes confusion or runtime errors if multiple items are expected.
