v0.3.7

Aura v0.3.7

This patch release fixes misplaced and oversized interface icons when Windows display scaling is above 100%. It addresses the layout regression introduced by v0.3.6's switch to CPU rendering, while retaining the CPU renderer.

Changes

• Navigation, toolbar, button, and empty-state SVG icons now stay aligned with their controls at 125%, 150%, 175%, and 200% display scaling. Previously, icons could drift down and to the right, leave their button bounds, or appear outside an empty-state badge while text and backgrounds remained correctly positioned. The problem was triggered by display scaling, including on 2560 x 1440 monitors.
• The cause was a double application of the DPI transform in Iced 0.13's tiny-skia SVG path. Aura now carries a small local renderer patch: the engine passes logical bounds, SVGs are rasterized at physical resolution, and their position and dimensions are transformed once. The patch preserves rotation, tint, opacity, and clipping. Its source and MIT license are recorded in vendor/iced_tiny_skia/.
• Regression coverage exercises the actual Aura icon widget and the renderer's offscreen pixel output at 100%, 125%, 150%, 175%, and 200%. CI also runs the patched renderer's tests separately, because that dependency is not a workspace member.

Upgrade behavior

Install the update through Settings or run aura-setup.exe, then reopen Aura to load the corrected renderer. The installer retains existing application and Profile configuration and the previous installation directory. The installer closes the Aura control process without recursively terminating applications it launched.

This release requires no Profile migration. Runtime hooks, virtualization behavior, and Windows system display settings are unchanged. CPU rendering remains enabled; this release does not make a new memory-performance claim.

Validation and limitations

• Before the fix, the actual Aura icon widget regression failed at 125% scaling: the Apps icon produced a visible pixel at (130, 159) outside its expected physical bounds (100, 125, 22.5, 22.5). The same regression passes with the fix, including repeated scale changes through one renderer and its cache.
• Local GUI tests passed: 35 passed, 5 ignored. The ignored tests require installed applications, a live release download, or explicitly requested UI snapshot output.
• Local renderer tests passed: 3 passed, 0 failed. They assert exact SVG pixel bounds and filled area, rotation with tint and opacity, and layer clipping across all five display scales.
• Local workspace build and cargo check --workspace passed. With the existing Runtime DLLs supplied, local workspace tests stopped at the same acceptance_ansi_default_locale_uses_profile failure recorded for v0.3.6: the session returned en-US where the test expects fr-FR; six other tests in that matrix passed and one was ignored. This local run is not a complete workspace test pass. Clean Windows CI for the release commit is required before tagging.
• Fifteen 2560 x 1440 offscreen snapshots were generated from Aura's actual Application, Audit, and Settings views with isolated configuration, covering all five display scales. The Audit view at 150% and Application and Settings views at 200% were visually inspected: navigation and action icons aligned correctly, and the audit document icon was centered inside its badge.
• These are renderer and page-code checks, not verification of a fresh installed upgrade, cross-monitor window dragging, high-DPI fast scrolling, or an hours-long memory observation on the user's physical display. Those interactions remain manually unverified.
• Publication is gated on a successful Windows CI run for the exact release commit, including workspace build/tests and the renderer regressions. The release workflow builds all six executables and both Runtime DLLs through the canonical installer script and appends the published installer's size and SHA-256 below.

Installer

• File: aura-setup.exe
• Size: 6344242 bytes
• SHA-256: b64722ccb2366a44ffc42eefdf71426a59350b3fbcdb1f2db20a9ce390a77002