v0.9.10

Aelira v0.9.10

Fixed

Document remediation no longer estimates an after-score from how many changes were attempted. Supported comparisons scan the original and saved output with the same deterministic settings. A lower measured score is reported honestly; an unavailable comparison is not replaced with zero or a projected improvement.

DOCX, PowerPoint and Excel uploads retain the canonical findings used by their scanner. Incomplete legacy Office records can be enriched from uniquely matching findings in the retained original. Ambiguous targets, unsupported semantic claims and missing source evidence remain review-required. Original scan records are not rewritten, and recovery does not expand a selected set of findings.

PDF verification requires complete paired checks. HTML/CSS/JavaScript and LaTeX source comparisons use their corresponding source scanners. Static source checks cannot certify website or Canvas browser findings; Canvas stored content has a separate paired browser verification path. Multimedia output without a comparable verifier remains unverified.

Changed

Verified job results include score_verified, score_provenance, and score_measurement. The measurement contains method_version, source_sha256, output_sha256, source_score, and output_score. These fields identify the exact measured artifacts and scoring method; they are not an accessibility conformance certificate.

Unavailable results include a bounded score_verification_reason. Clients must support nullable after-scores and improvement values. Do not calculate substitute scores from fixed counts or assume that a completed job proves accessibility conformance.

Diagnostic	Meaning and next step
original_file_missing	Restore or re-upload the original and scan it again.
original_scan_failed	The original could not be fully scored; inspect scanner availability and the document.
output_file_missing	The saved output could not be read for comparison; re-run remediation from the original.
output_scan_failed	The saved output could not be fully scored; inspect the document and scanner availability.
incomplete_comparison	Required comparison evidence is missing or some source findings could not be reproduced. Review and rescan.
baseline_mismatch	The recorded original score differs from the new paired measurement. Create a fresh scan of the original.
unsupported_scan_type	This path cannot compare the source and output using compatible checks.
legacy_unverified	The old result lacks a verified measurement record. Re-run from the original.
artifact_mismatch	File identity differs from the measurement. Do not rely on that comparison; investigate and re-run.

Operator action required

No database migration or new environment variable is required. Back up the database and retained files, then deploy API, worker, and dashboard from the same 0.9.10 release. Preserve the v0.9.8 operator actions, including worker-health and review requirements.

Existing job estimates remain historical records and are not promoted to verified measurements. Opening an old result may now show an unavailable after-score. Where the original is retained, re-run remediation to produce new evidence. If its original findings cannot be reproduced, create a fresh scan of the original. When the original is missing, recover it from your own source system and upload it again. Scanning a previously remediated file establishes its current score, not the missing before-score.

The public workflow continues to withhold publication of partial remediation output. Recovering legacy findings does not create a new Office approval workflow or enable automatic upload. Review remaining findings and the actual downloaded file before use.

Release verification

Regression suites cover canonical Office persistence, pre-hotfix findings, paired scores, byte identity, safe diagnostics, and old-result presentation. Browser checks supplement the automated tests; they do not imply a complete user-journey CI certification.

The release workflow retains linux/amd64 and linux/arm64 images. Publication uses a signed annotated tag and the existing seven-file SBOM release process. This checked-in release body is consumed verbatim by the release workflow. Image publication and release assets must be checked when the release is tagged.