# Changelog

## Score

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

## Lenses

- Code Health 71 → 71 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 49 → 49 (+0.0)
- Readiness 38 → 38 (+0.0)
- Security 100 → 100 (+0.0)

## Resolved (3)

- Documentation: no contributor guidance (README.md)
- Inconsistent parameter semantics for 'unsubscribe'. The parameter name 'unsubscribe' with type 'bool' is confusing. Does passing 'true' mean 'perform the unsubscribe action' or 'is the state now unsubscribed'? Furthermore, 'unsubscribe' is the inverse of 'subscribe', but if 'subscribe' means 'start listening', 'unsubscribe' means 'stop listening'. However, ListenerProvider also has 'addListener' and 'clearListeners'. The presence of 'unsubscribe' on both suggests a lifecycle operation, but the boolean parameter is redundant and confusing (usually a method call implies the action).
- Semantic ambiguity of 'subscribe' across different domains. In EventDrivenListenerInterface, 'subscribe' likely implies starting a long-running listener loop or connection (given the timeout parameter). In ListenerProvider, 'subscribe' is ambiguous: it could mean registering a new listener (which is already done via addListener) or starting the provider's internal subscription mechanism. The naming collision suggests these are different operations (lifecycle management vs. registration) sharing the same verb.
