# Changelog

## Score

- CAI 45 → 53 (+8.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 43 → 43 (+0.4)
- Architecture 88 → 98 (+10.4)
- Maturity 33 → 55 (+21.4)
- Readiness 62 → 62 (+0.0)
- Security 60 → 60 (+0.6)
- Performance 94 → 94 (+0.0)

## Resolved (13)

- ASTAnalyzer.visit_ClassDef (cognitive 17) (tools/analyze_codebase_ast.py)
- Critical CVE: [GHSA redacted] (uv.lock)
- Critical CVE: [GHSA redacted] (uv.lock)
- Documentation: contradicts the code (docs/DOCUMENTATION_GUIDE.md)
- Documentation: contradicts the code (docs/plans/2026-02-05-A03-p0-p1-improvements.md)
- Documentation: no project overview (README.md)
- Inconsistent method naming on analyzer classes. 'analyze_file' implies the method handles file I/O or is specific to files, whereas 'analyze_flow' implies it operates on the Flow object. Since both are instance methods on their respective analyzers, the naming should be parallel (e.g., 'analyze' or 'analyze_routine' vs 'analyze_flow').
- Inconsistent naming for top-level analysis entry points. One uses 'analyze_routine_file' (specific to file input) while the other uses 'analyze_workflow' (generic to the object). This breaks the parallel structure expected in a library API.
- Medium CVE: [GHSA redacted] (uv.lock)
- Medium CVE: [GHSA redacted] (uv.lock)
- Projects may be oversized for their cohesion
- analyze_codebase_ast.format_compact_doc (cognitive 115) (tools/analyze_codebase_ast.py)
- analyze_codebase_ast.format_compact_doc (cyclomatic 27) (tools/analyze_codebase_ast.py)

## New (5)

- Critical CVE: [GHSA redacted] (uv.lock)
- Critical CVE: [GHSA redacted] (uv.lock)
- Medium CVE: [GHSA redacted] (uv.lock)
- Medium CVE: [GHSA redacted] (uv.lock)
- Medium CVE: [GHSA redacted] (uv.lock)

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
