# Changelog

## Score

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

## Lenses

- Code Health 99 → 99 (+0.0)
- Architecture 92 → 92 (-0.0)
- Maturity 37 → 37 (+0.0)
- Readiness 64 → 64 (+0.0)
- Security 98 → 98 (+0.0)

## Resolved (3)

- Ambiguous Action Execution Pattern: `Foundation.Action` has a generic `resolve` method, while `DataMapperAction` and the `DataMapper` contract use `execute`. Additionally, `ResolveCommandAction` and `ResolveComposerAutoLoaderAction` also use `execute`. The `Foundation.Action` class seems to be a base or factory that might delegate, but its `resolve` method signature is distinct from the `execute` pattern used by the concrete action classes. This suggests a split in how 'actions' are invoked.
- Duplicate Intent in Factory Resolution: Both the `Factory` contract and `CreateNewFactory` foundation class expose `resolveFactory()`. It is unclear if `CreateNewFactory` implements `Factory` or if they are separate concepts. If `CreateNewFactory` is the implementation, it should implement the contract. If they are distinct, the naming `resolveFactory` in both suggests they do the same thing (resolving a factory instance), leading to potential confusion about which one to use.
- Inconsistent Resolution Method Naming: The `HasOptions` trait provides specific resolution methods like `resolveForceOption`, `resolveEventOption`, and `resolveModelOption`. However, the `HasArguments` trait and `Arguments` contract use a generic `resolveNameArgument`. Furthermore, `InteractsWithConsole` has `getFileName` and `getClassName` (getters) while `HasOptions` has `resolve...` (resolvers). This mixes 'getting' and 'resolving' semantics inconsistently across concerns.
