Akashic 0.1.0-alpha.7 — unsigned testing alpha

Unsigned testing alpha. Windows installers are not code-signed and may show an unknown-publisher or SmartScreen warning. Updates are enabled for this alpha channel. Earlier testing previews with updates disabled need a one-time manual installation.

Akashic 0.1.0-alpha.7. Installers for Windows x64 and Linux x64. Linux packaging source revision: 5d6b306fc682b3d753f3294a63f64fe5229cad84. SHA256SUMS accompanies the downloads. macOS is not included in this release.

Linux native packages use a space-free installation directory to avoid a Chromium sandbox launch failure. Runtime payload revision: d2145265b0e05732f15a2a86e30693ebb3d3faf6; packaging revision: 5d6b306fc682b3d753f3294a63f64fe5229cad84. Includes the selected Velvet Afterimage startup chime, non-blocking backend liveness initialization, and transactional first-run database schema creation. Linux AppImage and Debian onboarding/chat/restart were tested with the bundled runtime and a local scripted provider on Stargaze (Debian application files on a temporary RAM-backed volume; profile state on disk). RPM is packaged but has not been exercised on a native RPM distribution.

Windows and Linux are both alpha.7. Older Windows alpha.6 assets are retained for recovery; alpha.yml now points to the alpha.7 Windows installer.

Windows x64 alpha.7 was built and installed natively on Neptune from source 43e074ad488eaa2ca5abcc3f4a2c3d794a11a262, including the merged database-startup/backend-liveness fixes and corrected Windows executable version metadata. Relocated runtime checks passed with no network or package-installer attempts. Fresh onboarding, profile/theme persistence, local scripted-provider chat, active-work quit behavior and restart passed against the exact installed candidate with Chromium sandboxing enabled and no owned backend survivors. This was simulated inference, not a real provider/account test; a live alpha.6-to-alpha.7 in-app replacement was not retested. Known limitation: first launch on the tested mechanical disk was very slow (333 seconds for full runtime verification); subsequent full verifications took 12 and 20 seconds. The native journey used longer bounded startup waits and waited for usable onboarding rather than requiring a transient splash to remain visible. This is an unsigned testing alpha, not a claim that cold-start performance is fixed.