# Changelog

## Score

- CAI 43 → 48 (+4.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 93 → 93 (+0.0)
- Architecture 59 → 58 (-0.6)
- Maturity 44 → 50 (+5.8)
- Readiness 46 → 46 (+0.0)
- Security 31 → 38 (+7.8)
- Domain Modelling 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)

## Resolved (6)

- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- Inconsistent authorizer implementation patterns. The v1 authorizer uses a callback-based pattern with `any` types for context and return values, while the v2 authorizer uses a Promise-based async pattern with typed context and response. This forces consumers to handle two different execution models for the same logical concept (API Gateway authorization).
- Inconsistent parameter naming and typing within the same handler module. `graphqlHandler` uses `lambdaEvent` and `lambdaContext` with V2 event types, while `getUsers` uses `event` and `context` with V1 event types. This creates confusion about which API Gateway version each handler expects and enforces inconsistent naming conventions.
- Medium CVE: [GHSA redacted] (package-lock.json)

## New (7)

- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- Low CVE: [GHSA redacted] (package-lock.json)
- Scattered collaborators
- redundant comment (src/application/eventPublisher.ts)
- redundant comment (src/infrastructure/secrets/index.ts)
