# Changelog

## Score

- CAI 57 → 60 (+2.7)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 73 → 73 (+0.0)
- Architecture 99 → 99 (-0.0)
- Maturity 44 → 50 (+5.8)
- Readiness 53 → 53 (+0.0)
- Security 100 → 100 (+0.0)

## Resolved (5)

- Ambiguous request handling entry points. handleRequest() takes only a request, implying it creates its own response, while handle() takes both request and response. This duplicates the intent of 'processing a request' but with different responsibilities (response creation vs. response manipulation). It is unclear when to use which.
- Duplicate getter for the event emitter with inconsistent naming. Application.getEmitter() and AbstractApplication.getEventEmitter() likely return the same or similar emitter instances. The naming inconsistency (Emitter vs EventEmitter) is confusing.
- Duplicate initialization logic with divergent signatures. The concrete Application class exposes an init method taking a configuration object, while the AbstractApplication base class also exposes an init method with no parameters. This creates confusion about whether initialization is handled by the concrete class or the abstract base, and suggests a potential code smell where the abstract class should not expose init if the concrete class overrides it with a different signature.
- Duplicate shutdown logic with divergent signatures. Similar to init, Application.shutdown() takes a response object, while AbstractApplication.shutdown() takes no arguments. This inconsistency makes it unclear which method is the canonical shutdown point and risks double-shutdown or missed cleanup if both are called or if the wrong one is called.
- Inconsistent naming for route/command registration. Both Application and Console use the method name 'map' to register handlers, but the parameters differ significantly (HTTP method/route/action vs. command name/callback/arguments). While the domain is different (HTTP vs CLI), the identical method name for distinct registration patterns can be confusing for developers using both.
