# Changelog

## Score

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

## Lenses

- Code Health 70 → 70 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 50 → 50 (+0.0)
- Readiness 23 → 23 (+0.0)
- Security 100 → 100 (+0.0)

## Resolved (5)

- Ambiguous reconstruction intent. `AggregateRoot.fromEvents` takes a single `AggregateEvent` (singular type hint but likely iterable in usage given the name) to reconstruct state, while `Repository.load` handles the full persistence lifecycle. The method name `fromEvents` (plural intent) accepting a singular type hint `AggregateEvent` is confusing. Furthermore, having a static-style reconstruction method on the AggregateRoot itself bypasses the Repository, which can lead to inconsistent state if the Repository performs additional hydration logic.
- Inconsistent naming for similar operations. `ReadModelManager` uses `registerReadModel` while its concrete implementation `PdoReadModelManager` uses `withReadModel`. These appear to perform the same function (associating a read model with the manager), but the different verbs (`register` vs `with`) create confusion about whether they have different side effects or lifecycles.
- Inconsistent parameter typing. The interface/base `EventStore` and its implementations accept `AggregateEvent` (singular) for the `add` method, despite the parameter name being plural `events`. This suggests the method is intended to handle multiple events, but the type hint indicates a single event. This is a type signature inconsistency.
- No tests found
- Redundant creation paths with inconsistent signatures. The static factory `create` omits the `version` parameter (likely setting it to 0 or 1 internally), while the constructor requires it. This creates two ways to instantiate the same immutable value object with different required arguments, confusing users about whether they should use the factory or the constructor.
