# Changelog

## Score

- CAI 40 → 42 (+1.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 65 → 65 (+0.0)
- Architecture 87 → 86 (-0.8)
- Maturity 50 → 69 (+18.4)
- Readiness 27 → 28 (+1.4)
- Security 46 → 45 (-1.0)
- Domain Modelling 100 → 100 (+0.0)
- Event Sourcing 100 → 100 (+0.0)
- Accessibility 45 → 45 (-0.2)
- Performance 100 → 100 (+0.0)

## Resolved (8)

- Complete duplication of Refresh Session management logic. GameApplication exposes every single method from RefreshSessionUseCases with identical signatures (except for the implicit 'self' context). This makes the Use Case layer redundant and violates the separation of concerns. The Application layer should not expose the internal mechanics of session management directly.
- Same duplication issue as above, but for Player entities. The Application layer exposes two distinct lookup methods for Player that mirror the Port and Repository layers exactly. This violates the principle of the Application layer being a coordinator rather than a pass-through for data access. It also creates a tight coupling between the Application interface and the underlying data model's indexing strategy.
- Scanner failed to run — not a clean result
- Scanner failed to run — not a clean result
- Severe duplication of identity lookup operations across three layers (Application, Port, Repository) with inconsistent naming conventions. The Application layer uses 'get_user_by_*', the Port layer uses 'get_user_by_*', but the Repository layer uses 'get_by_*'. Furthermore, the Application layer exposes low-level repository-style queries directly, bypassing the Use Case pattern for simple lookups, while other operations (like registration) go through Use Cases.
- Split parabellum_app
- Split parabellum_infra
- The GameApplication exposes raw map queries with positional parameters (x, y, radius) directly, while the MapUseCases layer expects structured Request objects. This inconsistency suggests that GameApplication is acting as a facade that duplicates the functionality of MapUseCases but with a less flexible, parameter-heavy signature. It also forces callers to construct coordinate logic that might be better handled by the use case layer.

## New (1)

- Projects may be oversized for their cohesion
