# Changelog

## Score

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

## Lenses

- Code Health 87 → 87 (+0.0)
- Architecture 85 → 96 (+10.9)
- Maturity 60 → 63 (+3.3)
- Readiness 66 → 66 (+0.4)
- Security 70 → 61 (-8.7)
- Performance 100 → 100 (+0.0)

## Resolved (10)

- Ambiguous intent between `createFromEvents` and `catchUp`. `createFromEvents` implies reconstruction of a new instance, while `catchUp` implies updating an existing one. However, `catchUp` is also present in `AggregateRootBehaviour` and `AggregateRootMetadataAwareBehaviour`, creating a confusing layer of behavior vs. root methods.
- Duplicate type definitions for descriptor objects with identical signatures in different namespaces. `CommandBus.HandlerDescriptor` and `EventBus.ListenerDescriptor` are structurally identical (name + callable), suggesting a shared base interface or class should be used instead of duplicating the definition.
- Inconsistent factory method naming. `create` is used for the basic case, while `createWithHeaders` is used for the extended case. Standard PHP/PSR conventions often prefer `from*` or distinct static factories, or at least consistent suffixes. `createWithHeaders` is verbose compared to a potential `withHeaders` instance method (which exists) or a static `fromHeaders`.
- Inconsistent method naming for parallel interfaces. `CommandBus.HandlerProvider` uses `handlerForCommand` while `QueryBus.HandlerProvider` uses `handlerForQuery`. While the domain differs, the interface pattern should ideally be consistent (e.g., `handlerFor` with a generic type or consistent naming convention).
- Inconsistent property naming for the same concept. `CommandBus.HandlerReference` uses `commandClass` while `QueryBus.HandlerReference` uses `queryClass`. Since both represent the target class for a handler, the property name should be consistent (e.g., `targetClass` or `eventClass`/`commandClass` depending on context, but the pattern should be uniform).
- Inverted test pyramid
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Rotate the exposed credentials — git history can't be un-committed
- Secret: square-access-token (composer.lock)

## New (1)

- Off-boarding risk: anonymized user #1
