# Changelog

## Score

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

## Lenses

- Code Health 100 → 100 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 54 → 54 (+0.0)
- Readiness 36 → 36 (+0.0)
- Security 100 → 100 (+0.0)

## Resolved (3)

- Confusing separation of concerns between `Actions.get` and `Action.swift.action`. `Actions.get` retrieves an instance, while `Action.swift.action` seems to execute or transform. However, the naming `action` is ambiguous—it could imply retrieval, execution, or configuration. Given `Action.perform` exists, `action` is a confusingly named method that overlaps with execution semantics.
- Duplicate intent for registering/configuring an action. `Actions.plug` and the infix operator `<~` appear to perform the same registration logic but use different naming conventions (method vs operator) and potentially different parameter structures (one takes a closure directly, the other uses an infix pattern).
- Inconsistent overloading strategy for the `action` method. The API exposes four overloads that mix optional and non-optional types for both the action type and input/output, creating ambiguity. It is unclear why `T?` variants exist alongside `Type` variants, or if they serve distinct domains. This suggests a lack of clear generic constraints or protocol adherence.
