# Changelog

## Score

- CAI 55 → 61 (+6.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 66 → 66 (+0.0)
- Architecture 96 → 96 (+0.0)
- Maturity 33 → 48 (+14.8)
- Readiness 78 → 78 (+0.0)
- Security 73 → 70 (-3.2)
- Domain Modelling 100 → 100 (+0.0)

## Resolved (4)

- Ambiguous getter/setter pattern. `Resource` exposes `uri(value)` as a method, implying it can be used as both a getter (no args) and setter (with args). While this is a common Ruby idiom, it is inconsistent with other properties like `description(value)` and `description()` which are listed separately. More importantly, `Resource.uri()` is also listed as a method, creating redundancy with the getter behavior of `uri(value)`. This suggests a lack of clarity on whether `uri` is a property or a method.
- Duplicate notification API surface. Both `FastMcp` and `Server` expose `notify_resource_updated`. This mirrors the registration issue, offering two ways to trigger the same internal event, potentially leading to redundant notifications or race conditions.
- Duplicate registration API surface. Both the top-level `FastMcp` class and the internal `Server` class expose identical `register_tool` and `register_tools` methods. This creates confusion about whether the user should interact with the facade (`FastMcp`) or the underlying component (`Server`), and risks double-registration or inconsistent state if both are used.
- Inconsistent server startup/middleware patterns. `FastMcp` offers two distinct methods for Rack middleware (`rack_middleware` vs `authenticated_rack_middleware`), while `Server` offers `start_rack`. It is unclear if `Server.start_rack` is equivalent to one of the `FastMcp` methods or a lower-level primitive. The naming convention (`_middleware` vs `start_`) suggests different abstraction levels that are not clearly documented or separated in the public surface.

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
