# Changelog

## Score

- CAI 55 → 58 (+2.8)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 73 → 73 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 43 → 49 (+5.9)
- Readiness 58 → 58 (+0.0)
- Security 100 → 100 (+0.0)

## Resolved (4)

- Duplicate Implementation Logic: Same issue as above for the Query domain. `ContainerQueryHandlerLocator` and `SymfonyContainerQueryHandlerLocator` have identical method signatures.
- Duplicate Implementation Logic: `ContainerCommandHandlerLocator` and `SymfonyContainerCommandHandlerLocator` have identical method signatures for `registerService` and `registerSubscriberService`. While they may differ in internal implementation (generic container vs Symfony-specific), exposing both with identical public APIs suggests a potential duplication of effort or a lack of clear separation of concerns. If `SymfonyContainerCommandHandlerLocator` is just a specialized version, it should extend `ContainerCommandHandlerLocator` or implement a common interface, but the presence of both as distinct top-level types with identical signatures can be confusing.
- Redundant Interface/Class: Same issue as above for the Query domain. `QueryBus` and `HandlerLocatedQueryBus` share the exact same `handle` signature. This creates ambiguity about whether `QueryBus` is an interface or a redundant class.
- Redundant Interface/Class: `CommandBus` appears to be a base interface or abstract class that is functionally identical to `HandlerLocatedCommandBus` regarding the `handle` method. Since `HandlerLocatedCommandBus` is the concrete implementation that actually performs the dispatching via a locator, the existence of `CommandBus` as a separate top-level type with the same signature suggests either a missing interface definition or a confusing hierarchy where the interface name doesn't reflect its role (e.g., should it be `CommandDispatcher`?).
