# Changelog

## Score

- CAI 70 → 73 (+2.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

## Lenses

- Code Health 100 → 100 (-0.3)
- Architecture 100 → 97 (-2.9)
- Maturity 50 → 55 (+5.2)
- Readiness 81 → 80 (-0.6)
- Security 94 → 94 (+0.0)

## Resolved (5)

- Duplicate operations on Route. Both `run` and `handle` have identical signatures and likely identical implementations (invoking the route handler). This creates ambiguity for consumers regarding which method represents the 'execution' of the route.
- Inconsistent resolution strategy naming. `CallableResolver` has a generic `resolve` method, but also specific `resolveRoute` and `resolveMiddleware` methods. The interface `AdvancedCallableResolverInterface` exposes the specific methods but not the generic one. This suggests that `resolve` might be a fallback or that the specific methods are redundant if `resolve` handles context-aware resolution. It forces users to choose between a generic resolver and specific resolvers without clear distinction in intent.
- Off-boarding risk: anonymized user #1
- Redundant method pairs for adding middleware. Both `add` and `addMiddleware` exist on App, MiddlewareDispatcher, Route, and RouteGroup. While `addMiddleware` is type-safe, `add` is an alias that likely accepts mixed types or strings, creating confusion about which method to use. The naming convention is inconsistent with standard PSR-15/PSR-15-like patterns where a single `add` or `pipe` is typical.
- Semantic overlap in route lookup. `RouteCollector.lookupRoute` and `RouteResolver.resolveRoute` appear to perform the same function: finding a route by identifier. `RouteCollector` is typically for definition, while `RouteResolver` is for execution, but having two public APIs for the same lookup operation creates redundancy.

## New (3)

- Edited copy of a member (19 corresponding lines) (Slim/MiddlewareDispatcher.php)
- Edited copy of a member (8 corresponding lines) (Slim/Factory/Psr17/Psr17Factory.php)
- Off-boarding risk: anonymized user #1
