# Changelog

## Score

- CAI 66 → 67 (+1.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 76 → 76 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 57 → 61 (+3.7)
- Readiness 80 → 80 (+0.0)
- Security 82 → 73 (-8.9)

## Resolved (3)

- Duplicate intent across nested config types: `Slack.Config`, `Slack.Events.Config`, and `Slack.Web.Config` all have a `reset()` method. While they operate on different scopes, the repetition suggests a shared base class or module for configuration management could reduce duplication and ensure consistent behavior.
- Legacy vs Modern API duplication: `Oauth.oauth_access` corresponds to the deprecated OAuth 1.0a flow, while `OauthV2.oauth_v2_access` is the modern OAuth 2.0 flow. While technically distinct due to API versioning, exposing both without clear deprecation warnings or a unified `oauth_access` entry point that handles versioning internally can confuse users.
- Redundant configuration methods: Every major subsystem (Slack, Events, Web, Client) exposes both a `configure()` and a `config()` method. In Ruby libraries, `config` is typically a getter for the configuration object/state, while `configure` is a setter/block-based mutator. However, exposing both on every single module creates significant API bloat and confusion about whether they are aliases or distinct operations (e.g., does `config()` return a mutable object that affects state, or is it a snapshot?).
