# Changelog

> **This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.**

## Score

- CAI 28 → 41 (+12.9)
- Rubric changed (rubric-2026.08.18 → rubric-2026.08.19) — scores are not directly comparable.

## Lenses

- Code Health 100 (new)
- Architecture 100 (new)
- Maturity 13 → 43 (+29.5)
- Readiness 15 → 8 (-7.7)
- Security 100 → 97 (-2.5)

## Resolved (5)

- Dependency hygiene not measured — no supported dependency manifest was read
- No automated tests
- No tests found
- bus factor not measured — no commits were sampled
- single-commit history — no usable git history window to measure hotspots

## New (9)

- Coverage not included — suite not readable by the collector
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- Leaked secret: high-entropy-secret (adapters/src/main/resources/application.yml)
- Leaked secret: signing-key (adapters/src/main/resources/application.yml)
- Medium: security finding (details withheld)
- Scanner failed to run — not a clean result
- git history depth insufficient
- git history depth insufficient
- single-maintainer — knowledge-concentration (bus factor) risk