@@ -6,7 +6,7 @@ Linux 2.3.3 is published. The Windows, macOS and Flatpak packages are also publi
 
 On the Omarchy x64 laptop, the publisher-authenticated public AppImage was installed with the independently reviewed 2.3.3 trust bundle. The installed AppImage SHA-256 is `4d7b49048718bc7a25407362958ea63b7d5d69a66f23afc8a287274be3245747`; the extracted native binary is `6b47514c3028cc4e3e98d7bd2fa46f73a437d5883dd8551278d3b0e4da3d04f7`. The installer required and observed the first native window.
 
-A focused test on the laptop's actual Wayland compositor passed 12 interface checks, including onboarding, provider discovery (including Grok), accessibility, a scripted-provider task with approved file writing and command execution, and clean app shutdown. It excludes the floating-window sizing and resize tests, recovery and the full UI endurance suite. Separately, the extracted installed engine passed 100 sequential and 80 concurrent tasks, five cancellations and persistence after a graceful stop. That probe uses a loopback scripted provider: it does not demonstrate real-model inference or inference-server memory behavior. The [installation receipt](qa/platform-release-2.3.3/omarchy-installation.json), [Wayland interface results](qa/platform-release-2.3.3/omarchy-native-wayland.json), and [endurance results](qa/platform-release-2.3.3/omarchy-endurance.json) retain the hashes and measurements.
+A focused test on the laptop's actual Wayland compositor passed 12 interface checks, including onboarding, provider discovery (including Grok), accessibility, a scripted-provider task with approved file writing and command execution, and clean app shutdown. It excludes the floating-window sizing and resize tests, recovery and the full UI endurance suite. Separately, the extracted installed engine passed 100 sequential and 80 concurrent tasks, five cancellations and persistence after a graceful stop. That probe uses a loopback scripted provider: it does not demonstrate real-model inference or inference-server memory behavior. The [installation receipt](qa/platform-release-2.3.3/omarchy-installation.json), [Wayland interface results](qa/platform-release-2.3.3/omarchy-native-wayland.json), and [endurance results](qa/platform-release-2.3.3/omarchy-endurance.json) retain the hashes and measurements. The raw Wayland receipt retains a stale scope sentence saying Grok was excluded; its recorded configuration and picker check show that the Grok row was present in this run. The receipt is kept unchanged. This does not qualify a live Grok login or model task.
 
 On the Windows 11 x64 laptop, the public 2.3.3 installer (SHA-256 `f6991390e42d0fd85e2456b95e6209053bf9db35ff94ed940df2bf7fd71e65c3`) installed successfully and passed clean-PATH runtime probes. Native WebView checks verified editor find/replace, undo, both redo shortcuts, saving and Settings without reported JavaScript errors. The installed engine also passed 100 sequential and 80 concurrent tasks, five cancellations and persistence after forced process termination, using a scripted provider. A real Gemma 4 E4B local CPU coding task also passed in 662 seconds; the agent ran the original five tests, which were preserved and passed again independently. This one task does not establish broad model quality or GPU inference. See the [real-model result](qa/platform-release-2.3.3/windows-real-model.json), [installation](qa/platform-release-2.3.3/windows-installation.json), [native interface](qa/platform-release-2.3.3/windows-native-webview.json) and [endurance](qa/platform-release-2.3.3/windows-endurance.json) receipts.