# Changelog

## Score

- CAI 56 → 56 (+0.3)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 75 → 75 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 43 → 43 (+0.0)
- Readiness 49 → 49 (+0.0)
- Security 96 → 100 (+4.1)

## Resolved (4)

- Duplicate functionality exposed through different types with different verbs. `Container` exposes `observe`/`unobserve`, while `DependencyWatcher` exposes `watch`/`unwatch`. These appear to manage the same underlying observer pattern. Exposing both creates confusion about whether the user should interact with the Container or the Watcher directly.
- Inconsistent naming between `Container` and `Registry` for similar operations. `Container` uses `register` and `namespace`, while `Registry` uses `register_dependency` and `register_namespace`. This forces users to remember different method names depending on whether they are interacting with the high-level Container or the lower-level Registry, despite the operations being semantically identical.
- Inconsistent naming for the same operation. `Container` uses `clear_observers` while `DependencyWatcher` uses `clear_listeners`. This is a minor naming inconsistency that breaks API uniformity.
- Redundant methods with ambiguous distinction. Both `Container` and its internal `DependencyResolver` expose both `resolve` and `fetch`. In dependency injection contexts, 'resolve' typically implies instantiation or full resolution, while 'fetch' might imply retrieval from cache or raw lookup. However, without clear documentation or distinct behavioral signatures in the API surface, these appear to be duplicate entry points for the same core operation, confusing users about which to use.
