# 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 52 → 54 (+1.8)
- Rubric changed (rubric-2026.08.17 → rubric-2026.08.18) — scores are not directly comparable.

## Lenses

- Code Health 100 → 100 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 58 → 58 (+0.0)
- Readiness 59 → 59 (+0.0)
- Security 67 → 91 (+24.0)
- Domain Modelling 38 → 38 (+0.0)

## Resolved (6)

- Dependency hygiene not measured — no supported dependency manifest was read
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)

## New (3)

- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- OSV Dependency Vulnerabilities not included (check did not complete)
- The 'Architecture & code organization' section is cut off by the scanner mid-sentence ('Midway through each API request...'), so its full outline (setup, download/install both project and dev dependencies, start dependencies, run db migrations, load fixtures) cannot be confirmed from the visible text. (README.md)