v0.3.16

Aura v0.3.16

本版本支持为已配置的应用创建桌面快捷方式，双击即可按绑定环境启动，无需先打开 Aura。

Changes

• 已保存应用的详情页新增“创建桌面快捷方式”。快捷方式按“应用名 - 环境配置名”命名，例如 ChatGPT - US Development，使用目标应用自身的图标。
• 快捷方式引用 Application UUID，每次启动读取应用最新保存的默认 Profile、参数、工作目录和终端宿主设置。修改应用配置后，原快捷方式继续生效；文件名保留创建时的环境名称。
• 新增无主窗口启动入口，在 GUI 单例检查前处理快捷方式请求。Aura 未运行或主窗口已打开时均可直接启动目标，成功后启动入口退出，独立后台会话继续托管进程树。
• Windows Terminal 启动会等待真实启动交接完成，保留应用选择的终端宿主；交接超时或失败时取消本次启动并显示错误。
• 修复商店应用快捷方式使用 Aura 图标的问题。按 AUMID 从 Windows 应用命名空间读取图标，应用列表与快捷方式共用图标解析；创建快捷方式时可按需取图标，不依赖界面异步加载完成。
• 图标缓存包含实际图标源，编辑同一应用的启动目标后会重新取图标；命令应用先解析 PATH 中的实际程序，避免裸命令名称导致快捷方式使用 Aura 图标。
• 同一应用、配置目录和启动入口的同名快捷方式可重复更新；与其他桌面文件重名时添加编号，不覆盖无关文件。应用或绑定 Profile 缺失、配置损坏及启动失败均给出可见提示，不退回本机环境启动。

Validation

• 已在开发版界面实际创建原生 .lnk，并通过 Windows 桌面启动路径验证无 Aura 主窗口时的启动和后台存活。
• 同一快捷方式先后使用日语／东京时区与英语／伦敦时区，实际 Probe 读数、环境变量和工作目录与保存配置一致。Windows Terminal 启动及绑定 Profile 缺失时的错误提示也已有实机验证。
• 已在本机验证 ChatGPT 商店应用图标生成与 Windows Shell 实际图标读取，保留原快捷方式的启动目标和环境参数。
• 用户已确认本次功能测试通过；当前 ChatGPT、Codex 与命令子进程的 Runtime 载入及美国环境读数已核验，未注入对照进程仍读取宿主原设置。
• 发布门禁沿用干净 Windows CI：完整工作区、双架构 Runtime／DNS fixture、独立会话及 CPU 渲染器检查。正式 Release 工作流使用项目安装脚本生成安装包及 SHA-256 校验文件。

Limitations

快捷方式启动的普通实例由独立后台会话托管，当前不自动显示在 Aura 的运行实例列表中。浏览器网页沙箱仍受既有 Runtime 覆盖范围限制。

Upgrade

现有应用、Profile 与浏览器数据保留。旧的带 Aura 后缀的应用快捷方式继续可用；可在应用详情重新创建使用环境名称的新快捷方式，已有桌面文件不会被批量改名。

新配置和 Runtime 版本在之后启动的实例中生效，运行中的进程不热更新。本次发布不自动安装或重启用户正在使用的本机应用与服务。

Installer

• File: aura-setup.exe
• Size: 12153854 bytes
• SHA-256: c2e1e2118ef2a517a3b9c145852ec79b1fbb835421ce4e5e8a436d92b2ad55a3

v0.3.15

Aura v0.3.15

本版本新增浏览器独立数据目录、实际出口与时区查询、Profile HTTP／SOCKS5 代理和两个固定检测入口，并整理环境配置、应用、运行实例三个页面的职责。

Changes

• 环境配置可查询实际网络出口并预览 IANA／Windows 时区，确认后只填入两个时区字段，保存后生效。出口 IP 为本次请求的只读结果；取消、查询失败或过期结果不会覆盖已保存配置。时区映射使用随产品提供的 Unicode CLDR 数据，不通过国家或 UTC 偏移猜测具体时区。
• Profile 支持无代理、HTTP、SOCKS5，以及代理服务器地址和端口。受支持 Chrome 与出口／时区查询共用该配置；SOCKS5 使用代理侧 DNS，代理连接失败不回退直连。未配置代理的旧应用保留原网络行为，Host 启动不继承 Profile 代理；不修改 Windows 全局代理，不支持认证代理或任意进程全流量代理。
• Chrome 应用可开启独立数据目录，按应用和实际选择的 Profile 稳定分配；Host 使用单独身份。普通启动、临时选择环境与历史工作区链路共用目录规则。已有目录占用、参数冲突或配置身份无法确认时明确拒绝，不把旧浏览器误报为新的受控实例。
• 应用页提供 IPPure Claude 与 Net.Coffee Claude 检测入口，可选择已保存环境或 Host。页面在对应 Chrome 中打开，不调用系统默认浏览器，不永久改写应用参数；只有启动配置可确认匹配时才复用已运行浏览器。
• 当前支持的全部 11 个国家和地区统一显示中文；搜索同时识别中文名称和不区分大小写的地区代码。保存值仍使用原 ISO 标识，未知旧代码保持可见。
• Profile 页面只负责配置，已移除“使用此配置运行”面板及查看配置时不必要的后台管理请求。启动和浏览器检测在应用页，刷新、停止及诊断集中到运行实例页。
• 运行实例页同时展示本次会话与 Supervisor 后台记录，按实例 UUID 去重并统一应用筛选。后台管理不依赖当前选中的 Profile 草稿；环境批量停止有明确范围，应用筛选时不提供跨应用批量停止。
• DNS 上游按协议、地址和操作分项显示，连接 IP 与证书策略按需查看；概览不再把多个上游挤成一串。运行技术数据默认折叠到诊断详情，保留兼容启动、跟踪中断和配置观测状态。
• 修复空实例列表嵌入滚动区时的布局崩溃，以及旧 UTC 时区恒等替换可能出现的死循环。

Validation

• 开发构建中实际验证了出口／时区预览、填入与保存、HTTP／SOCKS5 查询、代理失败提示、代理保存重开，以及 Chrome 参数、网页出口对照与检测页面复用。目录冲突、代理参数冲突及变更配置后拒绝复用旧根进程有实际证据。
• 普通 Profile、临时选择环境、Host 与工作区 Chrome 的独立目录及关闭 GUI 后继续使用已有实际浏览器证据。后台重启后的兼容实例跟踪中断、停止拒绝，以及原 Job 在线归零后的退出确认已有专项记录。
• 页面调整后实际验证 Profile 不再显示运行面板、应用页正常启动及打开两站、会话实例的筛选和停止；发现并修复空列表布局崩溃后重新检查了空态及非空列表。
• 既有 GUI 检查 62 项通过、5 项忽略；本次功能与页面调整经独立 Standards／Spec 审查。未新增测试用例；仅按用户明确许可将原有日本地区显示断言同步为中文。
• 发布门禁要求同一提交通过干净 Windows CI 的完整工作区、双架构 Runtime／DNS fixture、独立会话及 CPU 渲染器检查，再由正式 Release 工作流使用项目安装脚本构建并发布安装包。

Limitations

页面调整后的后台实例真实列表、诊断展开、单实例／环境批量停止及待确认启动结果查询尚未在同版本 Supervisor 下重新实机验收。本机已安装服务与开发版制品身份不匹配；用户选择保留当前 Chrome 的管理状态，因此未切换服务。该部分已有源码及既有检查复核，干净 CI 不替代这项桌面验收。

Chrome 工作区使用明确标识的兼容启动：强制注入并确认根进程载入匹配配置，但不提供严格 EXE 入口门禁保证，也不把 Hook 安装数量或 Job 成员数量当作全部读取入口、沙箱 renderer 已验证。Supervisor 重启后，旧兼容实例可能保持 TrackingLost，不能自动接管或停止。

未实际覆盖其他 Chrome 渠道、认证代理、更多 IPv6 代理端点，以及第三方服务格式变化、证书异常、超限和全部网络时序分支。相同代理配置不保证所有网站分流出口一致；第三方检测评分不是 Aura 启动成功或匿名性的保证。

Upgrade

现有应用、Profile 和浏览器数据保留。独立数据目录默认关闭；首次开启时使用新目录，不自动复制宿主 Chrome 的登录、Cookie 或书签。新配置仅影响之后启动的实例，运行中的进程不热更新。

安装器会关闭该安装目录内的 Aura 管理进程，但不会终止它们启动的目标应用。仍使用安装目录 Runtime 的应用可能阻止文件替换；建议自行保存工作并关闭相关目标应用后再升级。Supervisor 重启也可能使旧 Chrome 兼容实例进入 TrackingLost。本次发布不自动安装或重启用户正在使用的本机服务。

Installer

• File: aura-setup.exe
• Size: 12008860 bytes
• SHA-256: 39adb4a7875e2d730becbb0f3e57aaaa0d7bd31a2a55d09b62b331e75e96a6e1

v0.3.14

Aura v0.3.14

本版本补齐本机 WMI/CIM 网卡 MAC 读取的 Profile 覆盖，新增 PowerShell 7 终端选项，并改善 MAC 审计和辅助进程启动失败反馈。同时包含 v0.3.13 开发版本的浏览器语言、时区缓存与子进程启动修复。

Changes

• 本机 Get-NetAdapter 和 Get-CimInstance 网卡查询现在返回 Profile 配置的 MAC。覆盖 Win32_NetworkAdapter.MACAddress、Win32_NetworkAdapterConfiguration.MACAddress，以及 MSFT_NetAdapter.NetworkAddresses 和 PermanentAddress。各接口保留原有地址格式；MAC 留空时仍返回宿主值。同步、异步查询以及对象克隆、序列化后的读取均纳入处理。
• 终端宿主明确区分 Windows PowerShell 与 PowerShell 7。PowerShell 7 使用 pwsh.exe，支持从 PATH 和常规安装目录查找，并保存所选终端；未找到时明确报错，不会静默改用 Windows PowerShell。
• MAC 审计区分 MAC 覆盖与 DNS 跟随宿主的情况，缓冲区大小查询不再被记录为成功覆盖。
• Session 辅助进程启动失败时提供失败阶段、文件路径、系统错误码、进程 PID 和退出状态。系统返回安全软件阻止的错误码时，提示查看 Windows 安全中心保护历史。这项改动改善诊断信息，不代表已消除 Defender 检出。
• Chrome/Edge 在 Compatibility 模式下启动的沙箱渲染进程收到父进程的固定 Profile 环境与语言参数，同时保留浏览器的受限令牌、沙箱启动属性和挂起状态。
• 时区缓存访问同步；临时 Windows 枚举错误会在后续查询中重试。标准时间与夏令时间状态按当前真实 UTC 时间计算，不再固定为进程启动时的状态。
• CreateProcessA 转换为 Unicode 时保留扩展启动属性及其他启动信息；无效结构或字符串转换失败明确返回错误。子进程审计补充成功创建的 PID 和失败时的 Windows 错误码。

Validation

• 在版本升级前的开发构建中，PowerShell 7、64 位与 32 位 Windows PowerShell 5.1 分别使用两套 MAC Profile，六次真实运行均成功；Get-NetAdapter 与 Get-CimInstance 返回配置值。
• x64/x86 原生 Probe 各观察到 96 个非空 MAC 值，均与 Profile 匹配。WQL 查询、Session 复用、显式本机 DCOM Session、-InputObject 刷新、Clone 和原生 CIM 序列化验证通过。
• 连续 1,100 次查询和 300 次 Session 创建、关闭正常完成；跨位数子进程继承正确。旧 Runtime 及混入旧 x86 DLL 的组合被拒绝，没有静默返回宿主 MAC。MAC 留空时返回宿主值，宿主查询结果在运行前后保持一致。
• 版本化的 cargo check --workspace、工作区构建和正式 NSIS 安装包构建通过，程序文件版本为 0.3.14；9 个安装包输入的哈希与本次 Release 构建一致。独立 CPU 渲染器的已有检查通过。没有新增或修改测试用例。
• 本地完整工作区检查在 Supervisor 通道项中断：正在运行的安装版 Supervisor 占用同一用户的唯一端点，测试拒绝了与预期不符的程序文件。未关闭该用户服务；发布流程要求同一提交通过干净 Windows CI 的完整工作区检查。
• v0.3.13 的既有验证中，独立数据目录下的 Chrome 页面报告 Profile 的语言和时区，加载的 Runtime 哈希与开发构建匹配，宿主配置保持原值；相关构建和已有检查通过。

Limitations

本次 MAC 覆盖针对注入进程的本机 CIM 查询。真实远端机器查询的保留行为尚未实测；安装升级、GUI 保存后重开及从下拉框启动 PowerShell 7 的完整操作流程、长时间运行尚未验证。

Defender 曾检出并隔离 Session Broker。现有事件无法确定具体触发行为，本版本不认定该检测为误报，也不宣称已解决检出问题。

浏览器修复关闭了已验证的环境传播缺口，但原始的另一台机器重启 Chrome 后保留宿主语言、时区的问题尚未在本机复现。Compatibility 模式的沙箱渲染进程仍仅有部分原生环境覆盖，不通过该路径注入 Runtime DLL。既有 Chrome 验证中出现过 ERROR_ACCESS_DENIED（5）的独立注入失败，其具体目标尚未确定；注入完全失败仍拒绝启动。

Upgrade

升级后重新启动目标应用实例，才能加载新的 Runtime。已运行实例保留启动时的 Profile 和已加载的 Runtime；已有应用与 Profile 无需重建。需要 PowerShell 7 时，在应用的终端宿主中选择 PowerShell 7，并确保已安装 pwsh.exe。

Installer

• File: aura-setup.exe
• Size: 11658348 bytes
• SHA-256: e62842ec811fd0a012fbc6be9a8fd9881058afe434f5aa1cf56ece56b8879b71

v0.3.12

Aura v0.3.12

This release makes the audit page responsive when scrolling through hundreds of records, corrects the selection and counting of recent audit events, and expands the Profile editor's region, language, and timezone options.

Changes

• The CPU renderer combines heavily fragmented repaint regions into one bounding rectangle before drawing. Scrolling an audit table previously produced about 100 regions per frame, repeatedly traversing layers and rebuilding the window-sized clip mask. Small updates retain their existing partial repaint behavior. The audit page keeps its continuous list of up to 500 records.
• Audit loading now scans every JSONL file one line at a time and retains the 500 newest events by their UTC timestamps. UUID filenames and delayed writes from different processes no longer determine the displayed timeline. Retained event memory is bounded, and the capture count reports all successfully parsed records rather than the 500-row display limit. The page explicitly states that Refresh updates its records.
• Region choices now include TW, SG, JP, PH, GB, DE, KR, BO, and TR alongside CN and US. Locale and UI language choices share these new values:

Location	Language choices	IANA timezone
Taipei	Traditional Chinese: zh-TW	Asia/Taipei
Singapore	English: en-SG; Chinese: zh-SG	Asia/Singapore
Japan	Japanese: ja-JP	Asia/Tokyo
Philippines	English: en-PH; Filipino: fil-PH	Asia/Manila
United Kingdom	English: en-GB	Europe/London
Germany	German: de-DE	Europe/Berlin
South Korea	Korean: ko-KR	Asia/Seoul
Bolivia	Spanish: es-BO	America/La_Paz
Turkey	Turkish: tr-TR	Europe/Istanbul

• Manila and La Paz now have explicit Windows/IANA mappings and Chinese display names. Japan, South Korea, Germany, the Philippines, and Bolivia can also be found by their Chinese country names in the Windows timezone selector. Singapore and the Philippines share the Windows ID Singapore Standard Time; the Windows list contains it once. Select Manila in the advanced IANA field for a Philippines-specific IANA identity; the Windows field synchronizes automatically.

Validation and performance

• Before versioning, an optimized build was measured in an actual Windows GUI using the same two captured logs, a 500-row continuous audit list, and 60 wheel inputs. Total input-processing time fell from about 17.4 seconds to 1.8 seconds, and process CPU time fell from about 17.3 seconds to 0.9 seconds. Median input response fell from about 287 ms to 31 ms. The measurement includes input pacing and message processing; it is not a frame-rate measurement or a guarantee for other machines.
• Targeted temporary renderer measurements identified drawing as the dominant cost: approximately 240–310 ms per scrolling frame before coalescing, and 12–14 ms after. Temporary instrumentation was removed. The final build was also checked by scrolling to the bottom, returning to the top, and switching pages, without observed stale pixels or displaced text.
• Existing GUI checks passed with 62 tests passed and five conditionally ignored. The separate CPU-renderer suite passed five existing checks. Existing option and timezone-mapping checks passed, and Windows accepted all 11 added locale names and enumerated the required timezone IDs. No new test cases were authored or existing test cases changed.
• After versioning, local workspace checks passed 482 tests before stopping at two Supervisor channel failures: a running Release Supervisor owned the same user/integrity endpoint, so the test fixture was correctly rejected for an executable identity mismatch; the second failure followed from the first panic. There were 20 conditionally ignored cases in the executed suites. The existing manager was preserved, subsequent workspace suites were not run locally, and this result is not a complete workspace pass. The locked renderer suite separately passed all five checks.
• Publication requires successful Windows CI on the exact release commit, including workspace, Runtime, detached-session, and separate CPU-renderer checks. The release workflow uses the canonical installer script; an independent download and SHA-256 comparison verifies the published installer.

Limitations

Audit loading still scans the directory synchronously on startup and manual refresh; very large accumulated logs have not been measured. Multi-monitor interaction and long-running scrolling have not been verified. Language tokens being accepted by Windows does not prove that every target application ships the corresponding interface translations.

The supplied logs contain Host DNS calls, three child creation/injection failures, and Chromium renderer coverage exceptions. This release does not change those Runtime paths or claim to diagnose their original configurations: the captured processes had exited, and the audit records did not identify the immutable Profile or loaded Runtime build. Audit status badges also retain their existing meaning.

Upgrade

Install aura-setup.exe or use Aura's updater, then reopen Aura. Existing application, Profile, and UI settings are retained; the new choices do not rewrite saved Profiles. For the new language or timezone settings to affect a target application, edit its Profile and launch a new instance. Already running processes retain their startup configuration.

Installer

• File: aura-setup.exe
• Size: 11648653 bytes
• SHA-256: 946661d2e6f98257f0753908b8155a56b21691403cce02672e433f6bc853f5dc

v0.3.11

Aura v0.3.11

This release fixes two child-process registration defects that can make Git and other short-lived commands fail to start through Aura. It also improves Broker concurrency and records actionable failure details instead of reporting every registration failure as access denied.

Changes

• Child registration now validates the real parent process and process creation time before retiring an obsolete binding for a reused Windows PID. A new process no longer conflicts with a stale registration left by an exited child. Repeated registration for the same process still preserves immutable Profile and runtime identity checks.
• The Runtime Broker handles up to eight connected clients independently, so an idle connection no longer blocks all subsequent bootstrap requests. Reply writes have their own bounded deadline after request validation; a slow validation no longer silently consumes the entire reply window. Shutdown skips queued validation work after acquiring the registry lock.
• Failed child registration records the connect, send, read, identity, or response stage, Windows error code, elapsed time, and a bounded Broker rejection reason in Audit Mode. Native I/O errors survive cancellation and handle cleanup. Injection and binding failures still reject startup.
• Runtime bundle construction no longer hashes the primary DLL twice. Per-process integrity and loaded-module checks remain enabled.

Validation and performance

• Existing IPC checks passed: 18 library checks and seven real named-pipe authorization checks. Fresh Runtime injection also passed for an x64 root, gated x64 children, legacy CreateProcessA children, and gated x86 children. No new test cases were authored.
• Before versioning, the final patched build completed 400 consecutive Git launches with Audit Mode enabled. Forty-nine launches reused a previously observed Git shim PID. The resulting audit contained 801 process initializations and zero child-binding or injection failures.
• On the same idle development machine, 40 sequential Git launches had median durations of 85.8 ms with the original 0.3.10 build and 80.8 ms with the patched build; the uninjected control was 30.3 ms. Four concurrent workers completing 40 launches had median durations of 77.6 ms with the original build and 58.0 ms with the patched build. Sequential measurements used the Git command shim with redirected output; concurrent measurements used the actual Git executable without output redirection. These are local samples, not whole-application benchmarks or a guarantee for other machines.
• A separate hang during the measurement occurred in the uninjected control as well when PowerShell background jobs redirected Git output. That workload was excluded from the performance comparison.
• Publication requires successful Windows CI for the exact release commit, including workspace checks, detached-session checks, and the separate CPU-renderer regression suite. The canonical installer build and an independent download/checksum comparison verify the published package.

Limitations

The supplied remote audit identifies child binding as the failing stage, but the old log does not distinguish every internal rejection or timeout. The reported ChatGPT/Codex workflow and brief console-window flashes on the other machine have not been reproduced interactively. This release does not claim to resolve every possible cause of those flashes or to establish DNS leak behavior from a Host-mode audit initialization entry.

Upgrade

Install aura-setup.exe or use the updater, then restart Aura and relaunch ChatGPT/Codex and other applications through the updated version. Existing application and Profile settings are retained. Already running processes and their detached session hosts keep the old Runtime until they are relaunched.

Installer

• File: aura-setup.exe
• Size: 11629732 bytes
• SHA-256: 70a3bc42f46d3a9c4964788b50bf3dfd98a5fea009f697379a2876303460a322

v0.3.10

Aura v0.3.10

Applications launched with an Aura environment can continue creating child processes after Aura closes. This fixes command startup timeouts in long-running applications such as Codex when their original Aura launcher has exited.

Changes

• Application and CLI launches with a Profile now use an independent session host. It retains the Runtime Broker and the immutable startup configuration until the entire tracked process tree has exited, including children that outlive their root process.
• Normal launcher exit, launcher termination, and closing the launcher's console no longer remove the Broker from an otherwise running process tree. The session host detaches from the launcher's console after startup completes.
• The session host executable and paired Runtime DLLs run from content-verified caches outside the installation directory. Installer shutdown of installed Aura executables does not directly terminate the cached session host.
• Startup retains authenticated Runtime identity checks and rejects injection failures. Session handoff checks both pipe endpoints and transfers the retained root process handle, so short-lived roots do not depend on reopening a PID.
• Windows Terminal handoff keeps its per-run Job and failure cleanup. Packaged applications retain their existing best-effort Job assignment behavior; managed Workspace runs continue using the existing Supervisor path.

Validation and limitations

• Before versioning, real-process checks covered normal launcher exit, termination of the test launcher, and closing its own hidden console. The fixture configuration and US Development Profile completed 30 cmd, Git, Cargo, Rustc, and PowerShell launches, preserved the Profile and actual timezone view, and released the Broker after the last target exited.
• Existing launcher and CLI checks passed with 244 tests passed and 12 conditionally ignored. No additional test cases were authored during this release preparation.
• Publication requires successful Windows CI for the exact release commit, including the existing workspace checks, detached-session checks, and separate CPU-renderer regression suite. The installer is built through the canonical packaging script and its public checksum is verified independently.
• These checks do not establish an interactive installed-Codex session, an elevated in-place upgrade, or Windows Terminal ConPTY interaction. Packaged application activation retains its existing post-activation coverage and tracking limitations.
• Aura remains a process-scoped environment launcher, not a security sandbox. Host Windows settings are unchanged.

Upgrade

Install aura-setup.exe or use the updater, reopen Aura, and restart applications through the updated version. Existing application, Profile, and UI settings are retained. Processes started by an older Aura version do not automatically acquire the new session host; already detached old instances need to be relaunched to benefit from this fix.

Installer

• File: aura-setup.exe
• Size: 11599413 bytes
• SHA-256: e288d6055b11312f090507d1bddf25cb68a59653622ce000e4bcce684f7204bc

v0.3.9

Aura v0.3.9

Aura gives application and environment configuration lists more room and remembers each page's pane proportions after restart. This release also separates GUI workflows and Windows command-line preparation into focused modules.

Changes

• Applications and environment configurations now share a default split of 60% for the list and 40% for the detail panel, excluding the navigation bar.
• Dragging either page's divider saves its proportion to the existing user UI configuration. Each page remembers its own value; reopening Aura restores it. Existing saved proportions take precedence over the default.
• Older UI configuration files retain their remembered window-close behavior and receive the new default proportions. Saving close preferences preserves pane proportions, and resizing panes preserves close preferences.
• GUI application operations, environment configuration editing, unsaved-edit navigation, and audit loading now live in separate modules. The DNS form depends on its editor state and DNS mode rather than the complete application state.
• Windows argument parsing, quoting, ComSpec preparation, and activation-program resolution now live in a dedicated launcher module. Public entry points, argument rules, and process injection behavior are preserved.

Validation and limitations

• Regression coverage exercises default proportions on both pages, independent resizing, application reconstruction, and preservation of close preferences. Configuration coverage also checks older files and invalid proportions.
• Existing argument parsing and ComSpec tests follow the extracted implementation. Publication requires successful Windows CI for the exact release commit, including workspace tests and the separate CPU-renderer regression suite.
• Build, test, and published-installer verification do not establish manual drag/restart behavior in an installed GUI, elevated in-place upgrades, or physical-monitor behavior. Those remain separately unverified for this release.
• Aura remains a process-scoped environment launcher, not a security sandbox. Existing Runtime and application compatibility limitations continue to apply.

Upgrade

Run aura-setup.exe or use the updater, then reopen Aura. Existing applications, environment configurations, and UI close preferences are retained. Previously saved divider proportions are restored; when no proportions were saved, both pages use the new 60% / 40% default.

Installer

• File: aura-setup.exe
• Size: 11142860 bytes
• SHA-256: b4d434dd21ac7eb83b6b1637722a26a4478571988aa47ed0950d53d99f089712

v0.3.8

Aura v0.3.8

Aura now manages reusable environment configurations directly, with clearer application launch controls, Profile identity views, and strict Profile DNS routing. This release also fixes input text escaping its fields and installation blocked by a running Supervisor.

Changes

• Application selection and launch actions live on the Applications page. Environment configurations manage region, locale, language, timezone, DNS, environment variables, and optional identity values; each new instance receives an immutable snapshot.
• Applications use compact selectable rows, with launch, alternate configuration, host launch, and instance actions in the detail panel. Application and configuration panes resize independently during the session. Forms and DNS menus share the dark styling; longer capability explanations are available through tooltips.
• Optional supported Win32 identity views cover computer name, user name, adapter MAC, and MachineGuid registry reads. MAC and GUID generation modifies only the draft configuration, without changing host identity.
• Arbitrary DNS QTYPEs route through configured UDP, TCP, DoT, and DoH transports. Strict virtual-view DNS returns failure when configured upstreams fail, preventing host-resolver fallback in supported API paths.
• Repeated full-QTYPE queries share a bounded process-local wire-response cache, including DoH service-name bootstrap answers. The new cache ages returned TTLs, expires within the shortest response TTL, separates upstream/TLS policies and query options, and merges simultaneous misses. Explicit cache-bypass and wire-only queries still access their configured upstream. SVCB/HTTPS flat records remain available on older Windows DNS decoders.
• Localhost resolution remains native while Profile DNS is enabled. This fixes Antigravity language-server startup failing with exit code 2 when Windows internally uses a private DNS request version. Public DNS requests continue through Profile routing and validation.
• DoH connection IPs can be left empty. Runtime bootstraps the service hostname through a directly connectable upstream from the same Profile, preserving URL/TLS identity and the original deadline/cancellation. It does not add a default resolver or use host DNS. Without an available bootstrap source, configuration can be saved but resolution fails.
• Saving also validates and includes the DNS upstream being entered, without requiring Add first. Invalid entries show a nearby error; saved editor state is normalized to avoid duplicate upstreams.
• CPU text rendering respects local clipping, keeping GUIDs and URLs within their fields and preserving subsequent dropdown labels/checkmarks and text alignment.
• Supervisor management/recovery retain authoritative snapshot identity and instance ownership across mixed architectures, late replies, generation changes, and uncertain stop results.
• Installer/uninstaller stop only Aura management processes from the chosen installation directory, including Supervisor, preserve launched applications, and check locked payloads before replacement. The finish page launches Aura through the ordinary Explorer desktop session.
• Rust 1.99.0 is pinned for development and Windows CI. The installer packages the GUI, CLI, Broker, Supervisor, probes/helper, and both Runtime architectures.

Validation and limitations

• Publication requires successful Windows CI for the exact release commit, including workspace build/tests and the separate CPU-renderer regression suite.
• Dual-architecture DoH routing contracts and eight actual injected cases cover controlled UDP/TCP bootstrap followed by public DoH, plus explicit no-source failure. This establishes covered API behavior, not a global network-capture guarantee.
• Cache and route contracts run for x64 and x86 in CI. Controlled routing verifies one transport call for 100 repeated A/HTTPS/SVCB queries and for eight simultaneous cold queries, plus cancellation/deadline while waiting. Injected API acceptance also counts real fixture UDP packets across A/W/UTF8/Ex/async queries and explicit bypass. These checks do not establish public DNS latency or a full application workload improvement.
• This optimization removes repeated work through response reuse. Cold DoH/DoT exchanges still establish connections; persistent connection pooling and trust-snapshot reuse are not part of this change. The existing address-only resolver cache retains its separate policy.
• Antigravity 2.19.1 language-server startup was reproduced as exit 2 with the existing Profile, then verified with the matched 0.3.8 CLI/Runtime: localhost HTTP/HTTPS listeners, successful initialization, and 30 seconds alive. Audit records preserve remote Profile DoH routing. Full IDE login/function testing remains separate.
• Desktop fixtures verified 1400/1100-pixel application layouts, narrow editor clipping, and pending-DoH save/reopen without duplication. Installer helper fixtures cover directory ownership, locks, and ordinary desktop launch. Elevated in-place upgrades across Windows installations and physical-monitor soak testing remain separately unverified.
• Aura provides process-scoped environment information while applications use host files, GPU, networking, and user permissions. It is not a security sandbox. App-owned DNS protocols and unsupported browser renderer/API paths may bypass these views; webpage/account language can differ from browser UI language.
• IPv6 connection discovery/transport and CPU/GPU/disk identity remain deferred. Driver/service prototypes are not a qualified kernel container; Container/Strong enforcement remains unavailable.

Upgrade

Run aura-setup.exe or use the updater, then reopen Aura. Existing application and environment configuration data is retained. Existing instances retain their snapshots; edits apply to new runs.

Installer

• File: aura-setup.exe
• Size: 11146819 bytes
• SHA-256: ca39d43d19fb84f603dfdc6b5cb107b54cbb542bf66a6104476039f4543bae13

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

v0.3.6

Aura v0.3.6

This patch release switches Aura's interface to CPU rendering to reduce its baseline memory use, reduces development build artifacts, and overlaps the independent Rust and Runtime builds when generating an installer.

Changes

• The GUI now uses Iced's tiny-skia CPU renderer directly. Previously, Iced tried wgpu first and used tiny-skia only when graphics-backend initialization failed. Aura's forms and lists now avoid initializing the GPU backend even on machines with a supported GPU. Existing font, theme, image, and SVG support is retained.
• Development builds keep source-file and line information for project code and omit third-party dependency debug symbols. Incremental compilation remains enabled. This reduces generated debug data and linker work; inspecting full variable and type information in a debugger requires a build with more debug information enabled.
• The canonical installer script starts the Rust release workspace and the x64/x86 Runtime builds concurrently, using their existing output directories and dependency tracking. It waits for every build to finish successfully before staging the six executables and two Runtime DLLs. Missing native exit codes and nonzero exits fail the build. Each task and the complete packaging operation now report elapsed time.

Measured results

A Windows comparison used the same debug harness binary and real Aura state, views, and font selection, changing only the Iced backend. Both runs used a 1400 x 880 window at scale factor 1, twelve synthetic applications, and equivalent isolated configurations. After hiding through Aura's tray transition, approximately forty seconds of observation produced these stable values:

Metric	tiny-skia CPU	wgpu GPU
Private working set	26.23 MiB	149.09-149.17 MiB
Total working set	57.78-57.79 MiB	242.05-242.12 MiB
Private committed memory	29.64 MiB	261.12-261.25 MiB

In this fixture, private working set decreased by about 82% and private committed memory by about 89%. Working set describes resident memory; private committed memory is not all resident physical memory. These are fixture measurements, not a promised installed-app baseline.

With the CPU-rendering dependency configuration held constant, the GUI development PDB decreased from 188.01 MiB to 37.56 MiB, and its executable decreased from 25.93 MiB to 23.37 MiB after the debug-information changes. Existing historical build artifacts are not automatically deleted.

An earlier local installer validation with unchanged inputs and available build caches completed in about five seconds. That is an incremental packaging result, not a cold-build benchmark or a quantified cold-build speedup.

Upgrade behavior

Install the update through Settings or run the downloaded aura-setup.exe, then reopen Aura to use the CPU renderer. The installer retains local configuration and the existing installation directory. Applications previously launched through Aura continue running when the installer closes the old control process. This release adds no Profile migration and changes no Runtime hook or virtualization policy.

Validation and limitations

• GUI unit tests passed: 34 passed, 4 ignored. Application, Profile, and Settings screenshots from the CPU fixture showed Chinese text, SVG icons, lists, and forms correctly; the application-list screenshot was also compared with the GPU fixture.
• Local v0.3.6 workspace build and check passed. After supplying both Runtime DLLs, local workspace tests stopped at acceptance_ansi_default_locale_uses_profile: the injected session reported en-US where that test expects fr-FR; six other tests in that acceptance matrix passed and one was ignored. This local run is not reported as a complete workspace test pass; the uninjected Windows CI run is required before tagging.
• PowerShell 7 and Windows PowerShell 5.1 passed isolated installer-script checks for successful builds, Cargo failure, x64 configure failure, x86 build failure, and a discovered tool disappearing before execution. Failure cases did not invoke NSIS. Paths containing spaces, an ampersand, and literal percent signs were exercised.
• Local v0.3.6 packaging completed in 17.4 seconds with available build caches and validated all eight staged payloads against their corresponding release outputs, including both Runtime architectures. The GUI executable identifies itself as Aura v0.3.6. The publication workflow rebuilds the installer for the tagged commit and appends its final size and SHA-256 below.
• The rendering harness used a one-second polling subscription and bypassed the production singleton. It did not reproduce the production 200 ms tray polling interval. Both comparison processes inherited the current session's Aura Runtime; they were not uninjected host controls.
• A fresh installed v0.3.6 upgrade, high-DPI fast scrolling, and an hours-long memory observation have not been manually verified. Clean-host workspace CI on the exact release commit remains the publication gate.

Installer

• File: aura-setup.exe
• Size: 6348089 bytes
• SHA-256: c68d1985c7a7623a4cf84e52bd0b572cc41b70aa4680324ebeaa0edfdcd8ed3e