# 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 49 → 52 (+3.0)

## Lenses

- Code Health 76 → 77 (+0.3)
- Architecture 78 → 78 (+0.0)
- Maturity 71 → 71 (+0.2)
- Readiness 42 → 42 (+0.0)
- Security 77 → 78 (+0.9)
- Domain Modelling 61 → 62 (+0.8)
- Accessibility 46 → 61 (+15.3)
- Performance 53 → 53 (+0.0)

## Resolved (7)

- Dead code: IsShareAlreadyAccessible (src/MS.Microservice.Infrastructure/FileSystem/NetworkShareAccessor.cs)
- Further orphaned files (smaller)
- Inconsistent naming for synchronous vs streaming operations. The non-streaming method is named GetResponseAsync, while the streaming method is named StreamAsync. This breaks the parallel naming convention (e.g., both should be GetAsync/StreamAsync or FetchAsync/StreamAsync).
- Inconsistent verb choices for core operations. ASR uses 'Recognize', TTS uses 'Synthesize', Image Generation uses 'Generate', and Image Edit uses 'Edit'. While these reflect domain-specific terminology, the lack of a unified verb (e.g., all using 'Execute' or 'Process') creates a fragmented API surface.
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Off-boarding risk: anonymized user #1

## New (1)

- Off-boarding risk: anonymized user #1

## API surface

- Unchanged — 19 HTTP endpoints